RS-15123Modded server
Backstage firewall test
Online 24.8.85.119:28325 checked 11m ago
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
Top 70% 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
| 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.
Quick answers
From the figures on this page.
Player count
How populated is Backstage firewall test?
Backstage firewall test is showing 0 players on 10 slots right now. Over the past seven days, the average player count was 0.
How is Backstage firewall test ranked?
The last seven days of player hours place Backstage firewall test at #15,123, in the top 70% of ranked servers.
Server tags and lists
Where does Backstage firewall test show up in Top Rust Servers lists and filters?
These Top Rust Servers lists count Backstage firewall test among their servers: Top modded Rust servers. These are the filters that 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 week.
What is the meaning of the tags on Backstage firewall test?
gmvanilla (Game mode): Vanilla survival mode; mp10 (Max players): Player slots: 10; ts8 (Group limit): At most 8 per team, as standard in the game; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Running game build 168909; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): Region code not set; ^z (Modded): It appears in Modded, as plugins or settings modify the game; ^y (Carbon): Plugin framework: Carbon are the tags Backstage firewall test publishes, and the game's server browser reads them. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.
Rules, settings, and map
What is the map on Backstage firewall test?
A procedural map of size 2,000 with seed 1610380731, created by the game, is in use on Backstage firewall test. You can look at the map on RustMaps from this page, because size and seed determine the map.
Which settings and rules apply on Backstage firewall test?
You will not find a gather rate in the name Backstage firewall test. Up to 8 players per group, as the game defaults. It runs survival, the normal mode where you gather, build and raid. You can fight and raid other players. Plugins or settings change the game; it is listed as Modded. Carbon plugins are loaded. VAC, Valve's anti-cheat, is enabled.
Server info
What Rust version is Backstage firewall test on?
Rust network protocol 2635 and build 168909 is what Backstage firewall test runs, on Windows. The protocol must match for you to join; Steam will update your game.
How well does Backstage firewall test perform?
The last 48 hours saw it average 240 server fps, never going under 239. The maximum entities it carried was 14,991, covering buildings, deployables and the rest. Memory usage peaked at 1,635 MB. A climbing entity count and low fps are the source of the lag players feel.
Where can Backstage firewall test be found?
A region is not published by Backstage firewall test. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 24.8.85.119:28325 is its address.
How reliable is Backstage firewall test?
The server Backstage firewall test is currently online. Going by its reported uptime, it restarted about 15 hours ago. It spent 49 of the last 72 hours online across 3 days, giving 68% uptime. It was first observed by Top Rust Servers on 19 October 2026.
Wipe schedule
On what schedule does Backstage firewall test wipe?
Not enough wipe data exists yet to identify the rhythm of Backstage firewall test. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 3 days 23 hours ago.
How to join
What is the process to join Backstage firewall test?
To connect, start Rust, hit F1, and enter client.connect 24.8.85.119:28325. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.