Offline 129.228.26.174:28115 checked 5d ago
EPIC PvE Local Production Validation
Connect
srv = rust.server("129.228.26.174:28116")
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 69% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 02:22 UTC27d ago | 0 | NaN | running | 0 |
| 1 | Wed 30 Sep, 17:22 UTC28d ago | 0 | NaN | 1.4 days | 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:28115
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 02:27 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 | 127/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 190/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 | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Player counts
How does EPIC PvE Local Production Validation compare in the rankings?
Over the last seven days EPIC PvE Local Production Validation sits at #15,335 on player hours, in the top 69% of ranked servers.
How full does EPIC PvE Local Production Validation run?
Offline now for EPIC PvE Local Production Validation, with the last sample 5 days ago. Over the last seven days it averaged 0 players.
Server data
What is the Rust version on EPIC PvE Local Production Validation?
Rust network protocol 2634 and build 167781 on Windows is what EPIC PvE Local Production Validation runs. Steam updates your game for you, but the protocol must match to join.
Is EPIC PvE Local Production Validation up, and what does its uptime show?
EPIC PvE Local Production Validation is offline at this refresh; the last response came 5 days ago. Uptime of 1% across the last 7 full days: 1 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is EPIC PvE Local Production Validation hosted?
No region is published by EPIC PvE Local Production Validation. Rust Data does not look up where the machine stands; it shows where a server says it is. 129.228.26.174:28115 is its address.
Map and rules
Which settings and rules does EPIC PvE Local Production Validation run?
The name EPIC PvE Local Production Validation 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 the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. Anti-cheat status: VAC on.
Wipe data
When does EPIC PvE Local Production Validation wipe, and on what schedule?
Too few wipes are on record for EPIC PvE Local Production Validation 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 27 days 7 hours ago.
On EPIC PvE Local Production Validation, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does EPIC PvE Local Production Validation appear among Rust Data lists and filters?
The Rust Data lists that EPIC PvE Local Production Validation fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on EPIC PvE Local Production Validation?
These tags are published by EPIC PvE Local Production Validation and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into EPIC PvE Local Production Validation?
In Rust, F1 opens the console: type client.connect 129.228.26.174:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.