LOCAL raid difficulty validation
Key statistics
the figures behind the quote- Players now
- 0/ 1 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,719 top 70%
- Rank · 7d ago
- #15,333 ▼386 places down
- Last wipe
- 16d 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
- – Custom Map
- First seen
- 26 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW6d ago | – | – | running | – |
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 | STEEL RUST /ДЛЯ НОВИЧКОВ /EU Main 11.11EU · groups of 24+ · monthly · 138 on average | 53/100 | ▼−403−88.4% | |
| 2 | 666 RUST /ДЛЯ НОВИЧКОВ /ПИТЕРСКИЙ 11.11EU · groups of 16+ · monthly · 137 on average | 51/750 | ▼−243−82.7% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 11.11EU · groups of 8+ · weekly · 127 on average | 133/100 | ▲+6+4.3% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 11.11EU · groups of 16+ · monthly · 124 on average | 210/1000 | ▼−81−27.8% | |
| 5 | ShockRust | Blue | NoLimitno group limit · 121 on average | 165/400 | ▼−40−19.3% | |
| 6 | Московская Классика для НовичковEU · groups of 8+ · weekly · 120 on average | 139/300 | ▲+15+11.8% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on LOCAL raid difficulty validation?
No gather rate is given in the name of LOCAL raid difficulty validation. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.
Activity
Where does LOCAL raid difficulty validation sit in the rankings?
In the top 70% of all ranked servers, LOCAL raid difficulty validation is #15,719 on player hours over the last seven days.
What is the population on LOCAL raid difficulty validation?
At present, LOCAL raid difficulty validation is offline; the last sighting was 16 days 17 hours ago.
Wipe Cycle
When does LOCAL raid difficulty validation schedule its wipes?
The record holds too few of LOCAL raid difficulty validation's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 3 December at 19:00 UTC. 16 days 17 hours ago the current world was created.
Server Info
Where can LOCAL raid difficulty validation be found?
There is no region published for LOCAL raid difficulty validation. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 89.106.72.63:28125 is its address.
LOCAL raid difficulty validation is on which Rust version?
The version in use at LOCAL raid difficulty validation: Rust network protocol 2635 and build 168909, on Windows. Your game needs the same protocol to get in; Steam takes care of the update.
How reliable is LOCAL raid difficulty validation and is it currently online?
LOCAL raid difficulty validation is down. The last time we saw it was 16 days 17 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. 26 October 2026 is when Rust Analytics first saw it.
Server Tags
How should you interpret the tags on LOCAL raid difficulty validation?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): Capacity: 1 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2635 (Protocol): To join, your game needs protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded listing applies: plugins or settings change play, which LOCAL raid difficulty validation publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
LOCAL raid difficulty validation appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include LOCAL raid difficulty 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.
Connection
How can I connect to LOCAL raid difficulty validation?
The console route: start Rust, press F1, enter client.connect 89.106.72.63:28125. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp1
ts8
v2635
cs168909
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.