TST13608
Test
Offline 89.58.33.175:28015 checked 16d 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 62% 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 827/850
-
02COMPlayers 57/250
-
03COMPlayers 133/250
-
04COMPlayers 517/575
-
05COMPlayers 322/350
-
06COMPlayers 233/325
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show Test?
On Rust Tracker, Test sits in these lists: Community servers, no tags. On the server list, these filters bring it up: 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): Standard survival mode for Rust; mp2 (Max players): 2 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs167058 (Build): The game build is 167058; 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 Times
When does Test wipe?
Too few wipes on record for Test to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. Its world went live 19 days 20 hours.
Location and Status
Is Test up, and how does its uptime hold?
Offline: Test confirmed offline, last seen 16 days 5 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 11 October 2026.
What Rust version is Test on?
Confirmed for Test: Rust network protocol 2634 and build 167058, 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 89.58.33.175:28015.
Population
What is the player count on Test?
Offline: Test, last seen 16 days 5 hours ago.
How does Test compare in the rankings?
Seven-day player hours put Test at #13,608, within the top 62% of all ranked servers.
Settings
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. Raiding and PvP are permitted between players. Listed under Community in the server browser, it is a community server. On: VAC, Valve's anti-cheat.
Which map is loaded on Test?
Generated by the game: the procedural map on Test.
Connect
How do you get onto Test?
Open the console in Rust with F1 after starting the game, then type client.connect 89.58.33.175:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp2,ptrak,$r?,v2634,gmrust,cs167058,ts8
Game
gmrust
mp2
ts8
v2634
cs167058
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.