Offline 86.106.182.68:28025 checked 33d ago
linuxbench
Connect
srv = rust.server("86.106.182.68:28027")
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 · 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 24 Sep, 22:26 UTC34d ago | 0 | NaN | running | 0 |
| 1 | Thu 24 Sep, 14:51 UTC34d ago | 0 | NaN | 0.3 days | 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
- 86.106.182.68:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 22:26 UTC
- hostname
- –
- first seen
- 24 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 | 72/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 71/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 60/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 18/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does linuxbench rank?
Player hours over seven days put linuxbench at #16,487, in the top 71% of the ranked set.
What population does linuxbench carry?
Offline now for linuxbench, with the last sample 33 days 3 hours ago.
Server data
What Rust version does linuxbench run?
Rust network protocol 2633 and build 165217 on Linux is what linuxbench runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is linuxbench, and is it up?
The latest sample has linuxbench offline, with a last sighting 33 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 24 September 2026.
Where does linuxbench sit?
For linuxbench, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 86.106.182.68:28025.
Settings and map
Which rules apply on linuxbench, and what settings?
You will not find a gather rate in the string linuxbench. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has linuxbench selected?
linuxbench runs a procedural map, which the game generates.
Wipe schedule
When does linuxbench wipe, and on what schedule?
Too few wipes are on record for linuxbench to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 34 days ago, and that is the one in play.
What is wipe day on linuxbench like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does linuxbench appear among Rust Data lists and filters?
The Rust Data lists that linuxbench fits are: 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 linuxbench?
The game's server browser reads these tags from linuxbench: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Recorded game build: 165217; 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. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into linuxbench?
In Rust, F1 opens the console: type client.connect 86.106.182.68:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.