Offline 78.63.13.236:28175 checked 15d ago
Local audit validation
Connect
srv = rust.server("78.63.13.236:28177")
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
- 78.63.13.236:28175
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 15:53 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 · 155 on average | 27/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 · 117 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 11/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Local audit validation take in the server rankings?
Over the last seven days Local audit validation sits at #15,312 on player hours, in the top 71% of ranked servers.
How many players does Local audit validation hold at once?
Offline now for Local audit validation, with the last sample 15 days 8 hours ago.
Server facts
Which Rust version is Local audit validation on?
The build is Rust network protocol 2634 and build 167584 on Windows, run by Local audit validation. Steam updates your game for you, but the protocol must match to join.
How reliable is Local audit validation, and is it up?
Offline now for Local audit validation, last seen 15 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 4 October 2026.
Where does Local audit validation sit?
For Local audit validation, no region is published. 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 78.63.13.236:28175.
Rules, settings, map
Which rules apply on Local audit validation, and what settings?
The name Local audit validation carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, 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.
Which map has Local audit validation selected?
Local audit validation runs a procedural map, which the game generates.
Wipe data
When does Local audit validation wipe, and on what schedule?
A rhythm cannot be read from the wipes of Local audit validation on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 24 days 10 hours ago.
Tags, lists
Which Rust Data filters and lists contain Local audit validation?
These Rust Data lists include Local audit validation: 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.
How should you read the server tags on Local audit validation?
The game's server browser reads these tags from Local audit validation: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167584 (Build): Build number: 167584; 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. 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.
Join steps
How can I connect to Local audit validation?
In Rust, F1 opens the console: type client.connect 78.63.13.236:28175. Launch Rust on this page does the same by opening the game through Steam and connecting.