Offline 91.113.10.234:28015 checked 22d ago
BRU Staging (QA)
Connect
srv = rust.server("91.113.10.234:28017")
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. 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 71% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 91.113.10.234:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 15:54 UTC
- hostname
- –
- first seen
- 4 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 | 170/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 75/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 83 on average | 252/700 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does BRU Staging (QA) rank?
Player hours over seven days put BRU Staging (QA) at #15,977, in the top 71% of the ranked set.
How many players does BRU Staging (QA) hold at once?
Offline now for BRU Staging (QA), with the last sample 22 days 15 hours ago.
Server data
Which Rust version is BRU Staging (QA) on?
The build is Rust network protocol 2634 and build 166652 on Linux, run by BRU Staging (QA). Joining needs the same protocol on your game; Steam handles the update.
Is BRU Staging (QA) up, and what does its uptime show?
BRU Staging (QA) is offline at this refresh; the last response came 22 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 4 October 2026.
Which location does BRU Staging (QA) run from?
No region is published by BRU Staging (QA). Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 91.113.10.234:28015.
Rules, settings, map
Which settings and rules does BRU Staging (QA) run?
The name BRU Staging (QA) carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has BRU Staging (QA) loaded?
The game generates its map: procedural, on BRU Staging (QA).
Wipe data
On what schedule does BRU Staging (QA) wipe?
Too few wipes are on record for BRU Staging (QA) 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 25 days 20 hours ago.
Tags, lists
Which lists on Rust Data hold BRU Staging (QA), and which filters?
The Rust Data lists that BRU Staging (QA) fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on BRU Staging (QA)?
Read by the game's server browser, the tags BRU Staging (QA) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to BRU Staging (QA)?
Enter client.connect 91.113.10.234:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.