Offline 101.81.76.35:28015 checked 29d ago
LinuxGSM BKN100
Connect
srv = rust.server("101.81.76.35:28017")
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 28 Sep, 10:08 UTC30d ago | 1 | NaN | running | 0 |
| 1 | Thu 24 Sep, 01:58 UTC34d ago | 1 | halved by day 1 | 4.3 days | 1 |
| 2 | Wed 23 Sep, 01:10 UTC35d ago | 1 | NaN | 1 days | 1 |
# 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
- 101.81.76.35:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 01:58 UTC
- hostname
- –
- first seen
- 22 Sep 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 | 101/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 110/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 91/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 28/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Population
What position does LinuxGSM BKN100 take in the server rankings?
Player hours over seven days put LinuxGSM BKN100 at #16,917, in the top 71% of the ranked set.
How many players does LinuxGSM BKN100 hold at once?
The current row shows LinuxGSM BKN100 offline; the last response was 29 days 19 hours ago.
Server data
What Rust version does LinuxGSM BKN100 run?
Version Rust network protocol 2633 and build 165217 on Linux is reported by LinuxGSM BKN100. The protocol has to match before you can join, and Steam does the updating.
How reliable is LinuxGSM BKN100, and is it up?
LinuxGSM BKN100 is offline at this refresh; the last response came 29 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 22 September 2026.
In which location is LinuxGSM BKN100 hosted?
No region is published by LinuxGSM BKN100. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 101.81.76.35:28015 is its address.
Settings and map
Which settings and rules does LinuxGSM BKN100 run?
No gather rate appears in the name: LinuxGSM BKN100. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has LinuxGSM BKN100 loaded?
A procedural map runs on LinuxGSM BKN100, generated by the game.
Wipe data
When does LinuxGSM BKN100 wipe, and on what schedule?
Irregular wipe times on LinuxGSM BKN100 leave no next wipe to forecast. 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 34 days 19 hours ago, and that is the one in play.
On LinuxGSM BKN100, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.
Lists and tags
Which Rust Data filters and lists contain LinuxGSM BKN100?
On Rust Data, LinuxGSM BKN100 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.
Which meanings do the tags on LinuxGSM BKN100 hold?
These tags are published by LinuxGSM BKN100 and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to LinuxGSM BKN100?
In Rust, F1 opens the console: type client.connect 101.81.76.35:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.