Test
Offline 62.226.100.227:28015 checked 43d 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 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- 137/250
- 125/200
- 14/250
- 18/250
- 12/100
- 35/200
Quick answers
from the figures on this pageWipe timing
When does Test wipe?
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. 45 days 12 hours ago the current world was made.
Tags
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; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty 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?
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.
Player count
Where does Test sit in the rankings?
Player hours over seven days put Test at #14,180, in the top – of all ranked servers.
What player count does Test carry?
Status for Test: offline. Last seen 43 days 6 hours ago.
Server
Where does Test sit?
Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 62.226.100.227:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.
Is Test up, and how often does it stay up?
Check: connection. Test is offline at this moment. Last contact was 43 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is Test configured, and what rules are in force?
No gather rate appears in the name: Test. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is Test on?
The game generates a procedural map for Test.
How to join
What do you do to join Test?
Press F1 in Rust and enter client.connect 62.226.100.227:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.