Online EU 94.154.200.202:28016 checked 12m ago
M_SERVER PVE
Connect
srv = rust.server("94.154.200.202:28015")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 15% of all ranked servers, top 41% in EU. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 29 October, 02:17 UTC, in 2h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 2h | Thu 29 Oct, 02:17 UTC | wipe |
| 1 | 7d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 14d 2h | Thu 12 Nov, 02:17 UTC | wipe |
| 3 | 28d 2h | Thu 26 Nov, 02:17 UTC | wipe |
| 4 | 35d 19h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 42d 2h | Thu 10 Dec, 02:17 UTC | wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 02:17 UTC13d ago | 7 | NaN | running | 0 |
| 1 | Thu 1 Oct, 17:50 UTC FW27d ago | 8 | halved by day 7 | 13.4 days | 2 |
| 2 | Sun 27 Sep, 04:01 UTC31d ago | 6 | held half | 4.6 days | 0 |
| 3 | Sat 26 Sep, 18:14 UTC32d ago | 6 | NaN | 0.4 days | 2 |
| 4 | 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.
display(srv.map, srv.info())Map
4500 · seed 1090470307
- map
- Procedural Map
- size
- 4500
- seed
- 1090470307
Server
srv.info()- address
- 94.154.200.202:28016
- region
- EU
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 02:17 UTC
- hostname
- pve.m-server.pp.ua
- first seen
- 13 Sep 2026
Operator · m-server.pp.ua
rust.servers(operator="m-server.pp.ua").sort_values("players")| server | players |
|---|
The only server publishing a m-server.pp.ua hostname.
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | RUMINI-Rust =|PVE|Нервы|На|Пределе|= | EU · groups of 8+ · monthly · 2 on average | 3/22 |
| 1 | RUSTILA PVE | SKINDROP | RAIDS | SKILL | KIT | TP | WIPED 15.10 | groups of 8+ · biweekly · 10 on average | 3/100 |
| 2 | BladeRust #PvE MARAUDER [ SKILLS | MODS | BOSS | CUSTOM WEAPONS | groups of 100+ · biweekly · 7 on average | 3/200 |
| 3 | EU GOM 25x Monthly PVE Grumpy Old Man |Kits|Skins|BackPack|Shop | EU · groups of 15+ · 25x · monthly · 5 on average | 2/100 |
| 4 | №[2] D2S Chaotica PvE 1000 Zombies|Raidable Bases|Monthly|Sho | groups of 16+ · monthly · 2 on average | 3/40 |
| 5 | Fusion 3.64 (test) | groups of 8+ · monthly · 1 on average | 2/30 |
Quick answers
From the figures on this page.
Population data
How does M_SERVER PVE compare in the rankings?
Ranked #3,230 on seven-day player hours, M_SERVER PVE is #1,200 in Europe and in the top 15% of all ranked servers.
How many players does M_SERVER PVE hold at once?
Current row: 0 players on M_SERVER PVE, against 100 slots. Over the last seven days it averaged 1 players and peaked at 8. Peak hour in the last 48 hours: 17:00 UTC, mean 4 players.
Server data
How well does M_SERVER PVE perform?
Server fps over the last 48 hours averages 119; the floor is 114. Buildings, deployables and all else in the world took the count as high as 134,882 entities. Memory peaked at 4,673 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is M_SERVER PVE on?
Rust network protocol 2635 and build 168909 on Linux is what M_SERVER PVE runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is M_SERVER PVE, and is it up?
The current sample puts M_SERVER PVE online. A restart about 2 hours ago is what its reported uptime implies. Uptime of 89% across the last 7 full days: 150 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does M_SERVER PVE run from?
In Europe, M_SERVER PVE lists itself, using the EU tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 94.154.200.202:28016 is its address.
Map and rules
What rules and settings are recorded for M_SERVER PVE?
You will not find a gather rate in the string M_SERVER PVE. No custom cap; the default of 8 players per group stands. Game mode minigames & battle royale, with this note: parkour, Bedwars, battle royale, arenas. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on M_SERVER PVE?
M_SERVER PVE runs a procedural map of size 4,500 with seed 1090470307, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does M_SERVER PVE wipe?
The tag sets the prediction: M_SERVER PVE has too few wipes on record to confirm its schedule. Thursday 29 October at 02:17 UTC is when the next wipe is due. The world it runs now was generated 13 days 21 hours ago. A fortnightly wipe schedule is published in its tags.
On M_SERVER PVE, what happens on wipe day?
Across recent wipes the busiest point averaged 7 players. Peak population on the latest wipe came 14 hours in. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. Otherwise the crowd fell below half by day 7.
Lists and tags
Where does M_SERVER PVE appear among Rust Data lists and filters?
On Rust Data, M_SERVER PVE appears in these lists: EU Rust servers, Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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 operates M_SERVER PVE?
No other server we track uses the m-server.pp.ua hostname that M_SERVER PVE publishes.
How should you read the server tags on M_SERVER PVE?
The game's server browser reads these tags from M_SERVER PVE: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^e (Minigames): Runs minigames such as arenas, Bedwars and parkour; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; EU (Europe): In the server browser it sits under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to M_SERVER PVE?
In Rust, F1 opens the console: type client.connect 94.154.200.202:28016. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://M-SERVER.pp.ua/.