Rust StatisticsWorking papers on every public Rust server · 89,289 players now

MORU RustServer s1

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 3h ago · 220.158.16.162:28015

Abstract

We describe the public Rust server MORU RustServer s1, reached at 220.158.16.162:28015. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 11. It ranks #5,783 of all servers, the top 26%. It last wiped 26d ago.

Keywordsmodded 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 now0/500% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#5,783top 26%
Last wipe26d agono schedule published
Next wipe3–too few wipes seen yet

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.

AveragePeak
00.250.50.75121:0006:0015:0023:0008:0017:00
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
05010015020021:0006:0015:0023:0008:0017:00
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, measured since 17 Sep.

4Rank

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

RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.3 daysbetween real wipes
Wipe-day peak2players, last three wipes
Fri 2 OctThu 1 Oct
00.511.52+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 2, 10 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 2 Oct, 06:2426d ago 2 – running 0
Thu 1 Oct, 22:48fw26d ago 2 – 0.3 d 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. 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

Map of MORU RustServer s1
Figure 5: The map: Custom Map, size 4500, seed 19686.
Table 4: The server's published settings.
Address220.158.16.162:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe2 Oct 2026, 06:24 UTC
Hostname–
First seen13 Sep 2026
MapCustom Map
Size4500
Seed19686

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 157 on average205/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average121/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average183/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average126/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average19/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1How well does MORU RustServer s1 run?

Its average server fps over the last 48 hours was 119, with a minimum of 95. The highest number of entities it carried was 88,803, comprising buildings, deployables and all other objects. Memory use peaked at 3,427 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is MORU RustServer s1 based?

A region is not published by MORU RustServer s1. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 220.158.16.162:28015 is its address.

A.3What is the online status and reliability of MORU RustServer s1?

MORU RustServer s1 is currently online. The uptime it reports indicates a restart about 19 hours ago. The server was up 100% of the time over the last 7 full days, 168 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on MORU RustServer s1?

The version of Rust on MORU RustServer s1 is network protocol 2635 and build 168909, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.5What schedule does MORU RustServer s1 follow for wipes?

Too few wipes by MORU RustServer s1 have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 26 days 13 hours have passed since the current world was generated.

A.6What happens on MORU RustServer s1 when wipe day arrives?

Recent wipes saw an average peak of 2 players. The peak on the latest wipe came 10 hours after it began.

Population

A.7How does MORU RustServer s1 compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts MORU RustServer s1 at #5,783, within the top 26% of ranked servers.

A.8How would you characterise the player activity on MORU RustServer s1?

The current population of MORU RustServer s1 is 0, drawn from 50 slots. Averaged over the last seven days: 0 players; the same period peaks at 1. The busiest hour of the last 48 is 00:00 UTC, averaging 1 players.

Tags and filters

A.9What do the tags associated with MORU RustServer s1 signify?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; 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): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which MORU RustServer s1 publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can MORU RustServer s1 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that MORU RustServer s1 fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.11Under what rules and settings does MORU RustServer s1 operate?

No gather rate appears in the name of MORU RustServer s1. At 8 players, the group limit equals the game's default. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.

A.12On which map does MORU RustServer s1 take place?

The game generates MORU RustServer s1's procedural map at size 4,500, from seed 19686. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page. The name of the map is Custom Map.

How to join

A.13What is the process for joining MORU RustServer s1?

Press F1 inside Rust to open the console and enter client.connect 220.158.16.162: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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp50Max players. The slot count is 50.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
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. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.