On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 1
Rank#13,093top 59%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
41/ 100
F
Working its way up from the back of the class: #13,093 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
99/ 100
A+
Runs smoothly: 59 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 5,493 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···FW··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 10:02 UTC26d ago
4
–
running
0
Thu 1 Oct, 20:15 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Mogu_Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 163.44.159.125:28015.
How dependable is Mogu_Server, and is it online at the moment?
You can join now: Mogu_Server is online. The uptime it reports puts the last restart at about 3 days 9 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Mogu_Server run?
The average over the last 48 hours was 59 server fps, and it never went below 50. Up to 129,894 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 4,405 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is Mogu_Server running?
The server Mogu_Server is on Rust network protocol 2634 and build 166494 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Mogu_Server wipe, and how often?
Mogu_Server has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 26 days 20 hours.
What happens on Mogu_Server when wipe day arrives?
Across its recent wipes, the busiest moments averaged 4 players. The crowd on the latest wipe was largest 6 hours after it began.
Player count
What position does Mogu_Server hold in the rankings?
Over the last seven days, Mogu_Server has #13,093 for player hours, in the top 59% of all ranked servers.
What does the population on Mogu_Server look like?
With 20 slots available, Mogu_Server currently has 0 players. It peaked at 1 and averaged 0 players over the last seven days.
Tags and filters
What is meant by the tags on Mogu_Server?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Mogu_Server publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Mogu_Server?
These Rust Server Score lists count Mogu_Server among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Mogu_Server?
Nothing in the name of Mogu_Server states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Mogu_Server?
Mogu_Server runs a game-generated procedural map at size 4,500, seed 1683482379. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto Mogu_Server?
Enter client.connect 163.44.159.125:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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.
A term to build on. Strongest in performance (A+); population is the one to work on (F).