Test
Offline 176.6.48.158:28015 checked 14d 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- 394/500
- 234/300
- 43/250
- 30/250
- 68/100
- 81/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. 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 16 days 9 hours ago.
Tag meanings
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): The server runs game build 167584; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Test?
On Rust Metrics, Test sits in these lists: 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 #12,979, in the top 60% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 14 days 9 hours ago.
Server details
Which location does Test run from?
No region tag on Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.6.48.158:28015.
What Rust version is Test on?
Version check: Rust network protocol 2634 and build 167584 on Windows, run by Test. 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 14 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 14 October 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
No gather rate appears in the name: Test. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
The game generates a procedural map for Test.
Join
What do you do to join Test?
Check: join. Open Rust, press F1, then enter client.connect 176.6.48.158:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.