Rust Server TrendsSeismic network · station log
Recording Stations11,716 Players55,754 Active3,252 Wipes · 3 h168 48 h

Station XX-16084 · no signal

StagingLab

Offline 178.126.210.193:28115 checked 27d ago

moddedoxidepve
Connect
Players now
0/ 800
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,084
top 69%
Last wipe
28d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16084 · 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 800 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 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
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 253 on average
100/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 242 on average
158/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 106 on average
23/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
67/ 200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 54 on average
4/ 300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 50 on average
50/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on StagingLab?

You will find no gather rate in the name of StagingLab. 50 players is the most a group can hold. pve is the game mode, no player-versus-player fighting. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on StagingLab right now?

A reading taken now finds StagingLab offline; the most recent activity was 27 days 15 hours ago.

How does StagingLab rank against other Rust servers?

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

Operator and location

How reliably does StagingLab stay online?

As recorded now, StagingLab is not reachable, the last contact having been 27 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 1 October 2026 is when Rust Server Trends first recorded it.

Which region does StagingLab run from?

A region is not published by StagingLab. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 178.126.210.193:28115.

Which Rust version is StagingLab running?

Rust network protocol 2634 and build 166462 on Windows is what StagingLab runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

How often does StagingLab wipe, and on which days?

The rhythm of StagingLab 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. It has run its current world for 28 days 2 hours.

Server tags

What do the server tags on StagingLab mean?

Tags published by StagingLab and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp800 (Max players): Slots: 800; ts50 (Group limit): Each team can hold up to 50; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166462 (Build): Game build: 166462; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; modded (Modded): Plugins or settings alter the game, so it's listed under Modded; oxidation (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does StagingLab appear?

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

How to join

What steps get you onto StagingLab?

To join, enter client.connect 178.126.210.193:28115 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 mp800,ptrak,$r?,v2634,^p,gmrust,cs166462,ts50,^o^z,oxidation,modded

Game

gmrust
Game mode Survival in standard Rust.
mp800
Max players Slots: 800.
ts50
Group limit Each team can hold up to 50.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166462
Build Game build: 166462.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Gameplay

^p
PvE You won't fight other players here; the world is what threatens you.

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.
modded
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

oxidation
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.

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.