Rust HeatmapInfrared · players
IR live Players53,198 Servers11,665 Warm3,312 Fresh wipes · 3h84 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–20° · slots

[JP] Japan Build Server | Creative

Online 162.43.74.201:28025 checked 8m ago

moddedcarbon
Sp1 · players now 1/ 20
5% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 4°
Mon 10:00flare: a wipe in that hourWed 08:00
1
7-day average
peak 5
#3,845
rank
top 17%
21d ago
last wipe
no schedule published
–
next wipe
too few wipes seen yet
UTC checked 8m ago

Li2Players

AveragePeak
0123410:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC.

Li3Server performance

010020030040010:0019:0004:0014:0023:0008: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.

Li4Rank

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.

Bx1Wipe 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.

22.9 days
usual gap
between real wipes
2
wipe-day peak
players, last three wipes
0%
crowd held
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 02:50 UTC21d ago 1 – running 0
Mon 14 Sep, 06:04 UTC44d ago 2 halved by day 7 22.9 days 0

Peak: the most players in the first 48 hours. 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.

Bx6Similar 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
15 / 100
14 / 50
4 / 188
5 / 150
風紀委員 堤防部
EA · groups of 8+ · 2 on average
0 / 30
【南瓜】Build-Test
EA · groups of 8+ · 10 on average
14 / 101

LogQuick answers

from the figures on this page

Wipe day

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

At their busiest, its recent wipes averaged 2 players. 0 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 0% of its recent wipes. By day 7 it was below half in the wipes that did not hold.

What is the wipe schedule on [JP] Japan Build Server | Creative?

[JP] Japan Build Server | Creative has too few wipes on record yet for its rhythm to show. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 21 days 6 hours ago.

Population

How busy is [JP] Japan Build Server | Creative?

Of 20 slots on [JP] Japan Build Server | Creative, 1 are in use right now. A seven-day average of 1 players, with a peak of 5. Its busiest point in the last 48 hours was 13:00 UTC, averaging 3 players.

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

Player hours over seven days put [JP] Japan Build Server | Creative at #3,845, in the top 17% of ranked servers.

Settings and rules

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

[JP] Japan Build Server | Creative runs a procedural map of size 1,500 with seed 1337, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map. You play on a map named Custom Map.

What are the rules and settings on [JP] Japan Build Server | Creative?

A gather rate is not given in the name [JP] Japan Build Server | Creative. 8 players is the default group size, and that is the limit here. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.

Server details

Which version of Rust does [JP] Japan Build Server | Creative run?

The build on [JP] Japan Build Server | Creative is Rust network protocol 2635 and build 168909, running on Linux. To join, your game must match the protocol; Steam handles the update.

Is [JP] Japan Build Server | Creative online, and how reliable is it?

Online now: [JP] Japan Build Server | Creative. The uptime it reports puts the last restart at about 5 days 11 hours ago. 168 of 168 hours up over the last 7 full days, which is 100%. Rust Heatmap has had it on record since 13 September 2026.

Where is [JP] Japan Build Server | Creative located?

By its name, [JP] Japan Build Server | Creative points to Asia, and it publishes no region tag. Rust Heatmap shows the location a server states. It does not look up the machine's location. 162.43.74.201:28025 is its address.

Does [JP] Japan Build Server | Creative run smoothly?

The last 48 hours brought an average of 233 server fps and a floor of 157. Buildings, deployables and the rest of the world came to as much as 9,847 entities. The highest memory use was 1,674 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Tags

Which Rust Heatmap lists and filters include [JP] Japan Build Server | Creative?

The Rust Heatmap lists that [JP] Japan Build Server | Creative fits are: Rust build servers, Rust servers tagged creative and Modded Rust servers, by live population. These are the filters that return it on the list: Region: Asia; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

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

These are the tags [JP] Japan Build Server | Creative publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): Plugins run through Carbon. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

How to join

How do I join [JP] Japan Build Server | Creative?

Press F1 in Rust to open the console, then enter client.connect 162.43.74.201:28025. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust form.
mp20
Max players Slot count: 20.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol Your game must match protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code No region code is set.

Mods and access

^z
Modded The game is changed by settings or plugins, so it sits under Modded.
^y
Carbon Plugins run through Carbon.

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.