Station XX-15341 · no signal
Backstage firewall test
Offline 24.8.85.119:28325 checked 4d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,341
- top 69%
- Last wipe
- 9d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 pageMap and rules
Which map is running on Backstage firewall test?
The procedural map on Backstage firewall test is size 2,000 with seed 1610380731, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Backstage firewall test?
No gather rate appears in the name of Backstage firewall test. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on Backstage firewall test?
Backstage firewall test is not responding at this moment and is offline, last seen 4 days 23 hours ago. Averaged across the last seven days, the population was 0 players.
How does Backstage firewall test rank against other Rust servers?
The last seven days of player hours place Backstage firewall test at #15,341, in the top 69% of all ranked servers.
Operator and location
How reliably does Backstage firewall test stay online?
No contact with Backstage firewall test right now, and the last recorded contact was 4 days 23 hours ago. It was up 22% of the time across the last 7 full days: 37 of 168 hours. On 19 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Backstage firewall test run from?
Nothing about a region comes from Backstage firewall test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 24.8.85.119:28325 is the address it uses.
Which Rust version is Backstage firewall test running?
Backstage firewall test is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does Backstage firewall test wipe, and on which days?
On record so far are too few of Backstage firewall test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 9 days 17 hours is how long the current world has been running.
Server tags
What do the server tags on Backstage firewall test mean?
These are the tags Backstage firewall test publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Backstage firewall test appear?
The Rust Server Trends lists that take in Backstage firewall test are: Modded Rust servers, tracked live. 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.
How to join
How do you connect to Backstage firewall test?
Enter client.connect 24.8.85.119:28325 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.