Rust StatisticsWorking papers on every public Rust server · 46,119 players now

MYASORUBKA

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 21d ago · 178.151.26.131:28015

Abstract

We describe the public Rust server MYASORUBKA, reached at 178.151.26.131:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #10,548 of all servers, the top 47%. It last wiped 21d ago.

Keywordsquad modded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now4/2020% full
In the queue0no queue
Seven-day mean0peak –
Rank2#10,548top 47%
Last wipe21d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 47% of all ranked servers, and #523 of the quad servers (top 64%). Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k2 Oct4 Oct6 Oct9 Oct11 Oct13 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.9 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak8players, last three wipes
Tue 6 OctTue 6 OctMon 5 Oct
02468+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Tue 6 Oct, 17:0321d ago 8 – running 0
Tue 6 Oct, 08:2721d ago 8 – 0.4 d 1
Mon 5 Oct, 17:2222d ago 8 – 0.6 d 5
Sun 4 Oct, 11:3023d ago 7 – 1.2 d 4
Fri 2 Oct, 21:3125d ago 7 – 1.6 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address178.151.26.131:28015
Region–
Max players20
Group limitquad
Wipe schedule–
Last wipe6 Oct 2026, 17:03 UTC
Hostname–
First seen2 Oct 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[RU] Кубань PVP [Solo/Duo/Trio/Quad]EU · quad · 6 on average1/60
Geležinis Miškasquad · 5 on average0/99
#MAGIC JUMP | ЛУТ ЗА ПРЫЖКИ | Вайп 23.10EU · quad · biweekly · 5 on average0/80
LusoTuga Prime | EU | Vanilla | BiweeklyEU · quad · biweekly · 4 on average1/100
Persona#1 |Для Новичков| х2EU · quad · monthly · 3 on average1/200
[EU] Protobit: No Offline | Shared BPs | Max 4 | Linux FriendlyEU · quad · biweekly · 3 on average1/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does MYASORUBKA have?

No region is published by MYASORUBKA. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 178.151.26.131:28015.

A.2What is the reliability of MYASORUBKA, and is it online?

Right now, MYASORUBKA is offline, and the last time it was seen was 21 days 5 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 2 October 2026.

A.3What version of Rust is run on MYASORUBKA?

Rust network protocol 2634 and build 166586 is the version that MYASORUBKA runs, on Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does MYASORUBKA follow for wipes?

With irregular wipe times, MYASORUBKA offers no next wipe to predict. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 21 days 8 hours ago.

A.5How would you describe wipe day on MYASORUBKA?

The average busiest point of recent wipes was 8 players. The crowd reached its maximum 1 hours after the latest wipe.

Population

A.6How does MYASORUBKA compare with other Rust servers in the rankings?

Ranked by player hours across seven days, MYASORUBKA holds #10,548, in the top 47% of all ranked servers. Within the quad group, its position is #523.

A.7At what level does MYASORUBKA operate in terms of players?

MYASORUBKA is not online now; 21 days 5 hours have passed since it was last seen.

Tags, lists

A.8What do the tags associated with MYASORUBKA signify?

gmrust (Game mode): Survival on standard Rust rules; mp20 (Max players): The slot count is 20; ts4 (Group limit): A team holds no more than 4; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166586 (Build): This server runs game build 166586; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags MYASORUBKA publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can MYASORUBKA be found among the Rust Statistics lists and filters?

The Rust Statistics lists that MYASORUBKA fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad.

Rules, settings, map

A.10What are the settings and rules that govern MYASORUBKA?

Its name carries no gather rate for MYASORUBKA. quad sets the team size at 4 players. The mode is survival, which means gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.

A.11What map is in use on MYASORUBKA?

The game generates the map on MYASORUBKA; that format is procedural.

Connection

A.12What steps are required to join MYASORUBKA?

Press F1 inside Rust to open the console and enter client.connect 178.151.26.131:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp20,ptrak,$r?,v2634,gmrust,cs166586,ts4,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp20Max players. The slot count is 20.
ts4Group limit. A team holds no more than 4.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166586Build. This server runs game build 166586.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.