DWG RG-S15497Server sheetchecked 35d ago
test
Offline 47.93.210.25:28015 checked 35d 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 67% 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
Server details
Is test online, and what uptime has been recorded?
The current state of test is offline, with the last sighting 35 days 16 hours ago. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
In which location is test hosted?
There is no region published by test. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 47.93.210.25:28015.
On which Rust version is test running?
Rust network protocol 2633 and build 162929 on Windows: that is what test runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
What does the population history show for test?
No response from test; the server was last seen 35 days 16 hours ago.
What rank has been recorded for test?
Within the top 67% of all ranked servers: test at #15,497 for player hours, seven days recorded.
Wipe times
On test, when do wipes occur?
test's rhythm cannot be told yet: too few of its wipes are on record. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 54 days 5 hours ago the current world was made.
Map and rules
Which settings does test run, and what rules?
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. Raiding and player combat are permitted. It appears under Community in the server browser. VAC is on: that is Valve's anti-cheat.
On which map is test played?
A procedural map, generated by the game, is what test runs.
Filters
Where does test appear among the Rust Graphs lists and filters?
These Rust Graphs lists include test: Rust community servers, plotted. On the server list, these filters bring it up: 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: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): Join only if your game is on protocol 2633; cs162929 (Build): Build: 162929; 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
By what method do you join test?
In Rust, press F1 and type client.connect 47.93.210.25:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
Server tags
Published as mp50,ptrak,$r?,v2633,gmvanilla,cs162929,ts8
Game
gmvanilla
mp50
ts8
v2633
cs162929
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.