Station EU-3138 · recording
M_SERVER PVE
Online EU 94.154.200.202:28016 checked 12m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 8
- Rank
- #3,138
- top 14% · #1176 in EU
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 19h
- Thu 29 Oct, 02:17 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −3into Tue 18:00 UTC
- Peak · 48 h
- 4most players in any hour
Players
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 19h. Its biweekly schedule tag · low confidence
- usual gap
- 7.1 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 7players, last three wipes
- crowd held
- 67%else halves by day 7
Coming wipes
- 19hThu 29 Oct, 02:17 UTC
- 8d 12hThu 5 Nov, 19:00 UTCFW
- 14d 19hThu 12 Nov, 02:17 UTC
- 28d 19hThu 26 Nov, 02:17 UTC
- 36d 12hThu 3 Dec, 19:00 UTCFW
- 42d 19hThu 10 Dec, 02:17 UTC
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 02:17 UTC13d ago | M0.8▲rising | 7 | – | running | 0 | |
| Thu 1 Oct, 17:50 UTC FW26d ago | M0.8▲rising | 8 | halved by day 7 | 13.4 days | 2 | |
| Sun 27 Sep, 04:01 UTC31d ago | M0.8▲rising | 6 | held half | 4.6 days | 0 | |
| Sat 26 Sep, 18:14 UTC31d ago | M0.6▲rising | 6 | – | 0.4 days | 2 | |
| Thu 17 Sep, 02:12 UTC41d ago | M0.8▲rising | 7 | held half | 9.7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on M_SERVER PVE?
The procedural map on M_SERVER PVE is size 4,500 with seed 1090470307, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on M_SERVER PVE?
The name of M_SERVER PVE gives no gather rate. Groups hold up to 8 players, which is the default for the game. minigames & battle royale is the game mode, parkour, Bedwars, battle royale and arenas. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on M_SERVER PVE?
A reading taken now shows 0 players on M_SERVER PVE, which has 100 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 8. The busiest point in the last 48 hours came at 17:00 UTC, averaging 4 players.
How does M_SERVER PVE rank against other Rust servers?
For player hours across the last seven days, M_SERVER PVE takes #3,138 overall and #1,176 in Europe, inside the top 14% of all ranked servers.
Server details
How reliably does M_SERVER PVE stay online?
Right now, you can reach M_SERVER PVE. Its reported uptime points to a restart about 54 minutes ago. 150 of 168 hours in the last 7 full days were up time, 89% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
How well does M_SERVER PVE perform under load?
Across the last 48 hours it averaged 119 server fps, with a floor of 115. At its highest, it carried 134,882 entities: buildings, deployables and the world's other contents. Memory use peaked at 4,673 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does M_SERVER PVE run from?
The EU tag is how M_SERVER PVE lists itself in Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 94.154.200.202:28016.
What build of Rust does M_SERVER PVE use?
Rust network protocol 2635 and build 168909 on Linux is what M_SERVER PVE runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on M_SERVER PVE?
7 players, on average, was the busiest crowd at its recent wipes. 14 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 67% of its recent wipes. By day 7 it fell below half in the wipes where it didn't hold.
How often does M_SERVER PVE wipe, and on which days?
The prediction is taken from its tag, since M_SERVER PVE has too few wipes on record to confirm the schedule. The date of its next wipe is Thursday 29 October at 02:17 UTC. It has run its current world for 13 days 4 hours. Its tags state that it wipes every two weeks.
Server tags
What do the server tags on M_SERVER PVE mean?
These are the tags M_SERVER PVE publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^e (Minigames): This server hosts minigames: arenas, Bedwars, parkour and more; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EU (Europe): The server browser files it under Europe. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does M_SERVER PVE appear?
These Rust Server Trends lists include M_SERVER PVE: EU Rust servers, Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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.
Who is behind M_SERVER PVE?
No other server we track uses the m-server.pp.ua hostname that M_SERVER PVE publishes.
How to join
How do you connect to M_SERVER PVE?
Enter client.connect 94.154.200.202:28016 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://M-SERVER.pp.ua/.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.