TST15990
TEST
Offline 93.123.46.57:28015 checked 22d 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 221/250
-
02COMPlayers 136/200
-
03COMPlayers 27/250
-
04COMPlayers 17/250
-
05COMPlayers 25/100
-
06COMPlayers 27/225
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry TEST?
Community servers, no tags — the Rust Tracker lists that include TEST. It comes up under these filters 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?
Listed for the server browser to read, TEST publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs166652 (Build): This server runs game build 166652; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not 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 Schedule
When does TEST wipe?
Too few wipes on record for TEST to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 22 days 13 hours since this world was made.
Server Details
What is the uptime on TEST, and is it online?
Tracking shows TEST offline as of now, last seen 22 days 8 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 6 October 2026.
Which Rust build is TEST running?
Confirmed for TEST: Rust network protocol 2634 and build 166652, Windows. Steam updates it for you; your game must share the protocol to join.
What location is TEST hosted in?
No region is published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 93.123.46.57:28015.
Population
How many players are on TEST right now?
Offline now for TEST, last seen 22 days 8 hours ago.
Where does TEST sit in the server rankings?
Seven-day player hours put TEST at #15,990, within the top 71% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on TEST?
Nothing in TEST's name states a gather rate. Up to 8 players per group, the game's default. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. A community server: the server browser lists it under Community. On: VAC, Valve's anti-cheat.
What map is TEST on?
Procedural map on TEST, made by the game.
How to Join
Which steps join TEST?
To connect: start Rust, press F1, enter client.connect 93.123.46.57: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?,v2634,gmrust,cs166652,ts8
Game
gmrust
mp10
ts8
v2634
cs166652
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.