RUST METRICSFlight deck · live data
Data live Servers11,649 Players43,286 Populated3,030 Fresh wipes 3 h94 Scan5 min
‹ All servers213.193.252.202:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Staging Test

Offline 213.193.252.202:28015 checked 27d ago

moddedoxide
COM 1 · connect
Launch Rust and join

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#16,608top 70%
Last wipe28d 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

Reset cycle

When does Local Staging Test wipe?

The rhythm of Local Staging Test'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. 28 days 11 hours ago the current world was made.

Lists and filters

How should you read the tags on Local Staging Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166427 (Build): Game build reading: 166427; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from Local Staging Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Rust Metrics lists featuring Local Staging Test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does Local Staging Test hold among Rust servers?

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

How full does Local Staging Test get?

Status for Local Staging Test: offline. Last seen 27 days 22 hours ago.

Operator and location

Where does Local Staging Test sit?

No region tag on Local Staging Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 213.193.252.202:28015.

What Rust version is Local Staging Test on?

Version check: Rust network protocol 2634 and build 166427 on Windows, run by Local Staging Test. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. Local Staging Test last answered 27 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Settings and map

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

Check: gather rate. The name Local Staging Test does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Local Staging Test?

Check: map. Procedural, generated by the game, on Local Staging Test.

How to join

How do you connect to Local Staging Test?

To join: start Rust, press F1 and type client.connect 213.193.252.202:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166427,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166427
Build Game build reading: 166427.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.