Local audit validation
Offline 78.63.13.236:28175 checked 15d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
daily · 1 is bestTop 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
every wipe as a delivery, newest first- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- ShockRust | Blue | NoLimit 65 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 122 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 99 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 31 / 700
- RustSpain.com | EU Main 3 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 8 / 1000
Quick answers
From the figures on this page.
Population
How does Local audit validation compare with other Rust servers in the rankings?
A seven-day player-hours count places Local audit validation at #15,312: the top 71% of every ranked server.
What is the current population on Local audit validation?
At the moment Local audit validation is offline, having last been seen 15 days 12 hours ago.
Server rules
Which map is active on Local audit validation?
The map on Local audit validation is procedural, produced by the game.
What settings and rules should you know for Local audit validation?
No gather rate appears in the name of Local audit validation. 8 players is the group limit, since the game's default applies. You get survival here, gather, build and raid, as the standard game goes. Raiding and PvP are both on. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Oxide. VAC, the anti-cheat from Valve, is active.
Operator and location
What location does Local audit validation run from?
There is no region published for Local audit validation. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 78.63.13.236:28175 is its address.
Is Local audit validation up, and how good is its uptime?
The current status for Local audit validation is offline, last seen 15 days 12 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. It was first seen by Rust Wipe Tracker on 4 October 2026.
What Rust version is Local audit validation using?
Rust network protocol 2634 and build 167584 on Windows is what Local audit validation runs. Steam keeps your game updated; it has to be on the same protocol to join.
Wipe schedule
When does Local audit validation wipe? What schedule does it follow?
Its rhythm cannot yet be told: too few of Local audit validation's wipes are on record. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 24 days 14 hours have passed since this world was made.
Tags and listings
Where does Local audit validation appear in Rust Wipe Tracker lists and filters?
You will find Local audit validation on the following Rust Wipe Tracker lists: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is the meaning of the server tags on Local audit validation?
The game's server browser picks up these Local audit validation tags: gmrust (Game mode): The game mode is standard Rust survival; mp0 (Max players): Slot count: 0; ts8 (Group limit): 8 per team, which is the default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): The game build is 167584; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
Connecting
What steps do you take to join Local audit validation?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 78.63.13.236:28175.