Fig. 1Players on TESTINGRG-S8840-01 · Sheet 1 of 10
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-S8840-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S8840-03 · Sheet 3 of 10
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 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak15players, last three wipes
crowd held80%else halves by day 1
The first 48 hours of its last wipes
Sat 17 OctThu 15 OctMon 12 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S8840-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 19:12 UTC10d ago
1
–
running
0
Thu 15 Oct, 14:58 UTC12d ago
18
held half
2.2 days
3
Mon 12 Oct, 14:59 UTC15d ago
25
held half
3 days
0
Thu 8 Oct, 14:58 UTC19d ago
12
held half
4 days
4
Mon 5 Oct, 15:00 UTC22d ago
24
held half
3 days
2
Thu 1 Oct, 17:57 UTCFW26d ago
23
halved by day 1
3.9 days
1
Mon 28 Sep, 15:58 UTC29d ago
24
held half
3.1 days
2
Fri 25 Sep, 17:03 UTC32d ago
22
held half
3 days
2
Mon 21 Sep, 15:57 UTC36d ago
6
halved by day 1
4 days
0
Mon 14 Sep, 15:56 UTC43d ago
25
halved by day 2
7 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.
Table 1Wipe logRG-S8840-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for TESTING, and is it up?
TESTING is up at this moment. Counted from its reported uptime, the last restart was about 2 days 12 hours ago. For the last 7 full days the record is 127 of 168 hours up, 76% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
Is TESTING stable in the figures recorded?
128 server fps on average over the last 48 hours, and never under 125. Counted at its highest: 4,021 entities, buildings, deployables and the rest of the world included. Memory use peaked at 1,061 MB. Players feel low fps and a climbing entity count as lag.
3.
In which location is TESTING hosted?
No region is published by TESTING. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 51.83.150.41:28015.
4.
On which Rust version is TESTING running?
The platform is Windows and the version is Rust network protocol 2635 and build 168909 on TESTING. The same protocol is required for joining, and Steam updates your game to it.
Player data
5.
What player count is recorded on TESTING?
At the last refresh, TESTING recorded 2 players across 500 slots. The seven-day mean is 0 players; the peak over the same period is 4.
6.
Against other Rust servers, where is TESTING placed?
Within the top 40% of all ranked servers: TESTING at #8,840 for player hours, seven days recorded.
Wipe times
7.
What is recorded on TESTING on wipe day?
An average of 15 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 80% of its recent wipes stayed above half that peak. In the other cases the crowd was below half by day 1.
8.
On TESTING, when do wipes occur?
No next wipe can be predicted for TESTING: its wipes fall at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 10 days 13 hours ago the current world was made.
Map and rules
9.
Which settings does TESTING run, and what rules?
Gather rate for TESTING: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Carbon. Anti-cheat: VAC, from Valve, is on.
10.
What is the map for TESTING?
Size 1,000 with seed 612351: that is the procedural map TESTING runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
11.
On Rust Graphs, which lists and filters contain TESTING?
The Rust Graphs lists that carry TESTING are: Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
12.
Which meaning is attached to each tag on TESTING?
The game's server browser reads these tags from TESTING: gmrust (Game mode): Standard survival, as Rust plays; mp500 (Max players): 500 player slots; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
13.
What is the way to connect to TESTING?
Enter client.connect 51.83.150.41:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.
NotesAnswered from the figuresRG-S8840-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeStandard survival, as Rust plays.
mp500
Max players500 player slots.
ts8
Group limitThe default team size of 8 applies.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Mods and access
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
^y
CarbonThe plugin framework is 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.