Rust StatisticsWorking papers on every public Rust server · 41,758 players now

ZMADHOUSE PVE

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 8m ago · 95.216.228.189:7781

Abstract

We describe the public Rust server ZMADHOUSE PVE, reached at 95.216.228.189:7781. At the last check it held 0 of 70 places, against a seven-day mean of 0 and a peak of 11. It ranks #10,801 of all servers, the top 49%. It last wiped 10d ago.

Keywordsmodded oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.
Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/700% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#10,801top 49%
Last wipe10d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75105:0014:0000:0008:0017:0002:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020005:0014:0000:0008:0017:0002:00
Figure 2: 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.

4Rank

The server stands in the top 49% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k13 Oct16 Oct20 Oct23 Oct27 Oct30 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak3players, last three wipes
01234+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 19 Oct, 06:0110d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of ZMADHOUSE PVE
Figure 5: The map: Procedural Map, size 3500, seed 2147483647. Open on RustMaps.
Table 4: The server's published settings.
Address95.216.228.189:7781
Region–
Max players70
Group limit8, the default
Wipe schedule–
Last wipe19 Oct 2026, 06:01 UTC
Hostname–
First seen13 Oct 2026
MapProcedural Map
Size3500
Seed2147483647

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average21/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average48/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average5/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average25/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average83/200

Appendix AQuick answers

From the figures on this page.

About the server

A.1How well does ZMADHOUSE PVE run?

Its average server fps over the last 48 hours was 110, with a minimum of 90. Its entity count reached a maximum of 76,405, including buildings, deployables and all other world objects. Its highest memory usage was 5,581 MB. Players experience lag when fps is low and the entity count is rising.

A.2What location does ZMADHOUSE PVE have?

A region is not published by ZMADHOUSE PVE. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 95.216.228.189:7781 is its address.

A.3What is the online status and reliability of ZMADHOUSE PVE?

ZMADHOUSE PVE is currently online. It last restarted around 7 days 4 hours ago, according to its reported uptime. Its uptime over the last full days (7 days) was 99%, with 167 of 168 hours online. Its first appearance in Rust Statistics's records is 13 October 2026.

A.4What version of Rust is run on ZMADHOUSE PVE?

ZMADHOUSE PVE is running Rust network protocol 2635 and build 168909 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5On what cycle does ZMADHOUSE PVE wipe?

There are not yet enough recorded wipes for ZMADHOUSE PVE to reveal its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 10 days 22 hours.

A.6What happens on ZMADHOUSE PVE when wipe day arrives?

The average busiest point of recent wipes was 3 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7What is the rank of ZMADHOUSE PVE among Rust servers?

Ranked by player hours across seven days, ZMADHOUSE PVE holds #10,801, in the top 49% of all ranked servers.

A.8How would you characterise the player activity on ZMADHOUSE PVE?

The current population of ZMADHOUSE PVE is 0, drawn from 70 slots. Averaged over the last seven days: 0 players; the same period peaks at 1. Averaging 0 players, 06:00 UTC was the busiest hour of the past 48.

Tags and filters

A.9How should the tags on ZMADHOUSE PVE be interpreted?

Tags from ZMADHOUSE PVE, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp70 (Max players): 70 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can ZMADHOUSE PVE be found among the Rust Statistics lists and filters?

The Rust Statistics lists that ZMADHOUSE PVE fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.11What are the settings and rules that govern ZMADHOUSE PVE?

The name of ZMADHOUSE PVE states no gather rate. At 8 players, the group limit equals the game's default. survival is the game mode here; the standard mode, in which you gather, build and raid. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.12What is the map for ZMADHOUSE PVE?

Generated by the game from seed 2147483647, the procedural map on ZMADHOUSE PVE measures 3,500. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

How to join

A.13How do you connect to ZMADHOUSE PVE?

Press F1 inside Rust to open the console and enter client.connect 95.216.228.189:7781. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. Its website can be found at https://www.gameserverapp.com.

Appendix BServer tags

What each of the server's tags means. Published as mp70,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp70Max players. 70 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.