Station XX-15960 · no signal
BM577 health (local)
Offline 41.133.205.47:28145 checked 23d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,960
- top 71%
- Last wipe
- 23d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M –not enough readings
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, last three wipes
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 15:24 UTC23d ago | M0.0■steady | 0 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on BM577 health (local)?
The map on BM577 health (local) is procedural, produced by the game.
Which settings and rules apply on BM577 health (local)?
You will find no gather rate in the name of BM577 health (local). At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on BM577 health (local) right now?
BM577 health (local) is not responding at this moment and is offline, last seen 23 days 3 hours ago.
How does BM577 health (local) rank against other Rust servers?
On player hours for the past week, BM577 health (local) sits at #15,960, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does BM577 health (local) stay online?
No contact with BM577 health (local) right now, and the last recorded contact was 23 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 5 October 2026.
Where in the world is BM577 health (local) hosted?
No region is published by BM577 health (local). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 41.133.205.47:28145.
What build of Rust does BM577 health (local) use?
On Windows, BM577 health (local) runs Rust network protocol 2634 and build 166494. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on BM577 health (local)?
The recent wipes averaged a busiest count of 0 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does BM577 health (local) wipe, and on which days?
The rhythm of BM577 health (local) cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 23 days 3 hours is how long the current world has been running.
Server tags
What do the server tags on BM577 health (local) mean?
Tags published by BM577 health (local) and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): 5 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): It runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does BM577 health (local) appear?
These Rust Server Trends lists include BM577 health (local): Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto BM577 health (local)?
Enter client.connect 41.133.205.47:28145 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.