TST16032
Test
Offline 95.24.102.22:28015 checked 33d 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
daily · 1 is bestTop 71% 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
newest first| 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
The same kind of game, then region, group limit, rate and wipes.
-
01COMPlayers 318/350
-
02COMPlayers 21/250
-
03COMPlayers 38/250
-
04COMPlayers 138/200
-
05COMPlayers 53/200
-
06COMPlayers 51/100
Quick answers
From the figures on this page.
Filters
Where does Test appear in Rust Tracker lists and filters?
These Rust Tracker lists carry Test: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Test?
The game's server browser reads these tags from Test: gmrust (Game mode): Rust survival, standard mode; mp2 (Max players): Slots: 2; ts8 (Group limit): Teams cap at 8; this is the game default; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs165217 (Build): Build: 165217; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
On what schedule does Test wipe?
Test's rhythm cannot be told yet: too few wipes on record. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 33 days 8 hours.
Location and Status
What is the uptime on Test, and is it online?
Offline now, Test was last seen 33 days 3 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. The first sighting by Rust Tracker was 24 September 2026.
What Rust version is Test on?
Confirmed for Test: Rust network protocol 2633 and build 165217, Windows. To join, your game must be on the same protocol; Steam handles the update.
Where does Test sit?
Region: none published by Test. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 95.24.102.22:28015.
Population
What is the player count on Test?
Offline now for Test, last seen 33 days 3 hours ago.
Where does Test sit in the server rankings?
On player hours over seven days, Test ranks #16,032, inside the top 71% of all ranked servers.
Settings
Which settings and rules are confirmed on Test?
No gather rate appears in Test's name. Up to 8 players per group, the game's default. It runs survival, gather, build and raid: the standard game. Players can raid and fight each other here. Listed under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.
Which map is loaded on Test?
Generated by the game: the procedural map on Test.
Connect
Which steps join Test?
Open the console in Rust with F1 after starting the game, then type client.connect 95.24.102.22:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp2
ts8
v2633
cs165217
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.