Rust Server TrendsSeismic network · station log
Recording Stations11,628 Players32,585 Active2,817 Wipes · 3 h70 48 h

Station XX-16330 · no signal

Local PVE Staging

Offline 65.18.215.85:28025 checked 27d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,330
top 69%
Last wipe
28d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16330 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep2 Oct3 Oct5 Oct6 Oct8 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
48/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
126/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
67/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
16/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
6/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Local PVE Staging?

The map on Local PVE Staging is procedural, produced by the game.

Which settings and rules apply on Local PVE Staging?

You will find no gather rate in the name of Local PVE Staging. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on Local PVE Staging?

Local PVE Staging is not responding at this moment and is offline, last seen 27 days 13 hours ago.

How does Local PVE Staging rank against other Rust servers?

Over the last seven days, Local PVE Staging recorded enough player hours to reach #16,330 worldwide, placing it in the top 69% of all ranked servers.

Operator and location

How reliably does Local PVE Staging stay online?

No contact with Local PVE Staging right now, and the last recorded contact was 27 days 13 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 30 September 2026 is when Rust Server Trends first recorded it.

Which region does Local PVE Staging run from?

No region is published by Local PVE Staging. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 65.18.215.85:28025.

What build of Rust does Local PVE Staging use?

Local PVE Staging is running Rust network protocol 2634 and build 166461 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

How often does Local PVE Staging wipe, and on which days?

The rhythm of Local PVE Staging cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 28 days 16 hours is how long the current world has been running.

Server tags

What do the server tags on Local PVE Staging mean?

Tags published by Local PVE Staging and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166461 (Build): It runs game build 166461; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Local PVE Staging appear?

You will find Local PVE Staging on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto Local PVE Staging?

To join, enter client.connect 65.18.215.85:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166461,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166461
Build It runs game build 166461.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

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.