DWG RG-S0000Server sheetchecked 46d ago
Test Server
Offline 109.200.242.137:28015 checked 46d 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
Server data
Is Test Server online, and what uptime has been recorded?
Test Server is offline at this moment; 46 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. First seen by Rust Graphs on 13 September 2026.
In which location is Test Server hosted?
There is no region published by Test Server. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 109.200.242.137:28015 is its address.
What Rust version is recorded for Test Server?
On Windows, Test Server runs Rust network protocol 2633 and build 163794. The same protocol is required for joining, and Steam updates your game to it.
Population
What does the population history show for Test Server?
Test Server is not responding at the latest refresh; the last record of it online is 46 days 5 hours ago.
Wipe data
On Test Server, when do wipes occur?
The record of Test Server's wipes is too short to tell its rhythm. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 46 days 13 hours ago.
Settings
What settings and rules apply on Test Server?
Gather rate for Test Server: 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. PvP and raiding are on. The server browser lists it under Community. VAC is on: that is Valve's anti-cheat.
On which map is Test Server played?
A procedural map, generated by the game, is what Test Server runs.
Filters
On Rust Graphs, which lists and filters contain Test Server?
The Rust Graphs lists that carry Test Server 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 Server?
The game's server browser reads these tags from Test Server: gmrust (Game mode): Standard survival, as Rust plays; mp500 (Max players): Slots: 500; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): To join, your game must be on protocol 2633; cs163794 (Build): Build: 163794; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Joining the server
By what method do you join Test Server?
Enter client.connect 109.200.242.137: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 mp500,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp500
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.