DWG RG-S15415Server sheetchecked 41d ago
test
Offline 91.108.0.219:28015 checked 41d 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?
test is offline at this moment; 41 days 15 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 17 September 2026.
What location is recorded for test?
There is no region published by test. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 91.108.0.219:28015.
On which Rust version is test running?
Rust network protocol 2633 and build 164530 on Linux: that is what test runs. Steam updates your game, which must be on the same protocol for you to join.
Counts
How many players are plotted on test?
test is not responding at the latest refresh; the last record of it online is 41 days 15 hours ago.
What rank has been recorded for test?
Within the top – of all ranked servers: test at #15,415 for player hours, seven days recorded.
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 world it runs now was made 55 days 17 hours ago.
Map and rules
Which settings does test run, and what rules?
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. The server browser lists it under Community. Anti-cheat: VAC, from Valve, is on.
Which map has test loaded?
test runs a procedural map, which the game generates.
Tags
Where does test appear among the Rust Graphs lists and filters?
These Rust Graphs lists include test: 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?
The game's server browser reads these tags from test: gmrust (Game mode): Survival in standard Rust style; mp75 (Max players): 75 player slots; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): Your game must match protocol 2633 to join; cs164530 (Build): 164530 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
How is test joined?
In Rust, press F1 and type client.connect 91.108.0.219:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
Server tags
Published as mp75,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp75
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.