M_SERVER PVE
Online EU 94.154.200.202:28016 checked 9m ago
Server instruments
last reading Tue 17:00 UTCPlayers now
1% full 7-day avg7-day peakServer fps
48 h low 113 · below 20 is lag, below 10 is badEntities
48 h range 127,152–134,882 · memory 3,582 MBUptime
1 h 43 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 14% of all ranked servers, top 40% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 02:17 UTC, in 1d 7h. Its biweekly schedule tag · low confidence
Coming wipes
- WPT 1Thu 29 Oct, 02:17 UTC1d 7h
- WPT 2Thu 5 Nov, 19:00 UTC9d 0hFW
- WPT 3Thu 12 Nov, 02:17 UTC15d 7h
- WPT 4Thu 26 Nov, 02:17 UTC29d 7h
- WPT 5Thu 3 Dec, 19:00 UTC37d 0hFW
- WPT 6Thu 10 Dec, 02:17 UTC43d 7h
The first 48 hours of its last wipes
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 UTC12d ago | 7 | – | running | 0 |
| Thu 1 Oct, 17:50 UTC FW26d ago | 8 | halved by day 7 | 13.4 days | 2 |
| Sun 27 Sep, 04:01 UTC30d ago | 6 | held half | 4.6 days | 0 |
| Sat 26 Sep, 18:14 UTC31d ago | 6 | – | 0.4 days | 2 |
| Thu 17 Sep, 02:12 UTC40d 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
the same kind of game, then region, group limit, rate and wipes- 3/22
- 8/100
- 9/200
- 10/100
- 5/40
- 1/30
Quick answers
from the figures on this pageWipe timing
What happens on M_SERVER PVE when wipe day comes?
The busiest point of its recent wipes drew 7 players on average. Peak crowd on the latest wipe: 14 hours in. Until the next wipe, the crowd stayed above half that peak in 67% of its recent wipes. When it didn't hold, by day 7 it fell below half.
What wipe timing does M_SERVER PVE follow?
The prediction follows its tag, because too few of M_SERVER PVE's wipes are on record to confirm its schedule. Due on Thursday 29 October at 02:17 UTC is its next wipe. 12 days 16 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.
Tag meanings
Which tags does M_SERVER PVE carry, and what do they mean?
These are the tags M_SERVER PVE publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^e (Minigames): Minigames run here: arenas, Bedwars, parkour and more; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; EU (Europe): Europe is the browser category it sits in. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which operator is behind M_SERVER PVE?
Check: operator. The m-server.pp.ua hostname comes from M_SERVER PVE alone; no other server we track uses it.
Which lists and filters on Rust Metrics show M_SERVER PVE?
On Rust Metrics, M_SERVER PVE sits in these lists: EU Rust servers, checked, Modded Rust servers, checked live and Rust PvE servers. These filters bring it up 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.
Player count
What position does M_SERVER PVE hold among Rust servers?
Ranked by seven-day player hours, M_SERVER PVE sits at #3,134 and #1,178 in Europe, inside the top 14%.
What player count does M_SERVER PVE carry?
Current headcount on M_SERVER PVE: 1 players, 100 slots available. Check: players over seven days. Average 1, peak 8. Check: 48-hour peak. 17:00 UTC, 4 players on average.
Server
What location is M_SERVER PVE hosted in?
Its EU tag places M_SERVER PVE in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 94.154.200.202:28016.
What Rust version is M_SERVER PVE on?
Reading: M_SERVER PVE, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
How does M_SERVER PVE perform?
Check: fps. Average 118 server fps over the last 48 hours, low of 113. Within range. Reading: 134,882 entities at the highest. That covers buildings, deployables and everything else. Reading: 5,109 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on M_SERVER PVE, and is it online?
Check: connection. M_SERVER PVE is online at this moment. Check: restart. The uptime it reports puts the last restart about 1 hours ago. Reading: 90% uptime over the last 7 full days. It was up 152 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What rules does M_SERVER PVE enforce, and what are its settings?
Check: gather rate. The name M_SERVER PVE does not state one. 8 players per group, the default value. Mode check gives minigames & battle royale; battle royale, parkour, Bedwars and arenas. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
What map is M_SERVER PVE on?
Size 4,500 and seed 1090470307: the game generates the procedural map on M_SERVER PVE from them. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
What do you do to join M_SERVER PVE?
To join: start Rust, press F1 and type client.connect 94.154.200.202:28016. Or press Launch Rust here and Steam opens the game and connects you. https://M-SERVER.pp.ua/ is where its website sits.