Test
Offline 95.24.102.22:28015 checked 33d 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 71% 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- 616/700
- 41/250
- 76/250
- 316/400
- 140/200
- 138/225
Quick answers
from the figures on this pageWipe schedule
When does Test wipe?
The rhythm of Test's wipes cannot be told yet: too few are on record. 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 33 days 5 hours ago.
Lists and filters
How should you read the tags on Test?
Tags published by Test, read by the game's server browser: 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; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. 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?
Rust Metrics lists featuring Test: 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: #16,032 on seven-day player hours, top 71% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 33 days 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. Connect using 95.24.102.22:28015.
What Rust version is Test on?
Version check: Rust network protocol 2633 and build 165217 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 33 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 24 September 2026.
Settings and map
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — 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.
Which map is live on Test?
The game generates a procedural map for Test.
Connection
What do you do to join Test?
Press F1 in Rust and enter client.connect 95.24.102.22:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.