Offline 129.228.26.174:29115 checked 20d ago
EPIC PvE Local Staging Validation
Connect
srv = rust.server("129.228.26.174:29116")
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 72% 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 1, 4 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 30 Sep, 18:21 UTC28d ago | 1 | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 129.228.26.174:29115
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 30 Sep 2026, 22:19 UTC
- hostname
- –
- first seen
- 13 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 · 149 on average | 163/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 68/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does EPIC PvE Local Staging Validation rank?
Rank #15,867 on seven-day player hours for EPIC PvE Local Staging Validation, within the top 72% of all ranked servers.
How many players does EPIC PvE Local Staging Validation hold at once?
Offline now for EPIC PvE Local Staging Validation, with the last sample 20 days 23 hours ago.
About the server
What is the Rust version on EPIC PvE Local Staging Validation?
The build is Rust network protocol 2634 and build 166655 on Windows, run by EPIC PvE Local Staging Validation. Steam updates your game for you, but the protocol must match to join.
Is EPIC PvE Local Staging Validation up, and what does its uptime show?
The latest sample has EPIC PvE Local Staging Validation offline, with a last sighting 20 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 13 September 2026.
Where does EPIC PvE Local Staging Validation sit?
No region is published by EPIC PvE Local Staging Validation. 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 129.228.26.174:29115.
Settings and map
Which settings and rules does EPIC PvE Local Staging Validation run?
You will not find a gather rate in the string EPIC PvE Local Staging Validation. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Wipe schedule
When does EPIC PvE Local Staging Validation wipe, and how often?
The record for EPIC PvE Local Staging Validation holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 28 days 13 hours ago.
What is wipe day on EPIC PvE Local Staging Validation like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 4 hours after it began.
Tags, lists
Where does EPIC PvE Local Staging Validation appear among Rust Data lists and filters?
On Rust Data, EPIC PvE Local Staging Validation appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on EPIC PvE Local Staging Validation hold?
These tags are published by EPIC PvE Local Staging Validation and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166655 (Build): Recorded game build: 166655; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join EPIC PvE Local Staging Validation?
In Rust, F1 opens the console: type client.connect 129.228.26.174:29115. Launch Rust on this page does the same by opening the game through Steam and connecting.