Fig. 1Players on 【南瓜】Build-TestRG-S0952-01 · Sheet 1 of 11
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S0952-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 4% of all ranked servers, top 16% in EA. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S0952-03 · Sheet 3 of 11
Schedule
Wipe 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.
usual gap3.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak24players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Thu 22 OctMon 19 OctTue 13 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 24, 15 hours in.
ScheduleExpected wipesRG-S0952-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 21:55 UTC6d ago
24
–
running
1
Mon 19 Oct, 01:15 UTC10d ago
25
held half
3.9 days
4
Tue 13 Oct, 20:03 UTC15d 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 UTC32d ago
31
held half
5.2 days
5
Wed 23 Sep, 21:05 UTC35d ago
24
held half
3.1 days
3
Mon 21 Sep, 22:30 UTC37d ago
33
–
1.9 days
0
Mon 21 Sep, 12:18 UTC37d ago
30
–
0.4 days
24
Thu 17 Sep, 23:45 UTC41d ago
27
held half
3.5 days
3
Sun 13 Sep, 16:19 UTC45d ago
33
held half
4.3 days
16
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.
Table 1Wipe logRG-S0952-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
How reliable is 【南瓜】Build-Test, and is it online now?
【南瓜】Build-Test is up at this moment. Counted from its reported uptime, the last restart was about 5 days 23 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.
2.
What does the recorded performance of 【南瓜】Build-Test show?
Average server fps over the last 48 hours is 99; the lowest was 49. Counted at its highest: 146,918 entities, buildings, deployables and the rest of the world included. 6,217 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.
3.
What location is recorded for 【南瓜】Build-Test?
The EA tag is how 【南瓜】Build-Test lists itself in Asia. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 45.125.45.246:28015 is its address.
4.
On which Rust version is 【南瓜】Build-Test running?
Rust network protocol 2635 and build 168909 on Windows: that is what 【南瓜】Build-Test runs. The same protocol is required for joining, and Steam updates your game to it.
Population
5.
How many players are plotted on 【南瓜】Build-Test?
At the last refresh, 【南瓜】Build-Test recorded 6 players across 101 slots. The seven-day mean is 10 players; the peak over the same period is 28. Averaged over the last 48 hours, the player count is highest at 13:00 UTC: 25 players.
6.
In the rankings, which position does 【南瓜】Build-Test hold?
The same seven-day player-hour count places 【南瓜】Build-Test at #89 within Asia, #952 across all ranked servers and in the top 4% of them.
Wipe data
7.
What happens on 【南瓜】Build-Test on the day of a wipe?
At their busiest, its recent wipes drew 24 players on average. 15 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.
8.
What wipe schedule has been recorded for 【南瓜】Build-Test?
No next wipe can be predicted for 【南瓜】Build-Test: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 6 days 2 hours ago.
Map and rules
9.
What settings and rules apply on 【南瓜】Build-Test?
Gather rate for 【南瓜】Build-Test: not stated in the name. Eight players per group: the default for the game. It runs the build & creative game mode, sandbox building, no gathering. It appears under Community in the server browser. Plugins run: Oxide. VAC is off: that is Valve's anti-cheat.
10.
What is the map for 【南瓜】Build-Test?
Seed 1361858059 and size 4,000 define the procedural map 【南瓜】Build-Test generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
11.
Where does 【南瓜】Build-Test appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry 【南瓜】Build-Test are: Rust build servers, plotted live. On the server list, these filters bring it up: 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.
12.
On 【南瓜】Build-Test, what is meant by each tag?
gmrust (Game mode): Survival in standard Rust style; mp101 (Max players): 101 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^k (Build server): Design and practise bases here; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): The browser's listing places it under East Asia are the tags 【南瓜】Build-Test publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
How to join
13.
How is 【南瓜】Build-Test joined?
Connect with client.connect 45.125.45.246:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
NotesAnswered from the figuresRG-S0952-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp101,ptrak,$r?,v2635,^k,EA,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeSurvival in standard Rust style.
mp101
Max players101 player slots.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Gameplay
^k
Build serverDesign and practise bases here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
EA
East AsiaThe browser's listing places it 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.