On the class lists: D (45), with population over 48 hours and no performance mark.
Players now0/ 700% full
7-day average0peak 1
Rank#10,306top 46%
Last wipe10d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 70 on average. Plenty of space to grow.
Standingrank on player hours
54/ 100
D
Working its way up from the back of the class: #10,306 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 112 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
32/ 100
F
Lost ground: down 3,711 places this week. A strong wipe could turn it round.
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 13 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 46% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak3players, 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
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 06:01 UTC10d ago
3
–
running
1
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
ZMADHOUSE PVE leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 95.216.228.189:7781.
How reliable is ZMADHOUSE PVE, and is it up?
You can join now: ZMADHOUSE PVE is online. According to its reported uptime, the last restart was about 7 days ago. It was up 85% of the time over the last 7 full days, 143 of 168 hours. The first sighting by Rust Server Score was on 13 October 2026.
How well does ZMADHOUSE PVE run?
The average over the last 48 hours was 112 server fps, and it never went below 90. At its peak, it held 76,405 entities, including buildings, deployables and all else in the world. Up to 5,313 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does ZMADHOUSE PVE sit?
You will find ZMADHOUSE PVE on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does ZMADHOUSE PVE wipe, and how often?
The record holds too few of ZMADHOUSE PVE's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 10 days 18 hours have passed since this world was made.
What should you expect from wipe day on ZMADHOUSE PVE?
The average peak on its recent wipes was 3 players. Peak numbers came 0 hours into the latest wipe.
Population
Where does ZMADHOUSE PVE place in the wider field of Rust servers?
In the top 46% of all ranked servers, ZMADHOUSE PVE sits at #10,306 for player hours over the last seven days.
How many players does ZMADHOUSE PVE usually have?
With 70 slots available, ZMADHOUSE PVE currently has 0 players. The seven-day average is 0 players, with a peak of 1. The busiest time in the last 48 hours was 06:00 UTC, with an average of 0 players.
Tags and filters
What is meant by the tags on ZMADHOUSE PVE?
The game's browser takes its cue from the tags ZMADHOUSE PVE has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp70 (Max players): 70 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Which Rust Server Score filters and lists feature ZMADHOUSE PVE?
Rust Server Score lists that include ZMADHOUSE PVE: Modded Rust servers, graded. It shows under the following filters 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.
Rules and settings
Which rules does ZMADHOUSE PVE enforce, and what are its settings?
The name of ZMADHOUSE PVE gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on ZMADHOUSE PVE?
A procedural map of size 3,500 and seed 2147483647, generated by the game, is what ZMADHOUSE PVE runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to ZMADHOUSE PVE?
To connect, start Rust, press F1, and type client.connect 95.216.228.189:7781. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://www.gameserverapp.com.
Server tags
what each one means
Published asmp70,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp70
Max players70 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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).