Offline 41.133.205.47:28145 checked 23d ago
BM577 health (local)
Connect
srv = rust.server("41.133.205.47:28147")
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 · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 15:24 UTC23d ago | 0 | NaN | running | 0 |
# 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
- 41.133.205.47:28145
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 18:29 UTC
- hostname
- –
- first seen
- 5 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 · 152 on average | 38/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 14/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Player counts
How does BM577 health (local) compare in the rankings?
Rank #15,960 on seven-day player hours for BM577 health (local), within the top 71% of all ranked servers.
How many players does BM577 health (local) hold at once?
The current row shows BM577 health (local) offline; the last response was 23 days 10 hours ago.
Server data
What is the Rust version on BM577 health (local)?
The build is Rust network protocol 2634 and build 166494 on Windows, run by BM577 health (local). The protocol has to match before you can join, and Steam does the updating.
How reliable is BM577 health (local), and is it online now?
BM577 health (local) is offline at this refresh; the last response came 23 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 5 October 2026.
In which location is BM577 health (local) hosted?
No region is published by BM577 health (local). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 41.133.205.47:28145 is its address.
Rules, settings, map
Which settings and rules does BM577 health (local) run?
No gather rate appears in the name: BM577 health (local). No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has BM577 health (local) loaded?
A procedural map runs on BM577 health (local), generated by the game.
Wipes and dates
When does BM577 health (local) wipe, and on what schedule?
A rhythm cannot be read from the wipes of BM577 health (local) on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 23 days 10 hours ago.
What is wipe day on BM577 health (local) like?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold BM577 health (local), and which filters?
On Rust Data, BM577 health (local) appears in these lists: Modded Rust servers. It appears under these filters 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 BM577 health (local)?
Read by the game's server browser, the tags BM577 health (local) publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not 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
What is the way into BM577 health (local)?
The manual route: launch Rust, F1, then client.connect 41.133.205.47:28145. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.