Offline 99.127.52.224:28315 checked 16d ago
e8 self-update
Connect
srv = rust.server("99.127.52.224:28317")
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 best
Top 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
- 99.127.52.224:28315
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 17:02 UTC
- hostname
- –
- first seen
- 12 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 · 151 on average | 121/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 76/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
What position does e8 self-update take in the server rankings?
Player hours over seven days put e8 self-update at #15,483, in the top 71% of the ranked set.
How full does e8 self-update run?
e8 self-update returns no live count at this refresh, having last been seen 16 days 23 hours ago.
Server data
Which Rust version is e8 self-update on?
Rust network protocol 2634 and build 167398 on Linux is what e8 self-update runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is e8 self-update, and is it online now?
Offline now for e8 self-update, last seen 16 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 12 October 2026.
Which location does e8 self-update run from?
No region is published by e8 self-update. 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 99.127.52.224:28315.
Rules, settings, map
What rules and settings are recorded for e8 self-update?
The name e8 self-update carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. 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 e8 self-update loaded?
A procedural map runs on e8 self-update, generated by the game.
Wipes and dates
When does e8 self-update wipe, and how often?
A rhythm cannot be read from the wipes of e8 self-update on record, which are too few. 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 17 days 1 hours ago.
Tags and filters
Which lists on Rust Data hold e8 self-update, and which filters?
The Rust Data lists that e8 self-update fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on e8 self-update hold?
These tags are published by e8 self-update and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to e8 self-update?
In Rust, F1 opens the console: type client.connect 99.127.52.224:28315. Launch Rust on this page does the same by opening the game through Steam and connecting.