Rust Server TrendsSeismic network · station log
Recording Stations11,597 Players34,587 Active2,830 Wipes · 3 h59 48 h

Station XX-3850 · recording

[JP] Japan Build Server | Creative

Online 162.43.74.201:28025 checked 12m ago

moddedcarbon
Connect
Players now
0/ 20
0% full
Motion · 24 h
M0.0falling
−1 players on the day
7-day average
1
peak 5
Rank
#3,850
top 17%
Last wipe
21d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-3850 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 20 slots
Motion · 24 h
M0.0falling−1 players
Sharpest hour
+2into Mon 11:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123405:0014:0023:0009:0018:0003:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040005:0014:0023:0009:0018:0003:00

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 17% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
22.9 daysbetween real wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 7

The first 48 hours of its last wipes

Wed 7 OctMon 14 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 7 Oct, 02:50 UTC21d ago M0.0rising 1 – running 0
Mon 14 Sep, 06:04 UTC43d ago M0.3rising 2 halved by day 7 22.9 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Intoxicated SEA Sandbox - Creative | Build | Noclip EA · groups of 8+ · 9 on average
11/ 100
6/ 50
5/ 188
風紀委員 堤防部 EA · groups of 8+ · 2 on average
0/ 30
1/ 150
【南瓜】Build-Test EA · groups of 8+ · 10 on average
7/ 101
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on [JP] Japan Build Server | Creative?

Generated by the game, the map on [JP] Japan Build Server | Creative is procedural, size 1,500 with seed 1337. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on [JP] Japan Build Server | Creative?

No gather rate appears in the name of [JP] Japan Build Server | Creative. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Carbon. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on [JP] Japan Build Server | Creative right now?

A reading taken now shows 0 players on [JP] Japan Build Server | Creative, which has 20 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 5. The busiest point in the last 48 hours came at 13:00 UTC, averaging 3 players.

How does [JP] Japan Build Server | Creative rank against other Rust servers?

Over the last seven days, [JP] Japan Build Server | Creative recorded enough player hours to reach #3,850 worldwide, placing it in the top 17% of all ranked servers.

Operator and location

How reliably does [JP] Japan Build Server | Creative stay online?

Right now, you can reach [JP] Japan Build Server | Creative. Its reported uptime points to a restart about 5 days 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.

How well does [JP] Japan Build Server | Creative perform under load?

Its average server fps over the last 48 hours was 232, and it never dropped below 157. The world held up to 9,847 entities at its peak, buildings and deployables included. Its highest memory use was 1,674 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does [JP] Japan Build Server | Creative run from?

The name of [JP] Japan Build Server | Creative points to Asia, even though it publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 162.43.74.201:28025 is the address it uses.

What build of Rust does [JP] Japan Build Server | Creative use?

On Linux, [JP] Japan Build Server | Creative runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on [JP] Japan Build Server | Creative?

2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 7 it fell below half in the wipes where it didn't hold.

How often does [JP] Japan Build Server | Creative wipe, and on which days?

On record so far are too few of [JP] Japan Build Server | Creative's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 21 days 1 hours is how long the current world has been running.

Tags

What do the server tags on [JP] Japan Build Server | Creative mean?

The game's server browser reads the tags [JP] Japan Build Server | Creative publishes: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [JP] Japan Build Server | Creative appear?

The Rust Server Trends lists that take in [JP] Japan Build Server | Creative are: Modded Rust servers, tracked live, Rust build and creative servers, live and Rust creative servers. On the server list, the filters it matches are: Region: Asia; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How to join

How do you connect to [JP] Japan Build Server | Creative?

To join, enter client.connect 162.43.74.201:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players 20 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.