Test
Offline 5.59.105.103:28015 checked 24d 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 70% 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- 390/350
- 200/225
- 22/250
- 26/250
- 111/225
- 38/100
Quick answers
from the figures on this pageReset cycle
When does Test wipe?
The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 28 days 18 hours ago the current world was made.
Tag meanings
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; mp2 (Max players): Slots: 2; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166640 (Build): Build 166640; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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. Check: filters. On the server list it appears under these: 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: #15,998 on seven-day player hours, top 70% of all ranked servers.
How full does Test get?
Reading for Test: offline at this moment; last seen 24 days 19 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 5.59.105.103:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 166640, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is Test up, and how often does it stay up?
Reading: offline. Test last answered 24 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 3 October 2026.
Settings and map
What settings and rules apply on Test?
No gather rate appears in the name: Test. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Check: map. Procedural, generated by the game, on Test.
Join
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 5.59.105.103:28015. Or press Launch Rust here and Steam opens the game and connects you.