Local audit validation
Offline 78.63.13.236:28175 checked 15d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
Population
How does Local audit validation rank against other Rust servers?
Over the past week it ranks #15,312 for player hours, which puts Local audit validation in the top 71% of all ranked servers.
How busy is Local audit validation?
We have no live count for Local audit validation right now. It was last seen 15 days 14 hours ago.
Lists and tags
What do the server tags on Local audit validation mean?
These are the tags Local audit validation publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167584 (Build): This server runs game build 167584; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include Local audit validation?
Local audit validation appears among the Rust Population lists that follow: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Wipe schedule
What is the wipe schedule on Local audit validation?
Too few wipes are on record for Local audit validation to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 24 days 16 hours ago.
Settings
Which map does Local audit validation run?
Local audit validation uses a map the game generates: procedural.
What are the rules and settings on Local audit validation?
The name tells you nothing about gather rates: Local audit validation states none. No limit is set beyond the standard 8 players per group. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. Modded is its browser category: plugins or settings change the game. Oxide plugins are in use here. VAC, Valve's anti-cheat, runs here.
About the server
Which version of Rust does Local audit validation run?
On Windows, Local audit validation runs Rust network protocol 2634 and build 167584. Your game needs the same protocol to join; 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 14 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. It was first seen by Rust Population on 4 October 2026.
Where is Local audit validation located?
No region is published by Local audit validation. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 78.63.13.236:28175.
How to join
How do I join Local audit validation?
To connect directly, open Rust's console with F1 and type client.connect 78.63.13.236:28175; or press Launch Rust on this page and Steam opens Rust and joins for you.