Rust Server TrendsSeismic network · station log
Recording Stations11,786 Players66,925 Active3,511 Wipes · 3 h190 48 h

Station XX-15312 · no signal

Local audit validation

Offline 78.63.13.236:28175 checked 15d ago

moddedoxide
Connect
Players now
0/ ?
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,312
top 71%
Last wipe
24d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15312 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of ? slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct14 Oct17 Oct20 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
159/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
128/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
184/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
71/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
15/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
22/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Local audit validation?

Local audit validation uses a procedural map, which the game generates.

Which settings and rules apply on Local audit validation?

The name of Local audit validation gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Local audit validation?

No players are recorded on Local audit validation at this moment; it is offline, and the last sighting was 15 days 18 hours ago.

How does Local audit validation rank against other Rust servers?

On player hours for the past week, Local audit validation sits at #15,312, which puts it inside the top 71% of every ranked server.

Server facts

How reliably does Local audit validation stay online?

As recorded now, Local audit validation is not reachable, the last contact having been 15 days 18 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 4 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Local audit validation hosted?

No region is published by Local audit validation. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 78.63.13.236:28175.

Which Rust version is Local audit validation running?

Local audit validation is running Rust network protocol 2634 and build 167584 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

How often does Local audit validation wipe, and on which days?

The rhythm of Local audit validation cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 24 days 20 hours.

Server tags

What do the server tags on Local audit validation mean?

These are the tags Local audit validation publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp0 (Max players): Slots: 0; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167584 (Build): It runs game build 167584; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Local audit validation appear?

The Rust Server Trends lists that take in Local audit validation are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

How do you connect to Local audit validation?

To join, enter client.connect 78.63.13.236:28175 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp0
Max players Slots: 0.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167584
Build It runs game build 167584.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.