Statistical profileOnline
$MONZ$
157.85.93.245:28683 checked 13m ago
Connect to this server
1. Main points
Players now
0/ 40
0% full
7-day average
0
peak 1
Rank
#9,911
top 45%
Last wipe
5d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 0 players on it, 0% of its 40 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #9,911 of all ranked servers, the top 45%, on player hours over the last seven days.
- Its current map went up 5d ago.
2. Players
Figure 1: Players on $MONZ$
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 45% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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 peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 16:04 UTC5d ago | 1 | – | running | 1 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of $MONZ$
3000 · seed 50000
8. Server characteristics
Table 3: Characteristics of $MONZ$
What the server publishes and what was recorded
| Address | 157.85.93.245:28683 |
|---|---|
| Region | – |
| Max players | 40 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 22 Oct 2026, 16:04 UTC |
| Hostname | – |
| First seen | 22 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 155 on average | 174 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 185 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 134 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 16 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 54 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
When does $MONZ$ wipe, and how often?
The rhythm of $MONZ$'s wipes cannot yet be told: too few are on record. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. The present world dates from 5 days 19 hours.
What should you expect on wipe day at $MONZ$?
An average of 1 players attended at peak across recent wipes. 0 hours after the latest wipe, the crowd peaked.
About the server
How reliable is $MONZ$, and is it online now?
This release records $MONZ$ as online. The uptime it reports puts the last restart at about 14 hours ago. 120 of 120 hours on across the last 5 full days gives an uptime of 100%. First recorded by Rust Census on 22 October 2026.
Does $MONZ$ hold a steady frame rate and connection?
The figures for the last 48 hours give an average of 162 server fps and a minimum of 114. Buildings, deployables and everything else in the world took the entity count to 48,572. The peak memory use recorded was 5,411 MB. Lag, as players feel it, comes from low fps and a climbing entity count.
What location has been recorded for $MONZ$?
A region is not published by $MONZ$. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 157.85.93.245:28683 it is addressed.
What version of Rust has been recorded on $MONZ$?
The version in use on $MONZ$ is Rust network protocol 2635 and build 167781 on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
What are the current player figures for $MONZ$?
$MONZ$ stands at 0 players from 40 slots in this release. Averaged over seven days: 0 players, with a peak of 1.
How does $MONZ$ compare with other servers in the rankings?
For seven-day player hours, $MONZ$ is ranked #9,911, placing it in the top 45% of all ranked servers.
Tag details
Which Rust Census filters and lists cover $MONZ$?
These Rust Census lists include $MONZ$: Modded Rust servers, counted. 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 week.
What is meant by each tag shown on $MONZ$?
These are the tags $MONZ$ publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp40 (Max players): Slots: 40; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Your game must run protocol 2635 to join; cs167781 (Build): Build 167781 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game on this modded server. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Rules, map
What map is listed for $MONZ$?
The procedural map on $MONZ$ is generated by the game, measures 3,000 and carries seed 50000. The same size and seed produce the same map; RustMaps shows it from this page.
What settings and rules have been listed for $MONZ$?
No gather rate is recorded for $MONZ$ in its name. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Fighting other players and raiding are allowed. Plugins or settings change the game, and the browser lists it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Join details
How can you connect to $MONZ$?
Enter client.connect 157.85.93.245:28683 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp40,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp40 | Max players Slots: 40. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs167781 | Build Build 167781 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
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.