test
Offline 209.198.153.25:20000 checked 26d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 61% 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- 439/475
- 339/375
- 38/250
- 31/250
- 45/100
- 145/200
Quick answers
from the figures on this pageWipe schedule
How often does test wipe, and when?
Its rhythm cannot be told from the wipes of test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 26 days 16 hours ago.
Tag meanings
How should you read the tags on test?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): The server runs game build 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does test appear in Rust Metrics lists and filters?
On Rust Metrics, test sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does test sit in the rankings?
Ranking for test: #13,832 on seven-day player hours, top 61% of all ranked servers.
How full does test get?
Reading for test: offline at this moment; last seen 26 days 14 hours ago.
Server
What location is test hosted in?
No region comes from test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 209.198.153.25:20000.
What Rust version is test on?
Version check: Rust network protocol 2634 and build 166586 on Windows, run by test. Check: protocol. To join, your game must match; Steam handles the update.
Is test up, and how often does it stay up?
Check: connection. test is offline at this moment. Last contact was 26 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 2 October 2026.
Map and rules
What rules does test enforce, and what are its settings?
Reading the name gives no gather rate for test. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.
What map is test on?
The game generates a procedural map for test.
Connection
How do you connect to test?
Check: join. Open Rust, press F1, then enter client.connect 209.198.153.25:20000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.