RUST METRICSFlight deck · live data
Data live Servers11,806 Players70,052 Populated3,612 Fresh wipes 3 h182 Scan5 min
‹ All servers89.106.72.63:28125
Offline Full Queue Fresh wipe Wipe due No query

LOCAL raid difficulty validation

Offline 89.106.72.63:28125 checked 2d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,326top 69%
Last wipe2d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

How often does LOCAL raid difficulty validation wipe, and when?

Its rhythm cannot be told from the wipes of LOCAL raid difficulty validation on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 2 days 15 hours ago.

Tags

How should you read the tags on LOCAL raid difficulty validation?

These are the tags LOCAL raid difficulty validation publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LOCAL raid difficulty validation appear in Rust Metrics lists and filters?

Rust Metrics lists featuring LOCAL raid difficulty validation: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does LOCAL raid difficulty validation sit in the rankings?

Player hours over seven days put LOCAL raid difficulty validation at #15,326, in the top 69% of all ranked servers.

What player count does LOCAL raid difficulty validation carry?

Reading for LOCAL raid difficulty validation: offline at this moment; last seen 2 days 15 hours ago. Seven-day reading: 0 players on average.

Server

Where does LOCAL raid difficulty validation sit?

Reading: location. LOCAL raid difficulty validation gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 89.106.72.63:28125.

What Rust version is LOCAL raid difficulty validation on?

Rust network protocol 2635 and build 168909 on Windows is the build LOCAL raid difficulty validation runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is LOCAL raid difficulty validation, and is it online now?

Check: connection. LOCAL raid difficulty validation is offline at this moment. Last contact was 2 days 15 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. Reading: first seen 26 October 2026, recorded by Rust Metrics.

Rules and settings

How is LOCAL raid difficulty validation configured, and what rules are in force?

Reading the name gives no gather rate for LOCAL raid difficulty validation. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Join

What do you do to join LOCAL raid difficulty validation?

To join: start Rust, press F1 and type client.connect 89.106.72.63:28125. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.