Offline 212.33.228.249:28215 checked 7d ago
Blood staging test
Connect
srv = rust.server("212.33.228.249:28216")
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 best
Top 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 212.33.228.249:28215
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 11:59 UTC
- hostname
- –
- first seen
- 22 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 · 150 on average | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 92/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 244/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 344/350 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Blood staging test rank?
Rank #15,339 on seven-day player hours for Blood staging test, within the top 69% of all ranked servers.
How full does Blood staging test run?
The current row shows Blood staging test offline; the last response was 7 days 9 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does Blood staging test run?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Blood staging test. Steam updates your game for you, but the protocol must match to join.
Is Blood staging test up, and what does its uptime show?
Blood staging test is offline at this refresh; the last response came 7 days 9 hours ago. Over the last 6 full days the hours up number 0 of 144, 0%. Rust Data logged it first on 22 October 2026.
In which location is Blood staging test hosted?
There is no region published for Blood staging test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 212.33.228.249:28215.
Rules, settings, map
Which rules apply on Blood staging test, and what settings?
No gather rate appears in the name: Blood staging test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Blood staging test selected?
A procedural map runs on Blood staging test, generated by the game.
Wipes and dates
When does Blood staging test wipe, and on what schedule?
The record for Blood staging test holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 28 days 4 hours ago.
Lists and tags
Which Rust Data filters and lists contain Blood staging test?
The Rust Data lists that Blood staging test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Blood staging test?
The game's server browser reads these tags from Blood staging test: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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
What is the way to join Blood staging test?
The manual route: launch Rust, F1, then client.connect 212.33.228.249:28215. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.