Offline 66.9.164.218:28415 checked 29d ago
xJermelz's v0.8.4 MultiMonument Test
Connect
srv = rust.server("66.9.164.218:28416")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 66.9.164.218:28415
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 18:48 UTC
- hostname
- –
- first seen
- 29 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 150/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 191/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 93/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 216/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 344/350 |
Quick answers
From the figures on this page.
Population data
What position does xJermelz's v0.8.4 MultiMonument Test take in the server rankings?
Rank #16,837 on seven-day player hours for xJermelz's v0.8.4 MultiMonument Test, within the top 71% of all ranked servers.
How many players does xJermelz's v0.8.4 MultiMonument Test hold at once?
xJermelz's v0.8.4 MultiMonument Test returns no live count at this refresh, having last been seen 29 days 15 hours ago.
Server facts
Which Rust version is xJermelz's v0.8.4 MultiMonument Test on?
Rust network protocol 2633 and build 165217 on Windows is what xJermelz's v0.8.4 MultiMonument Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is xJermelz's v0.8.4 MultiMonument Test, and is it online now?
Offline now for xJermelz's v0.8.4 MultiMonument Test, last seen 29 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 29 September 2026.
Where does xJermelz's v0.8.4 MultiMonument Test sit?
No region is published by xJermelz's v0.8.4 MultiMonument Test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 66.9.164.218:28415.
Settings and map
What rules and settings are recorded for xJermelz's v0.8.4 MultiMonument Test?
The name xJermelz's v0.8.4 MultiMonument Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has xJermelz's v0.8.4 MultiMonument Test loaded?
A procedural map runs on xJermelz's v0.8.4 MultiMonument Test, generated by the game.
Wipe data
When does xJermelz's v0.8.4 MultiMonument Test wipe, and how often?
Too few wipes are on record for xJermelz's v0.8.4 MultiMonument Test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 31 days 23 hours ago.
Tags, lists
Where does xJermelz's v0.8.4 MultiMonument Test appear among Rust Data lists and filters?
On Rust Data, xJermelz's v0.8.4 MultiMonument Test appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on xJermelz's v0.8.4 MultiMonument Test?
The game's server browser reads these tags from xJermelz's v0.8.4 MultiMonument Test: gmvanilla (Game mode): The mode is vanilla survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to xJermelz's v0.8.4 MultiMonument Test?
In Rust, F1 opens the console: type client.connect 66.9.164.218:28415. Launch Rust on this page does the same by opening the game through Steam and connecting.