DWG RG-S0000Server sheetchecked 46d ago
TEST
Offline 31.31.27.118: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
Recorded details
What uptime is recorded for TEST, and is it up?
TEST is offline at this moment; 46 days 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. On 13 September 2026 is when Rust Graphs first saw it.
What location is recorded for TEST?
A region is not published by TEST. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 31.31.27.118:28015.
On which Rust version is TEST running?
On Windows, TEST runs Rust network protocol 2633 and build 163794. The same protocol is required for joining, and Steam updates your game to it.
Counts
What player count is recorded on TEST?
No response from TEST; the server was last seen 46 days ago.
Schedules
Which times and days are wipes plotted at on TEST?
The record of TEST'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. 46 days 9 hours ago the current world was made.
Rules and settings
Which rules and settings are recorded for TEST?
Gather rate for TEST: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Community. VAC is on: that is Valve's anti-cheat.
What is the map for TEST?
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.
Which meaning is attached to each tag on TEST?
The game's server browser reads these tags from TEST: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): To join, your game must be on protocol 2633; cs163794 (Build): 163794 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty. 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
How is TEST joined?
Enter client.connect 31.31.27.118: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 mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
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.