TST16490
test
Offline 209.198.153.138:20000 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 287/300
-
02COMPlayers 228/250
-
03COMPlayers 21/250
-
04COMPlayers 23/250
-
05COMPlayers 27/100
-
06COMPlayers 110/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. 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?
These tags are published by test for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams cap at 8; this is the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs165217 (Build): Build: 165217; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set. 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 Schedule
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. Its world went live 47 days 18 hours.
Server Details
Is test up, and how does its uptime hold?
Offline: test confirmed offline, last seen 33 days 11 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 24 September 2026.
Which Rust build is test running?
Confirmed for test: Rust network protocol 2633 and build 165217, Windows. The same protocol is required to join, and Steam updates it for you.
Where does test sit?
No region is published by test. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 209.198.153.138:20000.
Player Count
Is test busy?
Offline now for test, last seen 33 days 11 hours ago.
What rank does test carry among Rust servers?
On player hours over seven days, test ranks #16,490, inside the top 71% of all ranked servers.
Settings
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. Off: VAC, Valve's anti-cheat.
What map is test on?
Generated by the game: the procedural map on test.
How to Join
Which steps join test?
Open the console in Rust with F1 after starting the game, then type client.connect 209.198.153.138:20000. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp10
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.