RUST METRICSFlight deck · live data
Data live Servers11,808 Players73,203 Populated3,760 Fresh wipes 3 h140 Scan5 min
‹ All servers116.203.97.221:28015
Offline Full Queue Fresh wipe Wipe due No query

Staging Dev Server

Offline 116.203.97.221:28015 checked 10d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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#15,153top 70%
Last wipe10d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k13 Oct15 Oct17 Oct19 Oct21 Oct23 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.3 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctFri 16 OctFri 16 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 23:11 UTC10d ago 0 – running 0
Fri 16 Oct, 16:41 UTC11d ago 0 – 0.3 days 0
Fri 16 Oct, 10:41 UTC11d ago 0 – 0.3 days 0
Fri 16 Oct, 00:41 UTC11d ago 0 – 0.4 days 0
Thu 15 Oct, 18:11 UTC12d ago 0 – 0.3 days 0
Thu 15 Oct, 12:11 UTC12d ago 0 – 0.3 days 0
Thu 15 Oct, 02:41 UTC12d ago 0 – 0.4 days 0
Wed 14 Oct, 18:11 UTC13d ago 0 – 0.4 days 0
Wed 14 Oct, 00:10 UTC13d ago 0 – 0.8 days 0
Tue 13 Oct, 08:11 UTC14d ago 0 – 0.7 days 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 happens on Staging Dev Server when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does Staging Dev Server wipe, and when?

There is no next wipe to predict: Staging Dev Server wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 10 days 22 hours ago the current world was made.

Tags

Which tags does Staging Dev Server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168330 (Build): Build 168330; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon from Staging Dev Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Staging Dev Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Staging Dev Server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does Staging Dev Server hold among Rust servers?

Player hours over seven days put Staging Dev Server at #15,153, in the top 70% of all ranked servers.

What player count does Staging Dev Server carry?

Reading for Staging Dev Server: offline at this moment; last seen 10 days 22 hours ago.

Operator and location

Where does Staging Dev Server sit?

Reading: location. Staging Dev Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 116.203.97.221:28015.

What Rust version is Staging Dev Server on?

Reading: Staging Dev Server, Rust network protocol 2635 and build 168330, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is Staging Dev Server, and is it online now?

Staging Dev Server reports offline. The last reading came 10 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 October 2026.

Map and rules

What settings and rules apply on Staging Dev Server?

Reading the name gives no gather rate for Staging Dev Server. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Staging Dev Server?

Procedural map on Staging Dev Server, made by the game's generator.

Connection

What do you do to join Staging Dev Server?

To join: start Rust, press F1 and type client.connect 116.203.97.221:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168330,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168330
Build Build 168330.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.