RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers2.28.122.57:28015
Offline Full Queue Fresh wipe Wipe due No query

Staging Dev Server

Offline 2.28.122.57:28015 checked 41d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

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,489no region published
Last wipe41d agono schedule published
Next wipe–no wipe 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep
PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

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

How often does Staging Dev Server wipe, and when?

To tell the rhythm of Staging Dev Server, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 41 days 12 hours ago the current world was made.

Tags

How should you read the tags on Staging Dev Server?

These are the tags Staging Dev Server publishes, and the server browser reads them: 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; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164613 (Build): Build 164613; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Staging Dev Server?

These Rust Metrics lists carry Staging Dev Server: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

What position does Staging Dev Server hold among Rust servers?

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

How full does Staging Dev Server get?

Status for Staging Dev Server: offline. Last seen 41 days 12 hours ago.

Server

What location is Staging Dev Server hosted in?

No region comes from Staging Dev Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 2.28.122.57:28015.

What Rust version is Staging Dev Server on?

Reading: Staging Dev Server, Rust network protocol 2633 and build 164613, Linux. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. Staging Dev Server last answered 41 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Staging Dev Server?

No gather rate appears in the name: Staging Dev Server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Staging Dev Server on?

Check: map. Procedural, generated by the game, on Staging Dev Server.

How to join

What do you do to join Staging Dev Server?

To join: start Rust, press F1 and type client.connect 2.28.122.57: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?,v2633,gmrust,cs164613,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.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164613
Build Build 164613.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Check: framework. 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.