Offline 178.151.26.131:28015 checked 21d ago
MYASORUBKA
Connect
srv = rust.server("178.151.26.131: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 47% of all ranked servers, and #523 of the quad servers (top 64%). 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 8, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 17:03 UTC21d ago | 8 | NaN | running | 0 |
| 1 | Tue 6 Oct, 08:27 UTC21d ago | 8 | NaN | 0.4 days | 1 |
| 2 | Mon 5 Oct, 17:22 UTC22d ago | 8 | NaN | 0.6 days | 5 |
| 3 | Sun 4 Oct, 11:30 UTC23d ago | 7 | NaN | 1.2 days | 4 |
| 4 | Fri 2 Oct, 21:31 UTC24d ago | 7 | NaN | 1.6 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
- 178.151.26.131:28015
- region
- –
- max players
- 20
- group limit
- quad
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 17:03 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 | Rustoria.co -Us Mondays | NA · quad · 7 on average | 0/300 |
| 1 | [RU] Кубань PVP [Solo/Duo/Trio/Quad] | EU · quad · 6 on average | 6/60 |
| 2 | Geležinis Miškas | quad · 5 on average | 10/99 |
| 3 | LusoTuga Prime | EU | Vanilla | Biweekly | EU · quad · biweekly · 4 on average | 7/100 |
| 4 | Persona#1 |Для Новичков| х2 | EU · quad · monthly · 3 on average | 5/200 |
| 5 | [ESP] RUST ESPAÑA DISOBEY.COM.ES | EU · quad · monthly · 3 on average | 2/101 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does MYASORUBKA rank?
Over the last seven days MYASORUBKA sits at #10,548 on player hours, in the top 47% of ranked servers. The quad group places it at #523.
What population does MYASORUBKA carry?
The current row shows MYASORUBKA offline; the last response was 21 days ago.
About the server
What Rust version does MYASORUBKA run?
Rust network protocol 2634 and build 166586 on Windows is what MYASORUBKA runs. Steam updates your game for you, but the protocol must match to join.
How reliable is MYASORUBKA, and is it up?
Offline now for MYASORUBKA, last seen 21 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 2 October 2026.
Where does MYASORUBKA sit?
No region is published by MYASORUBKA. 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 178.151.26.131:28015.
Rules, settings, map
Which settings and rules does MYASORUBKA run?
The name MYASORUBKA carries no gather rate. Up to 4 players may share a group (quad). Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has MYASORUBKA selected?
A procedural map runs on MYASORUBKA, generated by the game.
Wipe data
When does MYASORUBKA wipe, and how often?
No next wipe can be predicted for MYASORUBKA, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 21 days 3 hours ago.
On MYASORUBKA, what happens on wipe day?
Recent wipes averaged 8 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does MYASORUBKA appear among Rust Data lists and filters?
On Rust Data, MYASORUBKA 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: Quad.
Which meanings do the tags on MYASORUBKA hold?
The game's server browser reads these tags from MYASORUBKA: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts4 (Group limit): Team size tops out at 4; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): The server runs build 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Join steps
How can I connect to MYASORUBKA?
Enter client.connect 178.151.26.131:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.