Offline 66.9.164.119:28415 checked 17d ago
xJermelz's v0.8.7 Train Test
Connect
srv = rust.server("66.9.164.119: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.119:28415
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 01:39 UTC
- hostname
- –
- first seen
- 11 Oct 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 · 150 on average | 161/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 92/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 246/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 345/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does xJermelz's v0.8.7 Train Test rank?
Player hours over seven days put xJermelz's v0.8.7 Train Test at #15,627, in the top 71% of the ranked set.
How many players does xJermelz's v0.8.7 Train Test hold at once?
xJermelz's v0.8.7 Train Test returns no live count at this refresh, having last been seen 17 days 14 hours ago.
Server facts
Which Rust version is xJermelz's v0.8.7 Train Test on?
Rust network protocol 2634 and build 167398 on Windows is what xJermelz's v0.8.7 Train Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is xJermelz's v0.8.7 Train Test, and is it up?
Offline now for xJermelz's v0.8.7 Train Test, last seen 17 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 11 October 2026.
Which location does xJermelz's v0.8.7 Train Test run from?
For xJermelz's v0.8.7 Train Test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 66.9.164.119:28415.
Map and rules
Which rules apply on xJermelz's v0.8.7 Train Test, and what settings?
The name xJermelz's v0.8.7 Train Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on xJermelz's v0.8.7 Train Test?
The game generates its map: procedural, on xJermelz's v0.8.7 Train Test.
Wipe data
When does xJermelz's v0.8.7 Train Test wipe, and how often?
Too few wipes are on record for xJermelz's v0.8.7 Train Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 27 days 14 hours ago.
Tags and filters
Which Rust Data filters and lists contain xJermelz's v0.8.7 Train Test?
On Rust Data, xJermelz's v0.8.7 Train 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.
Which meanings do the tags on xJermelz's v0.8.7 Train Test hold?
These tags are published by xJermelz's v0.8.7 Train Test and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp5 (Max players): Slot count: 5; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join xJermelz's v0.8.7 Train Test?
In Rust, F1 opens the console: type client.connect 66.9.164.119:28415. Launch Rust on this page does the same by opening the game through Steam and connecting.