Offline 24.8.85.119:28325 checked 4d ago
Backstage firewall test
Connect
srv = rust.server("24.8.85.119:28327")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
2000 · seed 1610380731- map
- Procedural Map
- size
- 2000
- seed
- 1610380731
Server
srv.info()- address
- 24.8.85.119:28325
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 22:16 UTC
- hostname
- –
- first seen
- 19 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 77/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population
How does Backstage firewall test compare in the rankings?
Over the last seven days Backstage firewall test sits at #15,338 on player hours, in the top 69% of ranked servers.
How full does Backstage firewall test run?
The current row shows Backstage firewall test offline; the last response was 4 days 18 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does Backstage firewall test run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Backstage firewall test. Joining needs the same protocol on your game; Steam handles the update.
Is Backstage firewall test up, and what does its uptime show?
Backstage firewall test is offline at this refresh; the last response came 4 days 18 hours ago. Over the last 7 full days the hours up number 37 of 168, 22%. The first row Rust Data holds for it is dated 19 October 2026.
In which location is Backstage firewall test hosted?
For Backstage firewall test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 24.8.85.119:28325 is its address.
Rules, settings, map
Which rules apply on Backstage firewall test, and what settings?
The name Backstage firewall test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Backstage firewall test selected?
The game generates the map on Backstage firewall test: procedural, size 2,000, seed 1610380731. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does Backstage firewall test wipe, and on what schedule?
Too few wipes are on record for Backstage firewall test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 9 days 12 hours ago.
Tags, lists
Which lists on Rust Data hold Backstage firewall test, and which filters?
These Rust Data lists include Backstage firewall 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.
Which meanings do the tags on Backstage firewall test hold?
The game's server browser reads these tags from Backstage firewall test: gmvanilla (Game mode): Survival in vanilla form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Backstage firewall test?
In Rust, F1 opens the console: type client.connect 24.8.85.119:28325. Launch Rust on this page does the same by opening the game through Steam and connecting.