Offline 31.59.120.109:28535 checked 9d ago
BP-ISOLATED-TEST
Connect
srv = rust.server("31.59.120.109:28536")
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 | Tue 20 Oct, 08:49 UTC9d 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
- 31.59.120.109:28535
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 09:01 UTC
- hostname
- –
- first seen
- 20 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 | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 256/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Player counts
What position does BP-ISOLATED-TEST take in the server rankings?
Player hours over seven days put BP-ISOLATED-TEST at #15,350, in the top 70% of the ranked set.
What population does BP-ISOLATED-TEST carry?
The current row shows BP-ISOLATED-TEST offline; the last response was 9 days 7 hours ago.
About the server
Which Rust version is BP-ISOLATED-TEST on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by BP-ISOLATED-TEST. Joining needs the same protocol on your game; Steam handles the update.
Is BP-ISOLATED-TEST up, and what does its uptime show?
Offline now for BP-ISOLATED-TEST, last seen 9 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 20 October 2026.
Which location does BP-ISOLATED-TEST run from?
For BP-ISOLATED-TEST, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 31.59.120.109:28535 is its address.
Rules, settings, map
What rules and settings are recorded for BP-ISOLATED-TEST?
The name BP-ISOLATED-TEST carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. The VAC field reads off.
Which map has BP-ISOLATED-TEST selected?
A procedural map runs on BP-ISOLATED-TEST, generated by the game.
Wipe data
When does BP-ISOLATED-TEST wipe, and how often?
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. A new world was started 9 days 7 hours ago, and that is the one in play.
On BP-ISOLATED-TEST, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which Rust Data filters and lists contain BP-ISOLATED-TEST?
The Rust Data lists that BP-ISOLATED-TEST fits are: Modded Rust servers. These filters bring it up on the server list: 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?
The game's server browser reads these tags from BP-ISOLATED-TEST: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): 0 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; 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): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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.
Connecting
How can I connect to BP-ISOLATED-TEST?
The manual route: launch Rust, F1, then client.connect 31.59.120.109:28535. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.