Online 157.85.93.245:28683 checked 12m ago
$MONZ$
Connect
srv = rust.server("157.85.93.245:28684")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 45% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 16:04 UTC6d ago | 1 | 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
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 132/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 117/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 33/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 33/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does $MONZ$ rank?
Rank #9,855 on seven-day player hours for $MONZ$, within the top 45% of all ranked servers.
How many players does $MONZ$ hold at once?
$MONZ$ reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How well does $MONZ$ perform?
The 48-hour average is 171 server fps, with a low of 114. The entity count peaked at 48,686, covering buildings, deployables and the rest of the world. The memory field tops out at 5,411 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on $MONZ$?
The build is Rust network protocol 2635 and build 167781 on Linux, run by $MONZ$. Joining needs the same protocol on your game; Steam handles the update.
How reliable is $MONZ$, and is it up?
$MONZ$ reports itself online at the current refresh. A restart about 20 hours ago is what its reported uptime implies. Uptime of 100% across the last 5 full days: 120 hours of 120. The first row Rust Data holds for it is dated 22 October 2026.
In which location is $MONZ$ hosted?
No region is published by $MONZ$. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.93.245:28683 is its address.
Rules, settings, map
Which rules apply on $MONZ$, and what settings?
No gather rate appears in the name: $MONZ$. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has $MONZ$ selected?
The game generates the map on $MONZ$: procedural, size 3,000, seed 50000. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does $MONZ$ wipe, and on what schedule?
The record for $MONZ$ holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 6 days 4 hours ago.
What is wipe day on $MONZ$ like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which Rust Data filters and lists contain $MONZ$?
On Rust Data, $MONZ$ appears in these lists: 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 week.
How should you read the server tags on $MONZ$?
These tags are published by $MONZ$ and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into $MONZ$?
In Rust, F1 opens the console: type client.connect 157.85.93.245:28683. Launch Rust on this page does the same by opening the game through Steam and connecting.