Test
Offline 176.6.23.60:28015 checked 13d ago
Server instruments
no direct query in 48 hoursPlayers now
100% 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 60% 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- 163/250
- 107/200
- 16/250
- 16/250
- 15/100
- 19/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
To tell the rhythm of Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 16 days 12 hours ago the current world was made.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Build 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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. 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.
Occupancy
Where does Test sit in the rankings?
Ranking for Test: #12,905 on seven-day player hours, top 60% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 13 days 22 hours ago.
Operator and location
Where does Test sit?
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 176.6.23.60:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 167584, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Test reports offline. The last reading came 13 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 14 October 2026.
Settings and map
How is Test configured, and what rules are in force?
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. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on Test?
The game generates a procedural map for Test.
Join
How can you get onto Test?
Check: join. Open Rust, press F1, then enter client.connect 176.6.23.60:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.