DWG RG-S14163Server sheetchecked 34d ago
test
Offline 9.246.41.75:20000 checked 34d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
Quick answers
Recorded details
Is test online, and what uptime has been recorded?
Last seen 34 days 7 hours ago; right now test is offline. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 23 September 2026.
In which location is test hosted?
There is no region published by test. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 9.246.41.75:20000.
On which Rust version is test running?
The platform is Windows and the version is Rust network protocol 2633 and build 165217 on test. To join, your game must be on the same protocol; Steam handles the update.
Counts
How many players are plotted on test?
No response from test; the server was last seen 34 days 7 hours ago.
Against other Rust servers, where is test placed?
Player hours over seven days place test at #14,163, within the top 65% of ranked servers.
Wipe data
What wipe schedule has been recorded for test?
Too few wipes are on record for test to show its rhythm. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 46 days 14 hours ago the current world was made.
Settings
Which rules and settings are recorded for test?
Gather rate for test: not stated in the name. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. It appears under Community in the server browser. VAC is off: that is Valve's anti-cheat.
Which map has test loaded?
A procedural map, generated by the game, is what test runs.
Filters
Where does test appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry test are: Rust community servers, plotted. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
On test, what is meant by each tag?
The game's server browser reads these tags from test: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): Slots: 10; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): Your game must match protocol 2633 to join; cs165217 (Build): The game build is 165217; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set. 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
How is test joined?
Enter client.connect 9.246.41.75:20000 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.
Server tags
Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp10
ts8
v2633
cs165217
ptrak
$r?
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.