Local audit validation
Offline 78.63.13.236:28175 checked 15d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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.
Li4Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What is the wipe schedule on Local audit validation?
Its rhythm cannot yet be told: too few of Local audit validation's wipes are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 24 days 6 hours ago.
Player counts
How busy is Local audit validation?
The last time Local audit validation was seen was 15 days 4 hours ago, and it is offline now.
How does Local audit validation rank against other Rust servers?
The top 71% of ranked servers includes Local audit validation, at #15,312 for player hours over the last seven days.
Rules and settings
Which map does Local audit validation run?
Local audit validation runs a procedural map, which the game generates.
What are the rules and settings on Local audit validation?
The name Local audit validation does not specify a gather rate. 8 players is the default group size, and that is the limit here. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does Local audit validation run?
Rust network protocol 2634 and build 167584 on Windows is what Local audit validation runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Local audit validation online, and how reliable is it?
Offline at the moment: Local audit validation was last seen 15 days 4 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. It first appears in Rust Heatmap records on 4 October 2026.
Where is Local audit validation located?
No region is published by Local audit validation. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 78.63.13.236:28175.
Lists and filters
Which Rust Heatmap lists and filters include Local audit validation?
The Rust Heatmap lists that Local audit validation fits are: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more brings it up.
What do the server tags on Local audit validation mean?
These are the tags Local audit validation publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp0 (Max players): This server has 0 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, run the same version: game protocol 2634; cs167584 (Build): The game build here is 167584; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join Local audit validation?
Press F1 in Rust to open the console, then enter client.connect 78.63.13.236:28175. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.