Offline 99.127.52.224:28215 checked 17d ago
E2E update test
Connect
srv = rust.server("99.127.52.224:28217")
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 · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 08:57 UTC17d ago | 0 | NaN | running | 0 |
# 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:28215
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 08:57 UTC
- hostname
- –
- first seen
- 4 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 · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 169/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 100/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 244/700 |
Quick answers
From the figures on this page.
Player counts
What position does E2E update test take in the server rankings?
Rank #15,549 on seven-day player hours for E2E update test, within the top 71% of all ranked servers.
What population does E2E update test carry?
The current row shows E2E update test offline; the last response was 17 days 2 hours ago.
About the server
What Rust version does E2E update test run?
Version Rust network protocol 2634 and build 167398 on Linux is reported by E2E update test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is E2E update test, and is it online now?
The latest sample has E2E update test offline, with a last sighting 17 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 4 October 2026.
Which location does E2E update test run from?
There is no region published for E2E update test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 99.127.52.224:28215.
Rules, settings, map
What rules and settings are recorded for E2E update test?
The name E2E update test carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has E2E update test loaded?
A procedural map runs on E2E update test, generated by the game.
Wipe schedule
When does E2E update test wipe, and on what schedule?
Too few wipes are on record for E2E update 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 17 days 6 hours ago.
What is wipe day on E2E update test like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain E2E update test?
The Rust Data lists that E2E update test fits are: 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 E2E update test hold?
These tags are published by E2E update test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
How can I connect to E2E update test?
Enter client.connect 99.127.52.224:28215 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.