On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 8
Rank#3,220top 14% · #1194 in EU
Last wipe13d agobiweekly schedule
Next wipe4hThu 29 Oct, 02:17 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,220 on player hours.
Uptimehours on the list, last 48
83/ 100
B+
Missed a few lessons: on the list 40 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 119 server fps on average.
Wipeskeeping the crowd after a wipe
67/ 100
C+
Keeps a fair share of its players through a wipe: 67% of wipes kept half their crowd.
Momentumrank now against a week ago
40/ 100
F
Slipped a little: down 650 places this week. Nothing a good wipe can't fix.
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 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 14% of all ranked servers, top 41% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·····WW
···F···
·······
···W···
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 02:17 UTC, in 4h.
Its biweekly schedule tag · low confidence
usual gap7.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak7players, last three wipes
crowd held67%else halves by day 7
Coming wipes
4hThu 29 Oct, 02:17 UTC
7d 20hThu 5 Nov, 19:00 UTCFW
14d 4hThu 12 Nov, 02:17 UTC
28d 4hThu 26 Nov, 02:17 UTC
35d 20hThu 3 Dec, 19:00 UTCFW
42d 4hThu 10 Dec, 02:17 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctSun 27 Sep
Players each hour, from the hour of the wipe. The latest peaked at 7, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 02:17 UTC13d ago
7
–
running
0
Thu 1 Oct, 17:50 UTCFW27d ago
8
halved by day 7
13.4 days
2
Sun 27 Sep, 04:01 UTC31d ago
6
✓ held half
4.6 days
0
Sat 26 Sep, 18:14 UTC32d ago
6
–
0.4 days
2
Thu 17 Sep, 02:12 UTC41d ago
7
✓ held half
9.7 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
In Europe, according to its own listing, sits M_SERVER PVE, with the EU tag. Rust Server Score takes the server's word for its location and does not trace the hardware. 94.154.200.202:28016 is the address to use.
How dependable is M_SERVER PVE, and is it online at the moment?
The server is up: M_SERVER PVE is online now. About 6 minutes ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 150 of 168 hours, or 89% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is M_SERVER PVE smooth to play on?
It averaged 119 server fps over the last 48 hours, with a low of 114. At its peak, it held 134,882 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,673 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does M_SERVER PVE sit?
You will find M_SERVER PVE on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
When does M_SERVER PVE wipe, and how often?
Too few wipes on M_SERVER PVE are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Thursday 29 October at 02:17 UTC. The world it runs now was created 13 days 19 hours. Its tags say it wipes every two weeks.
What should you expect from wipe day on M_SERVER PVE?
The average peak on its recent wipes was 7 players. Peak numbers came 14 hours into the latest wipe. Half the peak held until the next wipe in 67% of its recent wipes. Day 7 is when it sank below half in the wipes that did not hold.
Player count
What position does M_SERVER PVE hold in the rankings?
In Europe, M_SERVER PVE is #1,194, and overall it is #3,220 on player hours over the last seven days, in the top 14% of all ranked servers.
How many players does M_SERVER PVE usually have?
With 100 slots available, M_SERVER PVE currently has 0 players. It peaked at 8 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 17:00 UTC, with 4 players.
Tags and filters
What is meant by the tags on M_SERVER PVE?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks it wipes; ^e (Minigames): It hosts minigames such as arenas, Bedwars and parkour; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EU (Europe): In the server browser it appears under Europe are the tags M_SERVER PVE publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Who is behind M_SERVER PVE?
Among all the servers we track, only M_SERVER PVE publishes this m-server.pp.ua hostname.
Which Rust Server Score filters and lists feature M_SERVER PVE?
Rust Server Score lists that include M_SERVER PVE: European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Minigames ^e, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Map and rules
Which rules does M_SERVER PVE enforce, and what are its settings?
You will find no gather rate in the name of M_SERVER PVE. With no change from the game default, groups take up to 8 players. minigames & battle royale is the mode here, battle royale, arenas, parkour and Bedwars. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map M_SERVER PVE uses?
A procedural map of size 4,500 and seed 1090470307, generated by the game, is what M_SERVER PVE runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join M_SERVER PVE?
Enter client.connect 94.154.200.202:28016 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://M-SERVER.pp.ua/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,^e,EU,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^e
MinigamesIt hosts minigames such as arenas, Bedwars and parkour.
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EU
EuropeIn the server browser it appears under Europe.
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).