TST014
Test
Offline 89.208.22.43: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 275/350
-
02COMPlayers 23/250
-
03COMPlayers 37/250
-
04COMPlayers 140/200
-
05COMPlayers 52/200
-
06COMPlayers 44/100
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry 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.
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; mp10 (Max players): Slots: 10; ts8 (Group limit): Default team size: 8; v2633 (Protocol): To join, your game must match protocol 2633; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Times
Which wipe times are confirmed for Test?
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. This world has been running 44 days 12 hours.
Server Details
What is the uptime on Test, and is it online?
Offline: Test confirmed offline, last seen 44 days 11 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. The first sighting by Rust Tracker was 13 September 2026.
What Rust version is Test on?
Confirmed for Test: Rust network protocol 2633 and build 163794, Windows. To join, your game must be on the same protocol; Steam handles the update.
What location is Test hosted in?
Region: none published by Test. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 89.208.22.43:28015.
Population
Is Test busy?
Offline now for Test, last seen 44 days 11 hours ago.
Map and Rules
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. A community server: the server browser lists it under Community. On: VAC, 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 89.208.22.43:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
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.