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

My Staging Test Server

Offline 85.155.228.58:28015 checked 39d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,412no region published
Last wipe41d 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 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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
Thu 17 Sep, 14:01 UTC41d 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

Reset cycle

What happens on My Staging Test Server when wipe day comes?

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

How often does My Staging Test Server wipe, and when?

The rhythm of My Staging Test Server'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 41 days 5 hours ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164795 (Build): Build 164795; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from My Staging Test 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 My Staging Test Server?

On Rust Metrics, My Staging Test Server sits in these lists: 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.

Population

What position does My Staging Test Server hold among Rust servers?

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

How full does My Staging Test Server get?

Status for My Staging Test Server: offline. Last seen 39 days 6 hours ago.

Server

What location is My Staging Test Server hosted in?

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

What Rust version is My Staging Test Server on?

Rust network protocol 2633 and build 164795 on Windows is the build My Staging Test Server runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on My Staging Test Server, and is it online?

My Staging Test Server reports offline. The last reading came 39 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Settings and map

What rules does My Staging Test Server enforce, and what are its settings?

No gather rate appears in the name: My Staging Test Server. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is My Staging Test Server on?

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

Join

How do you connect to My Staging Test Server?

Check: join. Open Rust, press F1, then enter client.connect 85.155.228.58:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs164795,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164795
Build Build 164795.
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.