RUST METRICSFlight deck · live data
Data live Servers11,888 Players103,803 Populated3,995 Fresh wipes 3 h419 Scan5 min
‹ All servers24.8.85.119:28325
Offline Full Queue Fresh wipe Wipe due No query

Backstage firewall test

Offline 24.8.85.119:28325 checked 5d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

0% 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#15,310top 69%
Last wipe9d 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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k19 Oct21 Oct23 Oct25 Oct27 Oct29 Oct

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

Wipe schedule

How often does Backstage firewall test wipe, and when?

To tell the rhythm of Backstage firewall test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 9 days 20 hours ago.

Tag meanings

How should you read the tags on Backstage firewall test?

Tags published by Backstage firewall test, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Backstage firewall test?

Rust Metrics lists featuring Backstage firewall test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does Backstage firewall test sit in the rankings?

Ranking for Backstage firewall test: #15,310 on seven-day player hours, top 69% of all ranked servers.

How full does Backstage firewall test get?

Reading for Backstage firewall test: offline at this moment; last seen 5 days 2 hours ago. Check: player average. 0 over the last seven days.

Server

Which location does Backstage firewall test run from?

No region tag on Backstage firewall test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 24.8.85.119:28325.

What Rust version is Backstage firewall test on?

Rust network protocol 2635 and build 168909 on Windows is the build Backstage firewall test runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Backstage firewall test, and is it online now?

Reading: offline. Backstage firewall test last answered 5 days 2 hours ago. Reading: 22% uptime over the last 7 full days. It was up 37 of 168 hours. Check: first contact. Rust Metrics logged it on 19 October 2026.

Settings and map

What settings and rules apply on Backstage firewall test?

Check: gather rate. The name Backstage firewall test does not state one. 8 players per group, the default value. Mode check gives survival; 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. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Backstage firewall test?

From seed 1610380731, the game generates the procedural map on Backstage firewall test. Its size is 2,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join Backstage firewall test?

Check: join. Open Rust, press F1, then enter client.connect 24.8.85.119:28325. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

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.