DWG RG-S15341Server sheetchecked 2d ago
Test
Offline 5.42.211.127:28015 checked 2d 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 69% 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 data
What uptime is recorded for Test, and is it up?
Last seen 2 days 14 hours ago; right now Test is offline. 1 of 168 hours up over the last 7 full days, which is 1% of the time. First seen by Rust Graphs on 22 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.42.211.127:28015.
On which Rust version is Test running?
Rust network protocol 2633 and build 164530 on Windows: that is what Test runs. The same protocol is required for joining, and Steam updates your game to it.
Counts
What does the population history show for Test?
No response from Test; the server was last seen 2 days 14 hours ago. The seven-day mean on this server is 0 players.
Against other Rust servers, where is Test placed?
Within the top 69% of all ranked servers: Test at #15,341 for player hours, seven days recorded.
Schedules
What wipe schedule has been recorded for Test?
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 37 days ago.
Map and rules
What settings and rules apply on Test?
No gather rate is stated in the name of Test. 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 on: that is Valve's anti-cheat.
On which map is Test played?
A procedural map, generated by the game, is what Test runs.
Lists and filters
On Rust Graphs, which lists and filters contain Test?
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.
Which meaning is attached to each tag on Test?
gmrust (Game mode): Survival in standard Rust style; mp50 (Max players): 50 player slots; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): To join, your game must be on protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty are the tags Test publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
How to join
What is the way to connect to Test?
Connect with client.connect 5.42.211.127:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp50,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp50
ts8
v2633
cs164530
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.