Rust Player Stats
Live UTC 86,091 playing

Offline 89.106.72.63:28125 checked 1d ago

LOCAL raid difficulty validation

moddedoxide
Players now0
Slots1
Full0%
7-day average0peak –
Rank#15,452top 69%
Last wipe1d agono schedule published
Next wipe–no wipe seen yet
Launch Rust and join

By the numbersMatch stats

against its 1 slots
Players now0
0% of the slots taken
7-day average0
players on an average hour this week
7-day peak–
the fullest it got this week
48-hour peak0
the busiest hour of the last two days
On the list1 of 48 hours
hours it answered in the last two days
Standingtop 69%
of all ranked servers, on player hours over seven days
Replay

The story of the match

Players, performance and rank, hour by hour and day by day.

CrowdPlayers

No hourly history yet.

Hourly average and peak, UTC.

FitnessServer 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.

FormRank

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

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

FixturesWipe schedule

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

ResultsWipes

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.

Other matches on now

Similar servers

The same kind of game, then region, group limit, rate and wipes.

The pundits

Quick answers

From the figures on this page.

Server details

Is LOCAL raid difficulty validation online, and how reliable is it?

LOCAL raid difficulty validation sits offline; 42 hours ago is when it was last seen. The board reads 0 hours up out of 24 across 1 day: 0%. The first record Rust Player Stats has of it is 26 October 2026.

Which Rust version is LOCAL raid difficulty validation on?

On Windows, LOCAL raid difficulty validation runs Rust network protocol 2635 and build 168909. Same protocol or no entry: your game must match, and Steam keeps it updated for you.

Where is LOCAL raid difficulty validation located?

Nothing on LOCAL raid difficulty validation states a region. Rust Player Stats takes the server's word on where it is and does not look up the machine's real location. 89.106.72.63:28125 is the address.

Lists and filters

What do the server tags on LOCAL raid difficulty validation mean?

The game's server browser reads these tags from LOCAL raid difficulty validation: gmrust (Game mode): The standard Rust survival rules apply here; mp1 (Max players): Slot count: 1; ts8 (Group limit): No more than 8 to a team, as the game sets by default; v2635 (Protocol): Game protocol 2635: join only if your game matches that version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, the standard one; $r? (Region code): No region code is set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Modded is its category: plugins or settings change how it plays. The tags carry more besides: present players, queue length and when the world was made, all displayed at the top of this page.

Which Rust Player Stats lists and filters include LOCAL raid difficulty validation?

You will find LOCAL raid difficulty validation on the following Rust Player Stats lists: Modded Rust servers, live. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Map and rules

What are the rules and settings on LOCAL raid difficulty validation?

The name of LOCAL raid difficulty validation does not say what the gather rate is. The cap is 8 players per group, the game's default. build, gather and raid in the standard game: that is the survival game mode. PvP is on, and so is raiding. Under Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are running. Anti-cheat is on: VAC.

Player counts

How full is LOCAL raid difficulty validation right now?

Last seen 42 hours ago, LOCAL raid difficulty validation is offline right now. The seven-day average for this server is 0 players.

Where does LOCAL raid difficulty validation sit in the rankings?

Player hours over seven days place LOCAL raid difficulty validation at #15,452, among the top 69% of ranked servers.

Wipe timing

What is the wipe schedule on LOCAL raid difficulty validation?

To tell its rhythm, more of LOCAL raid difficulty validation's wipes need to be on record. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 42 hours ago is when its current world was made.

Connect

How do I join LOCAL raid difficulty validation?

Console route: F1 in Rust, then client.connect 89.106.72.63:28125. Or use Launch Rust here, which opens Rust through Steam and connects you.

GlossaryServer tags

what each one means

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

Game

gmrust
Game mode The standard Rust survival rules apply here.
mp1
Max players Slot count: 1.
ts8
Group limit No more than 8 to a team, as the game sets by default.
v2635
Protocol Game protocol 2635: join only if your game matches that version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, the standard one.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Modded is its category: plugins or settings change how it plays.

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.