Test
Offline 171.22.172.200:28015 checked 10d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 64% 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- 147/250
- 125/200
- 14/250
- 18/250
- 13/100
- 38/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 21 days 6 hours ago.
Tag meanings
Which tags does Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
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
What position does Test hold among Rust servers?
Ranking for Test: #14,129 on seven-day player hours, top 64% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 10 days 7 hours ago.
Server
What location is Test hosted in?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 171.22.172.200:28015.
What Rust version is Test on?
Rust network protocol 2634 and build 167781 on Windows is the build Test runs. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Test reports offline. The last reading came 10 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 October 2026, recorded by Rust Metrics.
Rules and settings
How is Test configured, and what rules are in force?
Reading the name gives no gather rate for Test. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
Procedural map on Test, made by the game's generator.
How to join
What do you do to join Test?
Press F1 in Rust and enter client.connect 171.22.172.200:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.