Fig. 1Players on Test ServerRG-S14185-01 · Sheet 1 of 10
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S14185-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 64% of all ranked servers, top 77% in NA. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S14185-03 · Sheet 3 of 10
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h.
The force wipe · high confidence
usual gap1.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 2
Coming wipes
7d 18hThu 5 Nov, 19:00 UTCFW
35d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Wed 21 OctSun 18 OctFri 16 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-S14185-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 10:45 UTC7d ago
1
–
running
0
Sun 18 Oct, 01:50 UTC10d ago
1
held half
3.4 days
0
Fri 16 Oct, 20:56 UTC12d ago
1
–
1.2 days
0
Wed 14 Oct, 20:34 UTC14d ago
1
held half
2 days
1
Sat 3 Oct, 03:22 UTC25d ago
1
halved by day 2
11.7 days
0
Thu 1 Oct, 19:03 UTCFW27d ago
1
–
1.3 days
0
Wed 30 Sep, 20:43 UTC28d ago
1
–
0.9 days
1
Wed 30 Sep, 10:31 UTC28d ago
1
–
0.4 days
1
Mon 28 Sep, 17:22 UTC30d ago
1
–
1.7 days
0
Mon 28 Sep, 08:14 UTC30d ago
1
–
0.4 days
0
Sun 27 Sep, 07:08 UTC31d ago
1
–
1 days
0
Fri 25 Sep, 20:08 UTC33d ago
1
–
1.5 days
0
Fri 25 Sep, 10:09 UTC33d ago
1
–
0.4 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-S14185-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is Test Server online, and what uptime has been recorded?
Test Server is offline at this moment; 2 days 15 hours ago is when it was last seen. 4 of 168 hours up over the last 7 full days, which is 2% of the time. First seen by Rust Graphs on 24 September 2026.
2.
In which location is Test Server hosted?
With its NA tag, Test Server lists itself in North America. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 66.51.98.52:28005.
3.
What Rust version is recorded for Test Server?
On Linux, Test Server runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.
Population
4.
How many players are plotted on Test Server?
No response from Test Server; the server was last seen 2 days 15 hours ago. The seven-day mean is 0 players; the peak over the same period is 1.
5.
What rank has been recorded for Test Server?
Across seven days, player hours give Test Server #14,185 globally and #1,442 in North America, a top 64% position among ranked servers.
Wipe data
6.
What is recorded on Test Server on wipe day?
At their busiest, its recent wipes drew 1 players on average. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 67% of its recent wipes stayed above half that peak. By day 2 the crowd had fallen below half on the wipes where it did not hold.
7.
On Test Server, when do wipes occur?
At Test Server the only wipe is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The world it runs now was made 7 days 13 hours ago. Its tags give a wipe schedule of one wipe per month.
Rules and settings
8.
Which rules and settings are recorded for Test Server?
The name of Test Server records no gather rate. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
9.
What is the map for Test Server?
Size 5,800 with seed 1337: that is the procedural map Test Server runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.
Tags
10.
Where does Test Server appear among the Rust Graphs lists and filters?
These Rust Graphs lists include Test Server: Modded Rust servers and Rust server list: North America. These filters on the server list return it: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
11.
Which meaning is attached to each tag on Test Server?
Tags published by Test Server, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; NA (North America): The server browser lists it under North America. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
12.
How is Test Server joined?
Enter client.connect 66.51.98.52:28005 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-S14185-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp50
Max playersThe slot count is 50.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Wipe schedule
^m
MonthlyMonthly wipes, on Facepunch's force wipe.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Region
NA
North AmericaThe server browser lists it under North America.
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.
KeyTag string decodedRG-S14185-10 · Sheet 10 of 10