Test
Offline 5.18.236.67:28015 checked 39d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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 bestWipe 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- 33/500
- 120/100
- 52/225
- 13/700
- 2/200
- 3/1000
Quick answers
from the figures on this pageWipe timing
When does Test wipe?
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 it runs now was made 67 days 21 hours ago.
Tags
Which tags does Test carry, and what do they mean?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; v2556 (Protocol): Protocol 2556: join only on the same game version; cs104071 (Build): Build 104071; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $reu2 (Region code): eu2 is the region code on record; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test appear in Rust Metrics lists and filters?
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.
Occupancy
What position does Test hold among Rust servers?
Ranking for Test: #14,412 on seven-day player hours, top – of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 39 days 10 hours ago.
Operator and location
Where does Test sit?
No region tag on Test, whose region code is eu2. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 5.18.236.67:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2556 and build 104071, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Reading: offline. Test last answered 39 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 September 2026, recorded by Rust Metrics.
Map and rules
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. Check: group limit. None published. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
Check: map. Procedural, generated by the game, on Test.
Join
How can you get onto Test?
Check: join. Open Rust, press F1, then enter client.connect 5.18.236.67:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.