LOCAL raid difficulty validation
Offline 89.106.72.63:28125 checked 2d ago
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
Top 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
| 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.
Quick answers
From the figures on this page.
Rules and settings
On LOCAL raid difficulty validation, which rules and settings apply?
The name of LOCAL raid difficulty validation does not state a gather rate. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Tags and filters
On Rust Server Index, which lists and filters carry LOCAL raid difficulty validation?
These lists on Rust Server Index take LOCAL raid difficulty validation: Modded Rust servers, filed by play style. Filed 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 3 days.
How should you read the tags listed for LOCAL raid difficulty validation?
Filed under these tags, as published by LOCAL raid difficulty validation and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp1 (Max players): Player cap: 1; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): The game build here is 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): A region code is absent; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
How often is LOCAL raid difficulty validation wiped, and on what schedule?
Its rhythm is not yet clear, since the record holds too few of LOCAL raid difficulty validation's wipes. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 2 days 4 hours.
Player counts
Where does LOCAL raid difficulty validation sit in the rankings?
The seven-day player-hours ranking places LOCAL raid difficulty validation at #15,353, among the top 69% of ranked servers.
How many players are on LOCAL raid difficulty validation at the moment?
The last check found LOCAL raid difficulty validation offline, last seen 2 days 4 hours ago. Filed under seven-day average: 0 players.
Server details
Which Rust build is LOCAL raid difficulty validation running?
Rust network protocol 2635 and build 168909, on Windows, is what LOCAL raid difficulty validation runs. To join you need the same protocol; Steam handles the update.
How reliable is LOCAL raid difficulty validation, and is it online now?
As of now LOCAL raid difficulty validation is offline, with its last appearance 2 days 4 hours ago. It was up 0 of 48 hours across the last 2 full days, or 0% of the time. It was first recorded by Rust Server Index on 26 October 2026.
Where in the world is LOCAL raid difficulty validation hosted?
LOCAL raid difficulty validation gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 89.106.72.63:28125.
Connecting
How can you connect to LOCAL raid difficulty validation?
Two ways in. Type client.connect 89.106.72.63:28125 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published 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.