RUST METRICSFlight deck · live data
Data live Servers11,699 Players38,680 Populated2,939 Fresh wipes 3 h94 Scan5 min
‹ All servers159.196.83.189:28015
Offline Full Queue Fresh wipe Wipe due No query

Staging Server

Offline 159.196.83.189:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 2 /5

Players now

40% 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#12,590top 53%
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
15k10k15k20k30 Sep2 Oct3 Oct5 Oct6 Oct8 Oct

Top 53% 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 peak3players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 04:43 UTC27d ago 3 – running 1

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 schedule

What should you expect from wipe day on Staging Server?

The busiest point of its recent wipes drew 3 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Staging Server follow?

The rhythm of Staging Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 27 days 20 hours ago the current world was made.

Tags

How should you read the tags on Staging Server?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166452 (Build): Build 166452; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Staging Server. 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 Server?

These Rust Metrics lists carry Staging Server: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Staging Server hold among Rust servers?

Ranking for Staging Server: #12,590 on seven-day player hours, top 53% of all ranked servers.

How full does Staging Server get?

Status for Staging Server: offline. Last seen 27 days 18 hours ago.

Server

Which location does Staging Server run from?

Reading: location. Staging Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 159.196.83.189:28015.

What Rust version is Staging Server on?

Reading: Staging Server, Rust network protocol 2634 and build 166452, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

Staging Server reports offline. The last reading came 27 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 30 September 2026.

Map and rules

What settings and rules apply on Staging Server?

Check: gather rate. The name Staging Server does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Staging Server?

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

Join

How do you connect to Staging Server?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmvanilla,cs166452,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166452
Build Build 166452.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.