RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,316 Populated4,103 Fresh wipes 3 h158 Scan5 min
‹ All servers57.128.211.49:28019
Offline Full Queue Fresh wipe Wipe due No query

Facepunch Staging Auto Restart 10 minutes | Nav Disabled

Offline 57.128.211.49:28019 checked 4h ago

COM 1 · connect

Server instruments

last reading Tue 13:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg
0 10 30 60 120 256 FPS 237 SERVER FPS

Server fps

48 h low 193 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 218,000 ×1000

Entities

48 h range 209,000–218,000 · memory 2,527 MB
1239 ET SINCE RESTART 00:00

Uptime

0 h 0 min since its last restart, at the last reading
7-day average0peak –
Rank#15,369top 70%
Last wipe33d agono schedule published
Next wipe–too few wipes seen yet
Memory2,527MBat the last reading
REC 1

Players

AveragePeak
0123419:0003:0012:0020:0005:0013:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040019:0003:0012:0020:0005:0013:00

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, measured since 17 Sep. 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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
Thu 24 Sep, 10:41 UTC33d ago 0 – 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 happens on Facepunch Staging Auto Restart 10 minutes | Nav Disabled when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Facepunch Staging Auto Restart 10 minutes | Nav Disabled follow?

Its rhythm cannot be told from the wipes of Facepunch Staging Auto Restart 10 minutes | Nav Disabled on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 33 days 7 hours ago the current world was made.

Tags

How should you read the tags on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?

These are the tags Facepunch Staging Auto Restart 10 minutes | Nav Disabled publishes, and the server browser reads them: official (official): Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand; gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs169317 (Build): Game build reading: 169317; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Who operates Facepunch Staging Auto Restart 10 minutes | Nav Disabled?

The playrust.com hostname on Facepunch Staging Auto Restart 10 minutes | Nav Disabled also appears on 124 other servers we track, which points to one operator.

Where does Facepunch Staging Auto Restart 10 minutes | Nav Disabled appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Facepunch Staging Auto Restart 10 minutes | Nav Disabled: Tag: official. listed.. These filters bring it up on the server list: Type: No plugins at all; Group limit: 5 or more; Boxes: Official only.

Population

Where does Facepunch Staging Auto Restart 10 minutes | Nav Disabled sit in the rankings?

Player hours over seven days put Facepunch Staging Auto Restart 10 minutes | Nav Disabled at #15,369, in the top 70% of all ranked servers.

What is the population on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?

Reading for Facepunch Staging Auto Restart 10 minutes | Nav Disabled: offline at this moment; last seen 4 hours ago. Check: player average. 0 over the last seven days.

Operator and location

What location is Facepunch Staging Auto Restart 10 minutes | Nav Disabled hosted in?

No region comes from Facepunch Staging Auto Restart 10 minutes | Nav Disabled. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 57.128.211.49:28019.

What Rust version is Facepunch Staging Auto Restart 10 minutes | Nav Disabled on?

Version check: Rust network protocol 2635 and build 169317 on Windows, run by Facepunch Staging Auto Restart 10 minutes | Nav Disabled. Matching protocol is required to join. Let Steam update your game.

Is performance on Facepunch Staging Auto Restart 10 minutes | Nav Disabled within range?

Check: fps. Average 232 server fps over the last 48 hours, low of 193. Within range. Reading: 218,000 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 2,679 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is Facepunch Staging Auto Restart 10 minutes | Nav Disabled up, and how often does it stay up?

Facepunch Staging Auto Restart 10 minutes | Nav Disabled reports offline. The last reading came 4 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

How is Facepunch Staging Auto Restart 10 minutes | Nav Disabled configured, and what rules are in force?

Check: gather rate. The name Facepunch Staging Auto Restart 10 minutes | Nav Disabled does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The in-game Official tab of Rust lists it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?

Size 4,500 and seed 9563351: the game generates the procedural map on Facepunch Staging Auto Restart 10 minutes | Nav Disabled from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to Facepunch Staging Auto Restart 10 minutes | Nav Disabled?

Press F1 in Rust and enter client.connect 57.128.211.49:28019. 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 mp0,ptrak,$r?,v2635,gmrust,cs169317,ts8

On Rust Metrics

official
Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand.

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players The server holds 0 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs169317
Build Game build reading: 169317.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.