RUST METRICSFlight deck · live data
Data live Servers11,624 Players37,278 Populated2,941 Fresh wipes 3 h101 Scan5 min
‹ All servers83.217.171.135:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Staging Test Server

Offline 83.217.171.135:28015 checked 28d ago

COM 1 · connect

Server instruments

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

Players now

20% 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,186top 68%
Last wipe28d 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
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

Top 68% 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

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 21:01 UTC28d 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 should you expect from wipe day on Local Staging Test Server?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

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. 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 28 days 9 hours ago.

Tag meanings

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

These are the tags Local Staging Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166257 (Build): Game build reading: 166257; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

On Rust Metrics, Local 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.

Player count

Where does Local Staging Test Server sit in the rankings?

Player hours over seven days put Local Staging Test Server at #16,186, in the top 68% of all ranked servers.

How full does Local Staging Test Server get?

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

Server

Where does Local Staging Test Server sit?

Reading: location. Local Staging Test Server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 83.217.171.135:28015.

What Rust version is Local Staging Test Server on?

Version check: Rust network protocol 2634 and build 166257 on Windows, run by Local Staging Test Server. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. Local Staging Test Server is offline at this moment. Last contact was 28 days 9 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 29 September 2026.

Rules and settings

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

Check: gather rate. The name Local Staging Test Server does not state one. 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. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How do you connect to Local Staging Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166257,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166257
Build Game build reading: 166257.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.