Station XX-10287 · recording
ZMADHOUSE PVE
Online 95.216.228.189:7781 checked 8m ago
- Players now
- 0/ 70
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #10,287
- top 46%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 70 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +0into Wed 07:00 UTC
- Peak · 48 h
- 1most 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 13 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 46% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 06:01 UTC10d ago | M0.3▲rising | 3 | – | running | 1 |
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 ZMADHOUSE PVE?
The procedural map on ZMADHOUSE PVE is size 3,500 with seed 2147483647, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on ZMADHOUSE PVE?
No gather rate appears in the name of ZMADHOUSE PVE. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on ZMADHOUSE PVE right now?
At this moment, ZMADHOUSE PVE records 0 players across 70 slots. Across seven days this server recorded an average of 0 players and a peak of 1. The busiest point in the last 48 hours came at 06:00 UTC, averaging 0 players.
How does ZMADHOUSE PVE rank against other Rust servers?
Over the last seven days, ZMADHOUSE PVE recorded enough player hours to reach #10,287 worldwide, placing it in the top 46% of all ranked servers.
Operator and location
How reliably does ZMADHOUSE PVE stay online?
ZMADHOUSE PVE is up at the moment. Going by the uptime figure it reports, it restarted about 6 days 21 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.
How well does ZMADHOUSE PVE perform under load?
Its average server fps over the last 48 hours was 112, and it never dropped below 90. The world held up to 76,405 entities at its peak, buildings and deployables included. Memory use peaked at 5,247 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is ZMADHOUSE PVE hosted?
No region is published by ZMADHOUSE PVE. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 95.216.228.189:7781.
Which Rust version is ZMADHOUSE PVE running?
On Windows, ZMADHOUSE PVE runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on ZMADHOUSE PVE?
3 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does ZMADHOUSE PVE run its wipes?
On record so far are too few of ZMADHOUSE PVE's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 10 days 15 hours.
Server tags
What do the server tags on ZMADHOUSE PVE mean?
Tags published by ZMADHOUSE PVE and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp70 (Max players): 70 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; 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): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does ZMADHOUSE PVE appear?
These Rust Server Trends lists include ZMADHOUSE PVE: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
How do you connect to ZMADHOUSE PVE?
To join, enter client.connect 95.216.228.189:7781 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. For the website, go to https://www.gameserverapp.com.
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.