TST15050
TEST
Offline 188.19.173.245: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
daily · 1 is bestWipe 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 330/375
-
02COMPlayers 220/250
-
03COMPlayers 37/250
-
04COMPlayers 31/250
-
05COMPlayers 55/100
-
06COMPlayers 78/200
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show TEST?
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.
Which tags does TEST carry, and what do they mean?
The game's server browser reads these tags from TEST: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Slots: 10; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs163794 (Build): Build: 163794; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Times
On what schedule does TEST wipe?
TEST's rhythm cannot be told yet: too few wipes on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 44 days 14 hours.
Location and Status
What is the uptime on TEST, and is it online?
Offline: TEST confirmed offline, last seen 44 days 13 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. Rust Tracker logged it first on 14 September 2026.
What Rust version is TEST on?
Confirmed for TEST: Rust network protocol 2633 and build 163794, Windows. Steam updates it for you; your game must share the protocol to join.
Where does TEST sit?
Region: none published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 188.19.173.245:28015.
Population
What is the player count on TEST?
Last seen 44 days 13 hours ago; TEST is offline at present.
Where does TEST sit in the server rankings?
Seven-day player hours put TEST at #15,050, within the top – of all ranked servers.
Map and Rules
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. A community server: the server browser lists it under Community. On: VAC, Valve's anti-cheat.
Which map is loaded on TEST?
Procedural map on TEST, made by the game.
Connect
Which steps join TEST?
To connect: start Rust, press F1, enter client.connect 188.19.173.245:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
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.