DWG RG-S12998Server sheetchecked 44d ago
TEST
Offline 31.23.183.90: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
Server data
Is TEST online, and what uptime has been recorded?
Last seen 44 days 3 hours ago; right now TEST is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. First seen by Rust Graphs on 14 September 2026.
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.23.183.90:28015.
On which Rust version is TEST running?
Rust network protocol 2633 and build 163794 on Windows: that is what TEST runs. Steam updates your game, which must be on the same protocol for you to join.
Player data
What player count is recorded on TEST?
No response from TEST; the server was last seen 44 days 3 hours ago.
Against other Rust servers, where is TEST placed?
Player hours over seven days place TEST at #12,998, within the top – of ranked servers.
Schedules
On TEST, when do wipes occur?
Too few wipes are on record for TEST to show 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 current world has been in use since 44 days 3 hours ago.
Settings
Which rules and settings are recorded for TEST?
No gather rate is stated in the name of TEST. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. It appears under Community in the server browser. Anti-cheat: VAC, from Valve, is on.
On which map is TEST played?
A procedural map, generated by the game, is what TEST runs.
Tags
Where does TEST appear among the Rust Graphs lists and filters?
On Rust Graphs, TEST is placed in these lists: Rust community servers, plotted. It is returned by these filters on the server list: 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: gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): To join, your game must be on protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty. 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?
In Rust, press F1 and type client.connect 31.23.183.90:28015 in the console. Launch Rust on this page also works: Rust opens 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.