TEST
Offline 94.233.16.77: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 71% 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- 30/500
- 126/100
- 44/225
- 31/700
- 9/200
- 0/500
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. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 17 days 11 hours ago.
Tag meanings
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; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TEST?
These Rust Metrics lists carry TEST: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #15,535, in the top 71% of all ranked servers.
What is the population on TEST?
Status for TEST: offline. Last seen 15 days 12 hours ago.
Server details
Which location does TEST run from?
No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 94.233.16.77:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
Reading: offline. TEST last answered 15 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 11 October 2026.
Settings and map
What settings and rules apply on TEST?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
The game generates a procedural map for TEST.
How to join
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 94.233.16.77:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.