Rust Data LabData lab · live
Live readings Servers11,757 Players71,901 Populated3,470 Fresh wipes · 3h213 Sampled every 5 min

Element card · group Modded · atomic number 15,290, its rank

Mogu_Server

Online 163.44.159.125:28015 checked 10m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 20 0% full Room to join
7-day average0peak –
Rank · atomic number#15,290top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123400:0009:0019:0003:0012:0021:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608000:0009:0019:0003:0012:0021:00

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. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

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.

usual gap0.6 daysbetween real wipes
wipe-day peak4players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 10:02 UTC27d ago 4 – running 0
Thu 1 Oct, 20:15 UTC FW28d ago 4 – 0.6 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 33
    ShockRust | Blue | NoLimit no group limit · 149 on average 33/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 127
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 127/ 100
  3. 3 Re RETRO RUST #1 … 65
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average 65/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 20
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average 20/ 700
  5. 5 Ru 404 RUST 2Х|ДЛ… 67
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 93 on average 67/ 700
  6. 6 Ru RustSpain.com … 267
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average 267/ 310

Quick answers

from the figures on this page

Map and rules

What map is in play on Mogu_Server?

The map on Mogu_Server is procedural at size 4,500 with seed 1683482379, made by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

What rules has Mogu_Server set, and what settings are in force?

The name of Mogu_Server carries no gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running on it. The VAC anti-cheat from Valve is enabled.

Server details

What region hosts Mogu_Server?

Nothing about a region is published by Mogu_Server. Rust Data Lab shows a server's stated location, not a verified position of the machine. 163.44.159.125:28015 is the address it uses.

Which Rust version is Mogu_Server on?

On Linux, Mogu_Server is running Rust network protocol 2634 and build 166494. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does Mogu_Server stay online?

Right now, Mogu_Server is reachable. According to the uptime it reports, the last restart was about 4 days 1 hours ago. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. It first appeared to Rust Data Lab on 13 September 2026.

How well does Mogu_Server perform?

The last 48 hours show an average of 59 server fps and a minimum of 50. Buildings, deployables and everything else in the world added up to as many as 129,895 entities. Up to 4,405 MB of memory was used. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe days

What is the wiping pattern on Mogu_Server?

Too few wipes are on record for Mogu_Server to reveal a rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 27 days 13 hours ago.

How does Mogu_Server look on the day of a wipe?

At their busiest, recent wipes averaged 4 players. 6 hours after the latest wipe, the crowd peaked.

Where it appears

What should you understand from the tags Mogu_Server carries?

The game's server browser reads the tags Mogu_Server publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): 20 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166494 (Build): Build number: 166494; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does Mogu_Server come up?

You will find Mogu_Server on the following Rust Data Lab lists: Modded Rust servers, measured. You can find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

How does Mogu_Server compare with other servers in the rankings?

The seven-day player-hours table has Mogu_Server at #15,290, in the top 69% of ranked servers.

How full is Mogu_Server right now?

Of 20 slots, 0 are taken on Mogu_Server right now. The past week gives an average of 0 players.

Connection

What steps get you onto Mogu_Server?

In Rust, press F1 and enter client.connect 163.44.159.125:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp20
Max players 20 is the slot count.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166494
Build Build number: 166494.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under 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.