RUST METRICSFlight deck · live data
Data live Servers11,726 Players56,761 Populated3,425 Fresh wipes 3 h136 Scan5 min
‹ All servers189.99.180.99:32015
Offline Full Queue Fresh wipe Wipe due No query

STAGING

Offline 189.99.180.99:32015 checked 26d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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#16,084top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k27 Sep29 Sep1 Oct4 Oct6 Oct8 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 30 Sep, 20:10 UTC27d ago 1 – running 0

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 timing

What should you expect from wipe day on STAGING?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does STAGING wipe, and when?

Its rhythm cannot be told from the wipes of STAGING on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 27 days 2 hours ago.

Tags

Which tags does STAGING carry, and what do they mean?

Tags published by STAGING, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166493 (Build): The server runs game build 166493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show STAGING?

On Rust Metrics, STAGING sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does STAGING sit in the rankings?

Ranking for STAGING: #16,084 on seven-day player hours, top 69% of all ranked servers.

How full does STAGING get?

STAGING is not responding; status offline, last seen 26 days 5 hours ago.

Operator and location

Where does STAGING sit?

No region comes from STAGING. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 189.99.180.99:32015.

What Rust version is STAGING on?

Version check: Rust network protocol 2634 and build 166493 on Windows, run by STAGING. Check: protocol. To join, your game must match; Steam handles the update.

Is STAGING up, and how often does it stay up?

Check: connection. STAGING is offline at this moment. Last contact was 26 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 27 September 2026.

Map and rules

What rules does STAGING enforce, and what are its settings?

No gather rate appears in the name: STAGING. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How do you connect to STAGING?

Press F1 in Rust and enter client.connect 189.99.180.99:32015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmvanilla,cs166493,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166493
Build The server runs game build 166493.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.