Offline 135.106.180.14:27162 checked 26d ago
beshanov rust
Connect
srv = rust.server("135.106.180.14:27163")
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, measured since 2 Oct. 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 61% 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 3, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 10:19 UTC26d ago | 3 | NaN | running | 1 |
| 1 | Fri 2 Oct, 13:45 UTC27d ago | 4 | NaN | 0.9 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
3650 · seed 2046894025
- map
- Procedural Map
- size
- 3650
- seed
- 2046894025
Server
srv.info()- address
- 135.106.180.14:27162
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 10:19 UTC
- hostname
- –
- first seen
- 2 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 · 149 on average | 29/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 15/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 52/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 221/260 |
Quick answers
From the figures on this page.
Player counts
How does beshanov rust compare in the rankings?
Over the last seven days beshanov rust sits at #13,904 on player hours, in the top 61% of ranked servers.
How many players does beshanov rust hold at once?
beshanov rust returns no live count at this refresh, having last been seen 26 days 10 hours ago.
Server data
What Rust version does beshanov rust run?
Rust network protocol 2634 and build 166586 on Linux is what beshanov rust runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is beshanov rust, and is it up?
The latest sample has beshanov rust offline, with a last sighting 26 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 2 October 2026.
Where does beshanov rust sit?
There is no region published for beshanov rust. 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 135.106.180.14:27162.
Rules, settings, map
What rules and settings are recorded for beshanov rust?
You will not find a gather rate in the string beshanov rust. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on beshanov rust?
beshanov rust runs a procedural map of size 3,650 with seed 2046894025, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does beshanov rust wipe, and on what schedule?
A rhythm cannot be read from the wipes of beshanov rust on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 13 hours ago.
On beshanov rust, what happens on wipe day?
Across recent wipes the busiest point averaged 4 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold beshanov rust, and which filters?
The Rust Data lists that beshanov rust fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on beshanov rust?
The game's server browser reads these tags from beshanov rust: 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; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to beshanov rust?
In Rust, F1 opens the console: type client.connect 135.106.180.14:27162. Launch Rust on this page does the same by opening the game through Steam and connecting.