Station XX-16837 · no signal
xJermelz's v0.8.4 MultiMonument Test
Offline 66.9.164.218:28415 checked 29d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,837
- top 71%
- Last wipe
- 31d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M –not enough readings
Players
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on xJermelz's v0.8.4 MultiMonument Test?
xJermelz's v0.8.4 MultiMonument Test uses a procedural map, which the game generates.
Which settings and rules apply on xJermelz's v0.8.4 MultiMonument Test?
No gather rate appears in the name of xJermelz's v0.8.4 MultiMonument Test. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on xJermelz's v0.8.4 MultiMonument Test?
xJermelz's v0.8.4 MultiMonument Test is not responding at this moment and is offline, last seen 29 days 14 hours ago.
How does xJermelz's v0.8.4 MultiMonument Test rank against other Rust servers?
The last seven days of player hours place xJermelz's v0.8.4 MultiMonument Test at #16,837, in the top 71% of all ranked servers.
Server details
How reliably does xJermelz's v0.8.4 MultiMonument Test stay online?
No contact with xJermelz's v0.8.4 MultiMonument Test right now, and the last recorded contact was 29 days 14 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 29 September 2026 is when Rust Server Trends first recorded it.
Where in the world is xJermelz's v0.8.4 MultiMonument Test hosted?
Nothing about a region comes from xJermelz's v0.8.4 MultiMonument Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 66.9.164.218:28415.
Which Rust version is xJermelz's v0.8.4 MultiMonument Test running?
On Windows, xJermelz's v0.8.4 MultiMonument Test runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does xJermelz's v0.8.4 MultiMonument Test wipe, and on which days?
Too few wipes of xJermelz's v0.8.4 MultiMonument Test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 31 days 21 hours is how long the current world has been running.
Server tags
What do the server tags on xJermelz's v0.8.4 MultiMonument Test mean?
The game's server browser reads the tags xJermelz's v0.8.4 MultiMonument Test publishes: gmvanilla (Game mode): Survival in vanilla mode; mp5 (Max players): Slots: 5; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): Game build: 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does xJermelz's v0.8.4 MultiMonument Test appear?
The Rust Server Trends lists that take in xJermelz's v0.8.4 MultiMonument Test are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto xJermelz's v0.8.4 MultiMonument Test?
To join, enter client.connect 66.9.164.218:28415 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.