DWG RG-S13043Server sheetchecked 44d ago
test
Offline 5.175.178.27:28015 checked 44d 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
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
What uptime is recorded for test, and is it up?
test is offline at this moment; 44 days 5 hours ago is when it was last seen. 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.
What location is recorded for test?
No region is 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 5.175.178.27:28015.
On which Rust version is test running?
Rust network protocol 2633 and build 163794 on Windows: that is what test runs. To join, your game must be on the same protocol; Steam handles the update.
Population
What player count is recorded on test?
No response from test; the server was last seen 44 days 5 hours ago.
In the rankings, which position does test hold?
Player hours over seven days place test at #13,043, within the top – of ranked servers.
Wipe times
On test, when do wipes occur?
Too few wipes are on record for test to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 45 days 3 hours ago.
Rules and settings
Which settings does test run, and what rules?
The name of test records no gather rate. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Community is its tab in the server browser. Anti-cheat: VAC, from Valve, is off.
What is the map for test?
test runs a procedural map, which the game generates.
Lists and 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.
Which meaning is attached to each tag on test?
gmrust (Game mode): Standard survival, as Rust plays; mp8 (Max players): 8 player slots; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): To join, your game must be on protocol 2633; cs163794 (Build): 163794 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded are the tags 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.
Connect
What is the way to connect to test?
Enter client.connect 5.175.178.27: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.
Server tags
Published as mp8,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp8
ts8
v2633
cs163794
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.