Station XX-15490 · no signal
Local Staging Map Test
Offline 14.1.95.213:28015 checked 26d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,490
- top 65%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
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 yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1 daysbetween real wipes
- wipe-day peak
- 1players, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 12:21 UTC26d ago | M0.0■steady | 1 | – | – | running | 1 |
| Wed 30 Sep, 12:23 UTC27d ago | M0.0▲rising | 1 | – | 1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which settings and rules apply on Local Staging Map Test?
You will find no gather rate in the name of Local Staging Map Test. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Local Staging Map Test right now?
Local Staging Map Test is not responding at this moment and is offline, last seen 26 days 12 hours ago.
How does Local Staging Map Test rank against other Rust servers?
On player hours for the past week, Local Staging Map Test sits at #15,490, which puts it inside the top 65% of every ranked server.
Operator and location
How reliably does Local Staging Map Test stay online?
No contact with Local Staging Map Test right now, and the last recorded contact was 26 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 30 September 2026 is when Rust Server Trends first recorded it.
Which region does Local Staging Map Test run from?
A region is not published by Local Staging Map Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 14.1.95.213:28015.
What build of Rust does Local Staging Map Test use?
Rust network protocol 2634 and build 166472 on Windows is what Local Staging Map Test runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Local Staging Map Test?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does Local Staging Map Test wipe, and on which days?
The rhythm of Local Staging Map Test cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 26 days 12 hours.
Server tags
What do the server tags on Local Staging Map Test mean?
The game's server browser reads the tags Local Staging Map Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166472 (Build): The game build is 166472; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Local Staging Map Test appear?
These Rust Server Trends lists include Local Staging Map Test: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
What steps get you onto Local Staging Map Test?
You can connect by pressing F1 in Rust and typing client.connect 14.1.95.213:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.