RUST METRICSFlight deck · live data
Data live Servers11,721 Players48,587 Populated3,224 Fresh wipes 3 h110 Scan5 min
‹ All servers135.136.58.207:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Staging Test Server

Offline 135.136.58.207:28015 checked 20d 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 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,848top 72%
Last wipe29d 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

Top 72% 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 timing

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

Its rhythm cannot be told from the wipes of Local Staging Test Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 29 days 3 hours ago the current world was made.

Tag meanings

How should you read the tags on Local Staging Test Server?

Tags published by Local Staging Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167312 (Build): Build 167312; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Local Staging Test Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Local Staging Test Server: 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.

Player count

Where does Local Staging Test Server sit in the rankings?

Ranking for Local Staging Test Server: #15,848 on seven-day player hours, top 72% of all ranked servers.

How full does Local Staging Test Server get?

Local Staging Test Server is not responding; status offline, last seen 20 days 8 hours ago.

Server

Where does Local Staging Test Server sit?

No region tag on Local Staging Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 135.136.58.207:28015.

What Rust version is Local Staging Test Server on?

Rust network protocol 2634 and build 167312 on Windows is the build Local Staging Test Server runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Local Staging Test Server reports offline. The last reading came 20 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Rules and settings

How is Local Staging Test Server configured, and what rules are in force?

Reading the name gives no gather rate for Local Staging Test Server. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Connection

How do you connect to Local Staging Test Server?

To join: start Rust, press F1 and type client.connect 135.136.58.207: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,gmrust,cs167312,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167312
Build Build 167312.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.