On the class lists: D (51), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak 1
Rank#9,852top 45%
Last wipe5d 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 40 on average. Plenty of space to grow.
Standingrank on player hours
55/ 100
C−
Working its way up from the back of the class: #9,852 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 148 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
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 45% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
··
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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 16:04 UTC5d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
$MONZ$ leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 157.85.93.245:28683.
Is $MONZ$ up, and how steady is its uptime?
You can join now: $MONZ$ is online. According to its reported uptime, the last restart was about 5 days 3 hours ago. It was up 100% of the time over the last 4 full days, 96 of 96 hours. The first sighting by Rust Server Score was on 22 October 2026.
How well does $MONZ$ run?
The average over the last 48 hours was 148 server fps, and it never went below 113. At its peak, it held 48,549 entities, including buildings, deployables and all else in the world. Up to 5,411 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does $MONZ$ sit?
Rust network protocol 2634 and build 167781 on Linux is what $MONZ$ runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does $MONZ$ wipe its map?
There are too few wipes on record for $MONZ$ to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 5 days 4 hours.
What should you expect from wipe day on $MONZ$?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does $MONZ$ place in the wider field of Rust servers?
Over the last seven days, $MONZ$ has #9,852 for player hours, in the top 45% of all ranked servers.
Is $MONZ$ a busy server?
With 40 slots available, $MONZ$ currently has 0 players. The seven-day average is 0 players, with a peak of 1.
Lists and filters
How should you read the tags on $MONZ$?
The game's browser takes its cue from the tags $MONZ$ has set: gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does $MONZ$ appear in the Rust Server Score lists and filters?
Rust Server Score lists that include $MONZ$: 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; Last wipe: In the last week.
Rules and settings
Which rules does $MONZ$ enforce, and what are its settings?
You will find no gather rate in the name of $MONZ$. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on $MONZ$?
$MONZ$ runs a game-generated procedural map at size 3,000, seed 50000. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to $MONZ$?
Enter client.connect 157.85.93.245:28683 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 asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max players40 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).