Offline 95.182.82.154:28515 checked 12d ago
BP-ISOLATED-TEST
Connect
srv = rust.server("95.182.82.154:28516")
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 70% 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 | Thu 15 Oct, 20:29 UTC12d 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
- 95.182.82.154:28515
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 20:29 UTC
- hostname
- –
- first seen
- 8 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
How does BP-ISOLATED-TEST compare in the rankings?
Player hours over seven days put BP-ISOLATED-TEST at #15,092, in the top 70% of the ranked set.
How full does BP-ISOLATED-TEST run?
The current row shows BP-ISOLATED-TEST offline; the last response was 12 days 22 hours ago.
Server facts
What Rust version does BP-ISOLATED-TEST run?
Version Rust network protocol 2634 and build 167781 on Windows is reported by BP-ISOLATED-TEST. The protocol has to match before you can join, and Steam does the updating.
Is BP-ISOLATED-TEST up, and what does its uptime show?
Offline now for BP-ISOLATED-TEST, last seen 12 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 8 October 2026.
Which location does BP-ISOLATED-TEST run from?
For BP-ISOLATED-TEST, no region is published. 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 95.182.82.154:28515.
Settings and map
Which settings and rules does BP-ISOLATED-TEST run?
No gather rate appears in the name: BP-ISOLATED-TEST. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC off.
Which map has BP-ISOLATED-TEST loaded?
The game generates its map: procedural, on BP-ISOLATED-TEST.
Wipe schedule
On what schedule does BP-ISOLATED-TEST wipe?
Too few wipes are on record for BP-ISOLATED-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. The world it runs now was generated 12 days 22 hours ago.
On BP-ISOLATED-TEST, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold BP-ISOLATED-TEST, and which filters?
These Rust Data lists include BP-ISOLATED-TEST: 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on BP-ISOLATED-TEST hold?
These tags are published by BP-ISOLATED-TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to BP-ISOLATED-TEST?
In Rust, F1 opens the console: type client.connect 95.182.82.154:28515. Launch Rust on this page does the same by opening the game through Steam and connecting.