RUST METRICSFlight deck · live data
Data live Servers11,869 Players90,153 Populated3,832 Fresh wipes 3 h374 Scan5 min
‹ All servers209.222.101.220:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Staging Test

Offline 209.222.101.220:28015 checked 28d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

10% 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,033top 67%
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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

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

How often does Local Staging Test wipe, and when?

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 18 hours ago the current world was made.

Tags

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

Tags published by Local Staging Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166427 (Build): Build 166427; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. 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 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Local Staging Test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does Local Staging Test hold among Rust servers?

Ranking for Local Staging Test: #16,033 on seven-day player hours, top 67% of all ranked servers.

How full does Local Staging Test get?

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

Operator and location

Which location does Local Staging Test run from?

No region comes from Local Staging Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 209.222.101.220:28015.

What Rust version is Local Staging Test on?

Reading: Local Staging Test, Rust network protocol 2634 and build 166427, Windows. Matching protocol is required to join. Let Steam update your game.

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

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

Map and rules

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

Reading the name gives no gather rate for Local Staging Test. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is Local Staging Test on?

The game generates a procedural map for Local Staging Test.

How to join

How do you connect to Local Staging Test?

To join: start Rust, press F1 and type client.connect 209.222.101.220: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 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166427
Build Build 166427.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.