Offline 173.214.174.22:29015 checked 16d ago
Rust Repair Validation
Connect
srv = rust.server("173.214.174.22:29016")
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
- 173.214.174.22:29015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 00:34 UTC
- hostname
- –
- first seen
- 13 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 | 183/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 28/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 267/700 |
Quick answers
From the figures on this page.
Population
How does Rust Repair Validation compare in the rankings?
Over the last seven days Rust Repair Validation sits at #15,441 on player hours, in the top 71% of ranked servers.
How full does Rust Repair Validation run?
Rust Repair Validation returns no live count at this refresh, having last been seen 16 days 12 hours ago.
Server facts
Which Rust version is Rust Repair Validation on?
The build is Rust network protocol 2634 and build 167584 on Windows, run by Rust Repair Validation. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Rust Repair Validation, and is it online now?
Rust Repair Validation is offline at this refresh; the last response came 16 days 12 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 13 October 2026.
In which location is Rust Repair Validation hosted?
There is no region published for Rust Repair 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 173.214.174.22:29015.
Rules, settings, map
Which settings and rules does Rust Repair Validation run?
No gather rate appears in the name: Rust Repair Validation. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Rust Repair Validation?
A procedural map runs on Rust Repair Validation, generated by the game.
Wipes and dates
On what schedule does Rust Repair Validation wipe?
Too few wipes are on record for Rust Repair 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. A new world was started 16 days 12 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold Rust Repair Validation, and which filters?
On Rust Data, Rust Repair Validation 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 Rust Repair Validation hold?
These tags are published by Rust Repair Validation and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): Recorded game build: 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Rust Repair Validation?
In Rust, F1 opens the console: type client.connect 173.214.174.22:29015. Launch Rust on this page does the same by opening the game through Steam and connecting.