Test
Offline 219.100.37.233:28015 checked 1d 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 69% 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- 572/675
- 363/525
- 43/250
- 45/250
- 119/200
- 140/300
Quick answers
from the figures on this pageReset cycle
When does Test wipe?
To tell the rhythm of Test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 2 days 15 hours ago the current world was made.
Lists and filters
How should you read the tags on Test?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Population
Where does Test sit in the rankings?
Ranking for Test: #15,348 on seven-day player hours, top 69% of all ranked servers.
What is the population on Test?
Status for Test: offline. Last seen 43 hours ago. Check: player average. 0 over the last seven days.
Server details
What location is Test hosted in?
No region comes from Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 219.100.37.233:28015.
What Rust version is Test on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Test. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 43 hours ago. Check: first contact. Rust Metrics logged it on 27 October 2026.
Rules and settings
How is Test configured, and what rules are in force?
No gather rate appears in the name: Test. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
The game generates a procedural map for Test.
Join
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 219.100.37.233:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.