RUST METRICSFlight deck · live data
Data live Servers11,869 Players85,654 Populated3,976 Fresh wipes 3 h170 Scan5 min
‹ All servers63.135.78.85:28015
Offline Full Queue Fresh wipe Wipe due No query

[STAGING] Test Server

Offline 63.135.78.85:28015 checked 29d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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#16,674top 70%
Last wipe29d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 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 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, 5 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 11:18 UTC29d 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 happens on [STAGING] Test Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 5 hours.

When does [STAGING] Test Server wipe?

The rhythm of [STAGING] Test Server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 29 days 1 hours ago.

Tags

How should you read the tags on [STAGING] Test Server?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166065 (Build): Game build reading: 166065; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from [STAGING] Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [STAGING] Test Server?

On Rust Metrics, [STAGING] Test Server sits in these lists: 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

Where does [STAGING] Test Server sit in the rankings?

Ranking for [STAGING] Test Server: #16,674 on seven-day player hours, top 70% of all ranked servers.

How full does [STAGING] Test Server get?

[STAGING] Test Server is not responding; status offline, last seen 29 days 1 hours ago.

Server

Which location does [STAGING] Test Server run from?

Reading: location. [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 63.135.78.85:28015.

What Rust version is [STAGING] Test Server on?

Rust network protocol 2634 and build 166065 on Windows is the build [STAGING] Test Server runs. Check: protocol. To join, your game must match; Steam handles the update.

Is [STAGING] Test Server up, and how often does it stay up?

Check: connection. [STAGING] Test Server is offline at this moment. Last contact was 29 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 28 September 2026.

Rules and settings

What settings and rules apply on [STAGING] Test Server?

Check: gather rate. The name [STAGING] Test Server does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Connection

What do you do to join [STAGING] Test Server?

Press F1 in Rust and enter client.connect 63.135.78.85: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 mp50,ptrak,$r?,v2634,gmrust,cs166065,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166065
Build Game build reading: 166065.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.