Rust Data

rustdata.spaceservers95.216.228.189:27017.ipynb

Run all rust-data · live

‹ All servers

Online 95.216.228.189:7781 checked 8m ago

ZMADHOUSE PVE

moddedoxide

Connect

srv = rust.server("95.216.228.189:27017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/70 # 0% full
7-day average 0 # peak 1
rank #10,776 # top 48%
last wipe 10d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75103:0012:0022:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020003:0012:0022:0006:0015:0000:00

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k13 Oct16 Oct20 Oct23 Oct27 Oct30 Oct

Top 48% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 19 Oct, 06:01 UTC10d ago 3 NaN 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.

display(srv.map, srv.info())

Map

3500 · seed 2147483647
Map of ZMADHOUSE PVE
map
Procedural Map
size
3500
seed
2147483647
Open on RustMaps

Server

srv.info()
address
95.216.228.189:7781
region
–
max players
70
group limit
8, the default
wipe schedule
–
last wipe
19 Oct 2026, 06:01 UTC
hostname
–
first seen
13 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average13/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average35/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average7/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average35/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average128/200

Quick answers

From the figures on this page.

Player counts

What position does ZMADHOUSE PVE take in the server rankings?

Player hours over seven days put ZMADHOUSE PVE at #10,776, in the top 48% of the ranked set.

How many players does ZMADHOUSE PVE hold at once?

ZMADHOUSE PVE reports 0 players at this refresh, with 70 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 06:00 UTC, mean 0 players.

About the server

What does performance look like on ZMADHOUSE PVE?

The 48-hour average is 111 server fps, with a low of 90. Buildings, deployables and all else in the world took the count as high as 76,405 entities. A high of 5,565 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on ZMADHOUSE PVE?

Version Rust network protocol 2635 and build 168909 on Windows is reported by ZMADHOUSE PVE. Joining needs the same protocol on your game; Steam handles the update.

Is ZMADHOUSE PVE up, and what does its uptime show?

Online is the state at the latest refresh for ZMADHOUSE PVE. Count back 7 days 2 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 October 2026.

In which location is ZMADHOUSE PVE hosted?

For ZMADHOUSE PVE, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 95.216.228.189:7781 is its address.

Rules, settings, map

Which rules apply on ZMADHOUSE PVE, and what settings?

You will not find a gather rate in the string ZMADHOUSE PVE. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has ZMADHOUSE PVE selected?

Size 3,500, seed 2147483647: the procedural map on ZMADHOUSE PVE, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does ZMADHOUSE PVE wipe, and how often?

The record for ZMADHOUSE PVE holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 20 hours ago.

On ZMADHOUSE PVE, what happens on wipe day?

Recent wipes averaged 3 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Where does ZMADHOUSE PVE appear among Rust Data lists and filters?

These Rust Data lists include ZMADHOUSE PVE: Modded Rust servers. 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.

How should you read the server tags on ZMADHOUSE PVE?

Read by the game's server browser, the tags ZMADHOUSE PVE publishes are: gmrust (Game mode): Survival play, standard Rust; mp70 (Max players): The server lists 70 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join ZMADHOUSE PVE?

In Rust, F1 opens the console: type client.connect 95.216.228.189:7781. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://www.gameserverapp.com.

Server tags · what each one means

srv.tags.decode()

Published as mp70,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp70
Max players The server lists 70 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 51,221 players 11,693 servers online