Station XX-15400 · no signal
LOCAL raid difficulty validation
Offline 89.106.72.63:28125 checked 23h ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,400
- top 69%
- Last wipe
- 23h ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M –not enough readings
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 69% 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on LOCAL raid difficulty validation?
No gather rate appears in the name of LOCAL raid difficulty validation. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on LOCAL raid difficulty validation right now?
LOCAL raid difficulty validation is not responding at this moment and is offline, last seen 23 hours ago. Averaged across the last seven days, the population was 0 players.
How does LOCAL raid difficulty validation rank against other Rust servers?
The last seven days of player hours place LOCAL raid difficulty validation at #15,400, in the top 69% of all ranked servers.
Operator and location
How reliably does LOCAL raid difficulty validation stay online?
As recorded now, LOCAL raid difficulty validation is not reachable, the last contact having been 23 hours ago. 26 October 2026 is when Rust Server Trends first recorded it.
Which region does LOCAL raid difficulty validation run from?
No region is published by LOCAL raid difficulty validation. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 89.106.72.63:28125.
What build of Rust does LOCAL raid difficulty validation use?
On Windows, LOCAL raid difficulty validation runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
How often does LOCAL raid difficulty validation wipe, and on which days?
The rhythm of LOCAL raid difficulty 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. 23 hours is how long the current world has been running.
Tags
What do the server tags on LOCAL raid difficulty validation mean?
Tags published by LOCAL raid difficulty validation and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^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 raid difficulty validation appear?
The Rust Server Trends lists that take in LOCAL raid difficulty 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; Last wipe: In the last 24 hours.
Join the server
What steps get you onto LOCAL raid difficulty validation?
Enter client.connect 89.106.72.63:28125 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.