Rust Data

rustdata.spaceservers178.151.26.131:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 178.151.26.131:28015 checked 21d ago

MYASORUBKA

quad moddedoxide

Connect

srv = rust.server("178.151.26.131:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 4/20 # 20% full
7-day average 0 # peak –
rank #10,548 # top 47%
last wipe 21d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k2 Oct4 Oct6 Oct9 Oct11 Oct13 Oct

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.

usual gap0.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak8players, last three wipes

The first 48 hours of its last wipes

Tue 6 OctTue 6 OctMon 5 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 8, 1 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_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

No map picture published
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)
serverlike_thisplayers
0Rustoria.co -Us MondaysNA · quad · 7 on average0/300
1[RU] Кубань PVP [Solo/Duo/Trio/Quad]EU · quad · 6 on average6/60
2Geležinis Miškasquad · 5 on average10/99
3LusoTuga Prime | EU | Vanilla | BiweeklyEU · quad · biweekly · 4 on average7/100
4Persona#1 |Для Новичков| х2EU · quad · monthly · 3 on average5/200
5[ESP] RUST ESPAÑA DISOBEY.COM.ESEU · quad · monthly · 3 on average2/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.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2634,gmrust,cs166586,ts4,^o^z

Game

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.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 83,714 players 11,847 servers online