Local audit validation
Key statistics
the figures behind the quote- Players now
- 0/ ? slots not published
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,960 top 71%
- Rank · 7d ago
- #16,709 ▲749 places up
- Last wipe
- 9d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 4 Oct 2026 no hostname published
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
Wipes
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 86/300 | ▼−39−31.1% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 91/225 | ▼−4−4.3% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 90/100 | ▼−1−0.7% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 26/1000 | ▼−28−52.1% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 7/1000 | ▼−15−67.6% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 28/700 | ▼−55−66.4% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Local audit validation?
The name of Local audit validation carries no gather rate. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.
Which map is played on Local audit validation?
Local audit validation uses a procedural map, which the game generates.
Population
What is the rank of Local audit validation?
For the last seven days, Local audit validation holds rank #15,960 on player hours, in the top 71% of all ranked servers.
How full is Local audit validation?
At present, Local audit validation is offline; the last sighting was 15 hours ago. Average players over the last seven days: 0.
Wipe Frequency
When does Local audit validation schedule its wipes?
The record holds too few of Local audit validation's wipes to establish its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 9 days 17 hours.
Server Overview
What is the location of Local audit validation?
There is no region published for Local audit validation. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 78.63.13.236:28175 is its address.
What Rust version is Local audit validation running?
Rust network protocol 2634 and build 167584 on Windows is what Local audit validation runs. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of Local audit validation?
Offline at this moment: Local audit validation. Last seen 15 hours ago. 10% is its uptime for the last 7 full days, 16 of 168 hours. The earliest Rust Analytics saw it was 4 October 2026.
Tags and Rankings
What is the meaning of the tags on Local audit validation?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp0 (Max players): It holds 0 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167584 (Build): Game build: 167584; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Local audit validation publishes. Also in the tags and at the top of this page: current players, queue and world creation time.
On Rust Analytics, which lists and filters feature Local audit validation?
The following Rust Analytics lists feature Local audit validation: 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; Last wipe: In the last 2 weeks.
Connection
How can I connect to Local audit validation?
Type client.connect 78.63.13.236:28175 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp0,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z
Game
gmrust
mp0
ts8
v2634
cs167584
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.