StagingLab
Key statistics
the figures behind the quote- Players now
- 0/ 800 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,084 top 69%
- Rank · 7d ago
- #16,111 ▲27 places up
- Last wipe
- 13d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 50 max players per team
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Вайп был 10 ч наза
- First seen
- 1 Oct 2026 no hostname published
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
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 206 on average | 127/2000 | ▼−40−24.0% | |
| 2 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 201 on average | 67/2000 | ▼−23−25.8% | |
| 3 | 1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 76 on average | 61/200 | ▼−7−10.0% | |
| 4 | 桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 75 on average | 26/100 | ▼−54−67.5% | |
| 5 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 64 on average | 24/200 | ▲+1+3.6% | |
| 6 | Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 64 on average | 82/100 | ▼−14−15.0% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on StagingLab?
The name of StagingLab carries no gather rate. The maximum group size is 50 players. pve is the mode, no combat against other players. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, switched on.
Population
What is the rank of StagingLab?
In the top 69% of all ranked servers, StagingLab is #16,084 on player hours over the last seven days.
What is the population on StagingLab?
Right now, StagingLab is offline; the last sighting was 12 days 15 hours ago.
Wipe Schedule
How often does StagingLab wipe?
No rhythm can be told for StagingLab yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 13 days 2 hours.
Server Info
What is the location of StagingLab?
There is no region published for StagingLab. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 178.126.210.193:28115.
StagingLab runs which version of Rust?
The version in use at StagingLab: Rust network protocol 2634 and build 166462, on Windows. The protocol has to match for you to join, and Steam applies that update.
How reliable is StagingLab and is it currently online?
No response from StagingLab. It was last seen 12 days 15 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. 1 October 2026 is when Rust Analytics first saw it.
Server Tags
What is the meaning of the tags on StagingLab?
These tags are published by StagingLab and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp800 (Max players): Capacity: 800 slots; ts50 (Group limit): Teams take no more than 50; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166462 (Build): Game build: 166462; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^p (PvE): Player-versus-player fighting is off; the world supplies the danger; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; modded (Modded): Modded listing: the game is changed by plugins or settings; oxidation (Custom tag): A non-standard tag, added by the owner or through a plugin. The tags also carry its current players, queue and world creation time; this page shows them at the top.
StagingLab appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include StagingLab: Modded Rust servers and Best Rust PvE servers. It appears 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; Last wipe: In the last 2 weeks.
How to Join
What is the process to join StagingLab?
The console route: start Rust, press F1, enter client.connect 178.126.210.193:28115. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp800,ptrak,$r?,v2634,^p,gmrust,cs166462,ts50,^o^z,oxidation,modded
Game
gmrust
mp800
ts50
v2634
cs166462
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
modded
Other
oxidation
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.