Test
Offline 176.6.74.76:28015 checked 15d 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 69% 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- 377/425
- 23/250
- 44/250
- 177/200
- 68/200
- 76/100
Quick answers
from the figures on this pageWipe schedule
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. The world in play was created 15 days 10 hours ago.
Tags
How should you read the tags on Test?
Check: tags. The game's server browser reads 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): 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): Region code: none set from Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Test appear in Rust Metrics lists and filters?
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.
Population
Where does Test sit in the rankings?
Player hours over seven days put Test at #14,976, in the top 69% of all ranked servers.
What player count does Test carry?
Status for Test: offline. Last seen 15 days 2 hours ago.
Operator and location
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. The endpoint you need is 176.6.74.76:28015.
What Rust version is Test on?
Rust network protocol 2634 and build 167584 on Windows is the build Test runs. Matching protocol is required to join. Let Steam update your game.
Is Test up, and how often does it stay up?
Test reports offline. The last reading came 15 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 12 October 2026, recorded by Rust Metrics.
Settings and map
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
The game generates a procedural map for Test.
Connection
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 176.6.74.76:28015. Or press Launch Rust here and Steam opens the game and connects you.