RUST METRICSFlight deck · live data
Data live Servers11,726 Players56,761 Populated3,425 Fresh wipes 3 h138 Scan5 min
‹ All servers69.9.131.72:28015
Offline Full Queue Fresh wipe Wipe due No query

Staging

Offline 69.9.131.72:28015 checked 3d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg7-day peak
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 1
Rank#8,188top 37%
Last wipe6d 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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 37% 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 21 Oct, 05:06 UTC6d 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?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Staging follow?

The rhythm of Staging's wipes cannot be told yet: too few 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. 6 days 18 hours ago the current world was made.

Lists and filters

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

These are the tags Staging publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs169057 (Build): Build 169057; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Staging appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Staging: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does Staging sit in the rankings?

Ranking for Staging: #8,188 on seven-day player hours, top 37% of all ranked servers.

What player count does Staging carry?

Status for Staging: offline. Last seen 3 days 23 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

Which location does Staging run from?

Reading: location. Staging gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 69.9.131.72:28015.

What Rust version is Staging on?

Rust network protocol 2635 and build 169057 on Windows is the build Staging runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Staging, and is it online?

Staging reports offline. The last reading came 3 days 23 hours ago. Uptime for the last 6 full days: 24 of 144 hours, or 17%. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Staging?

No gather rate appears in the name: Staging. The group cap is 8 players, which is the default in the game. 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. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Staging?

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

Connection

What do you do to join Staging?

Press F1 in Rust and enter client.connect 69.9.131.72:28015. 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 mp500,ptrak,$r?,v2635,gmrust,cs169057,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs169057
Build Build 169057.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.