Test
Offline 176.6.0.43:28015 checked 12d 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 63% 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- 216/250
- 14/250
- 17/250
- 125/200
- 43/200
- 39/100
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 monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 15 days 15 hours ago the current world was made.
Tags
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; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Build 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.
Which lists and filters on Rust Metrics show Test?
These Rust Metrics lists carry 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
What position does Test hold among Rust servers?
Ranking for Test: #13,592 on seven-day player hours, top 63% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 12 days 13 hours ago.
Server
What location is Test hosted in?
Reading: location. Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 176.6.0.43: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?
Reading: offline. Test last answered 12 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 October 2026, recorded by Rust Metrics.
Settings and map
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is Test on?
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.0.43:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.