Local Staging Test
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,608 top 70%
- Rank · 7d ago
- #16,111 ▼497 places down
- Last wipe
- 13d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 1 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 126 on average | 184/300 | ▼−12−6.2% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 190/225 | ▲+1+0.4% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▪+0+0.4% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 48/1000 | ▼−58−54.6% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 17/1000 | ▼−14−45.5% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 50/700 | ▼−78−61.1% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Local Staging Test?
The name of Local Staging Test carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are running. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Local Staging Test?
The game generates the procedural map on Local Staging Test.
Activity
Where does Local Staging Test sit in the rankings?
In the top 70% of all ranked servers, Local Staging Test is #16,608 on player hours over the last seven days.
What is the population on Local Staging Test?
Right now, Local Staging Test is offline; the last sighting was 13 days 3 hours ago.
Wipe Frequency
On what cycle does Local Staging Test wipe?
There are too few wipes on record for Local Staging Test to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 13 days 15 hours ago the current world was created.
Server Overview
What is the location of Local Staging Test?
There is no region published for Local Staging Test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 213.193.252.202:28015.
Local Staging Test runs which version of Rust?
The version in use at Local Staging Test: Rust network protocol 2634 and build 166427, on Windows. Your game needs the same protocol to get in; Steam takes care of the update.
Is Local Staging Test up, and how consistent is its uptime?
No response from Local Staging Test. It was last seen 13 days 3 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 1 October 2026.
Tags & Filters
How should you interpret the tags on Local Staging Test?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166427 (Build): Game build: 166427; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Local Staging Test publishes. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does Local Staging Test show up in Rust Analytics lists and filters?
On Rust Analytics, Local Staging Test matches these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to Join
How can I connect to Local Staging Test?
The console route: start Rust, press F1, enter client.connect 213.193.252.202:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2634,gmrust,cs166427,ts8,^o^z
Game
gmrust
mp10
ts8
v2634
cs166427
ptrak
$r?
Mods and access
^o
^z
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.