Local Staging Map Test
Key statistics
the figures behind the quote- Players now
- 1/ 10 10% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,490 top 65%
- Rank · 7d ago
- #11,146 ▼4344 places down
- Last wipe
- 12d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Custom Map
- First seen
- 30 Sep 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 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 1 days between real wipes
- wipe-day peak
- 1 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 12:21 UTC12d ago | 1 | – | running | 1 |
| Wed 30 Sep, 12:23 UTC13d ago | 1 | – | 1 days | 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.
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 · 128 on average | 61/300 | ▲+12+25.6% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 101/245 | ▲+41+67.2% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 89/100 | ▪+0−0.6% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 84 on average | 52/1000 | ▼−17−24.3% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 17/1000 | ▼−17−50.0% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average | 54/700 | ▼−77−58.8% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on Local Staging Map Test?
No gather rate appears in the name of Local Staging Map Test. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Carbon. VAC, Valve's anti-cheat, is enabled.
Population
What is the rank of Local Staging Map Test?
In the top 65% of all ranked servers, Local Staging Map Test is #15,490 on player hours over the last seven days.
How full is Local Staging Map Test?
Right now, Local Staging Map Test is offline; the last sighting was 12 days 8 hours ago.
Wipe Frequency
What happens on wipe day at Local Staging Map Test?
Recent wipes at this server drew an average peak of 1 players. On the latest wipe, 0 hours after the wipe, the crowd peaked.
How often does Local Staging Map Test wipe?
There are too few wipes on record for Local Staging Map Test to reveal its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. Its world now is 12 days 8 hours old.
Server Details
Where can Local Staging Map Test be found?
There is no region published for Local Staging Map Test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 14.1.95.213:28015 is its address.
What Rust version is Local Staging Map Test running?
The version in use at Local Staging Map Test: Rust network protocol 2634 and build 166472, on Windows. The protocol has to match for you to join, and Steam applies that update.
Is Local Staging Map Test up, and how consistent is its uptime?
No response from Local Staging Map Test. It was last seen 12 days 8 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. The earliest Rust Analytics saw it was 30 September 2026.
Tags & Filters
How should you interpret the tags on Local Staging Map Test?
These tags are published by Local Staging Map Test and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Slot count: 10; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166472 (Build): Build 166472; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; ^y (Carbon): The plugin framework here is Carbon. Also in the tags and at the top of this page: current players, queue and world creation time.
On Rust Analytics, which lists and filters feature Local Staging Map Test?
The following Rust Analytics lists feature Local Staging Map Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connection
What steps do I take to join Local Staging Map Test?
The console route: start Rust, press F1, enter client.connect 14.1.95.213: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,cs166472,ts8,^z,^y
Game
gmrust
mp10
ts8
v2634
cs166472
ptrak
$r?
Mods and access
^z
^y
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.