Statistical profileOffline
Local audit validation
78.63.13.236:28175 checked 15d ago
Connect to this server
1. Main points
Players now
0/ ?
7-day average
0
peak –
Rank
#15,312
top 71%
Last wipe
24d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it.
- It ranks #15,312 of all ranked servers, the top 71%, on player hours over the last seven days.
- Its current map went up 24d ago.
2. Players
Figure 1: Players on Local audit validation
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Local audit validation
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Local audit validation
What the server publishes and what was recorded
| Address | 78.63.13.236:28175 |
|---|---|
| Region | – |
| Max players | – |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 4 Oct 2026, 15:53 UTC |
| Hostname | – |
| First seen | 4 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 153 on average | 35 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 59 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3 / 1000 |
10. Quick answers
From the figures on this page.
Wipe details
When does Local audit validation wipe, and how often?
Too few wipes of Local audit validation are on record to establish its rhythm. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. 24 days 12 hours have passed since this world was made.
About the server
Is Local audit validation up, and how well has it held up?
Local audit validation is offline at the time of this release; it was last seen 15 days 10 hours ago. 0 of 168 hours on across the last 7 full days gives an uptime of 0%. It was first seen by Rust Census on 4 October 2026.
In which location is Local audit validation based?
A region is not published by Local audit validation. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. At 78.63.13.236:28175 it is addressed.
Which Rust version is Local audit validation running?
This release lists Local audit validation on Rust network protocol 2634 and build 167584, running on Windows. Steam updates your game for you, but it has to be on the same protocol to join.
Player figures
What are the current player figures for Local audit validation?
At this release Local audit validation is offline, having last been seen 15 days 10 hours ago.
What position does Local audit validation hold in the server rankings?
The rank for Local audit validation is #15,312 on seven-day player hours, in the top 71% of ranked servers.
Tags, lists
Where does Local audit validation appear among the Rust Census lists and filters?
The Rust Census lists that Local audit validation fits are: Modded Rust servers, counted. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Local audit validation carry?
gmrust (Game mode): Survival play, in the standard Rust format; mp0 (Max players): 0 slots are available; ts8 (Group limit): This is the game default: 8 to a team; v2634 (Protocol): Your game must run protocol 2634 to join; cs167584 (Build): The server runs game build 167584; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): This server is listed as modded, with plugins or settings that change the game are the tags Local audit validation publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
What map is listed for Local audit validation?
Local audit validation runs a procedural map, which the game generates.
On Local audit validation, what rules and settings are in force?
No gather rate is recorded for Local audit validation in its name. 8 players is the group limit, the game's default. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Connecting
What steps are needed to join Local audit validation?
You can open the console in Rust with F1 and enter client.connect 78.63.13.236:28175; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp0,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp0 | Max players 0 slots are available. |
ts8 | Group limit This is the game default: 8 to a team. |
v2634 | Protocol Your game must run protocol 2634 to join. |
cs167584 | Build The server runs game build 167584. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
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.