RUST METRICSFlight deck · live data
Data live Servers11,672 Players34,284 Populated2,842 Fresh wipes 3 h85 Scan5 min
‹ All servers191.217.217.120:28016
Offline Full Queue Fresh wipe Wipe due No query

staging_pirog

Offline 191.217.217.120:28016 checked 3d ago

COM 1 · connect

Server instruments

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

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#15,195top 68%
Last wipe4d 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

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

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 schedule

When does staging_pirog wipe?

The rhythm of staging_pirog'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. The world it runs now was made 4 days 2 hours ago.

Tag meanings

How should you read the tags on staging_pirog?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs169075 (Build): Build 169075; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from staging_pirog. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does staging_pirog appear in Rust Metrics lists and filters?

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

Player count

What position does staging_pirog hold among Rust servers?

Player hours over seven days put staging_pirog at #15,195, in the top 68% of all ranked servers.

How full does staging_pirog get?

staging_pirog is not responding; status offline, last seen 3 days 16 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

What location is staging_pirog hosted in?

Reading: location. staging_pirog gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 191.217.217.120:28016.

What Rust version is staging_pirog on?

Rust network protocol 2635 and build 169075 on Windows is the build staging_pirog runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is staging_pirog, and is it online now?

Reading: offline. staging_pirog last answered 3 days 16 hours ago. Uptime for the last 3 full days: 0 of 72 hours, or 0%. Check: first contact. Rust Metrics logged it on 25 October 2026.

Settings and map

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

Check: gather rate. The name staging_pirog does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on staging_pirog?

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

Connection

How do you connect to staging_pirog?

Press F1 in Rust and enter client.connect 191.217.217.120:28016. 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 mp5,ptrak,$r?,v2635,gmrust,cs169075,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs169075
Build Build 169075.
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.