Rust HeatmapInfrared · players
IR live Players89,289 Servers11,829 Warm4,008 Fresh wipes · 3h82 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 13° now Linear · 0–101° · slots

【南瓜】Build-Test

Online EA 45.125.45.246:28015 checked 1h ago

oxide
Sp1 · players now 13/ 101
13% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 28°
Mon 19:00flare: a wipe in that hourWed 17:00
10
7-day average
peak 28
#958
rank
top 4% · #88 in EA
5d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 1h ago

Li2Players

AveragePeak
01020304019:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Li3Server performance

05010015020019:0004:0013:0023:0008:0017: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
15001k1.5k2k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 4% of all ranked servers, top 16% in EA. Ranked on player hours over the last seven days.

Bx1Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

3.5 days
usual gap
between real wipes
25%
on rhythm
of its recent wipes
24
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctMon 19 OctTue 13 Oct
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 24, 15 hours in.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 21:55 UTC5d ago 24 – running 1
Mon 19 Oct, 01:15 UTC9d ago 25 held half 3.9 days 4
Tue 13 Oct, 20:03 UTC14d ago 23 held half 5.2 days 0
Mon 12 Oct, 09:06 UTC16d ago 25 – 1.5 days 15
Sun 11 Oct, 17:55 UTC17d ago 25 – 0.6 days 2
Thu 8 Oct, 13:33 UTC20d ago 32 held half 3.2 days 0
Tue 6 Oct, 10:36 UTC22d ago 24 held half 2.1 days 12
Fri 2 Oct, 04:30 UTC26d ago 25 held half 4.3 days 0
Sun 27 Sep, 00:04 UTC31d ago 31 held half 5.2 days 5
Wed 23 Sep, 21:05 UTC34d ago 24 held half 3.1 days 3

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+ · 10 on average
17 / 100
19 / 50
2 / 188
2 / 150
風紀委員 堤防部
EA · groups of 8+ · 2 on average
0 / 30
【开心萌橙PVE-kxmc】休闲娱乐/5倍/防抄家/任务
EA · groups of 20+ · monthly · 2 on average
1 / 150

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on 【南瓜】Build-Test?

At their busiest, its recent wipes averaged 24 players. The crowd on the latest wipe reached its peak 15 hours in. Half the peak was held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on 【南瓜】Build-Test?

There is no next wipe to predict on 【南瓜】Build-Test, which wipes at irregular times. 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 5 days 16 hours ago.

Population

How busy is 【南瓜】Build-Test?

The current population of 【南瓜】Build-Test is 13, against 101 slots. Averaged over the past week: 10 players, peaking at 28. Its busiest point in the last 48 hours was 13:00 UTC, averaging 25 players.

How does 【南瓜】Build-Test rank against other Rust servers?

Seven-day player hours place 【南瓜】Build-Test at #958, in the top 4% of ranked servers; within Asia it is #88.

Settings and rules

Which map does 【南瓜】Build-Test run?

【南瓜】Build-Test runs a procedural map of size 4,000 with seed 1361858059, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.

What are the rules and settings on 【南瓜】Build-Test?

The name 【南瓜】Build-Test does not specify a gather rate. Groups can contain up to 8 players, the default in the game. build & creative is the game mode, building in a sandbox, with no gathering. The server browser lists it under Community. Oxide plugins are in use. Anti-cheat: Valve's VAC is off.

Location and uptime

Which version of Rust does 【南瓜】Build-Test run?

The build on 【南瓜】Build-Test is Rust network protocol 2635 and build 168909, running on Windows. Steam updates your game for you, and the protocol has to match for you to join.

Is 【南瓜】Build-Test online, and how reliable is it?

The server is up at the moment: 【南瓜】Build-Test is online. Its reported uptime dates the last restart to about 5 days 13 hours ago. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. Rust Heatmap has had it on record since 13 September 2026.

Where is 【南瓜】Build-Test located?

With its EA tag, 【南瓜】Build-Test lists itself in Asia. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 45.125.45.246:28015.

Does 【南瓜】Build-Test run smoothly?

Average server fps over the last 48 hours was 101; it never dropped below 49. The world held as many as 146,918 entities, buildings and deployables included. At its peak it held 6,217 MB of memory. What players call lag is low fps together with a growing entity count.

Tags

Which Rust Heatmap lists and filters include 【南瓜】Build-Test?

Rust build servers are the Rust Heatmap lists that 【南瓜】Build-Test fits. These are the filters that return it on the list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Build server ^k and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Players now: At least 10.

What do the server tags on 【南瓜】Build-Test mean?

gmrust (Game mode): Rust survival, standard rules; mp101 (Max players): This server has 101 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): This build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^k (Build server): Design and practise bases; ^o (Oxide): The plugin framework in use is Oxide (uMod); EA (East Asia): In the server browser it sits under East Asia are the tags 【南瓜】Build-Test publishes, and the server browser reads them. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

Connect

How do I join 【南瓜】Build-Test?

To join by console, open it with F1 in Rust and enter client.connect 45.125.45.246:28015. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

Published as mp101,ptrak,$r?,v2635,^k,EA,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Rust survival, standard rules.
mp101
Max players This server has 101 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Your game must match protocol 2635 to get in.
cs168909
Build This build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code The region code is blank.

Gameplay

^k
Build server Design and practise bases.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).

Region

EA
East Asia In the server browser it sits under East Asia.

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.