Test
Offline 176.6.61.1:28015 checked 21d 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 72% 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- 158/250
- 101/200
- 14/250
- 16/250
- 12/100
- 17/200
Quick answers
from the figures on this pageReset cycle
How often does Test wipe, and when?
The rhythm of Test's wipes cannot be told yet: too few 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. The world in play was created 1782 days 2 hours ago.
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): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; v2323 (Protocol): Your game must run protocol 2323 to get in; ptrak (Networking): RakNet carries the traffic, as standard for Rust; he8c2d43f (Custom tag): This tag is non-standard, added by the owner or a plugin; stok (Custom tag): This tag is non-standard, added by the owner or a plugin. 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?
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.
Player count
Where does Test sit in the rankings?
Ranking for Test: #15,948 on seven-day player hours, top 72% of all ranked servers.
How full does Test get?
Test is not responding; status offline, last seen 21 days 15 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. The endpoint you need is 176.6.61.1:28015.
What Rust version is Test on?
Rust network protocol 2323 on Windows is the build Test runs. Matching protocol is required to join. Let Steam update your game.
How reliable is Test, and is it online now?
Reading: offline. Test last answered 21 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 6 October 2026.
Rules and settings
How is Test configured, and what rules are in force?
Reading the name gives no gather rate for Test. No group limit is published. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
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 176.6.61.1:28015. Or press Launch Rust here and Steam opens the game and connects you.