Offline 217.87.231.46:28015 checked 22d ago
MoonRust [261 Devblog]
Connect
srv = rust.server("217.87.231.46:28015")
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. 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 10:37 UTC24d ago | 0 | NaN | running | 0 |
| 1 | Fri 2 Oct, 15:39 UTC25d ago | 0 | NaN | 0.8 days | 0 |
| 2 | Fri 2 Oct, 07:07 UTC25d ago | 0 | NaN | 0.4 days | 0 |
| 3 | Thu 1 Oct, 06:34 UTC26d ago | 0 | NaN | 1 days | 0 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.87.231.46:28015
- region
- –
- max players
- 25
- group limit
- not published
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:36 UTC
- hostname
- –
- first seen
- 30 Sep 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 · 160 on average | 39/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 17/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 7/1000 |
Quick answers
From the figures on this page.
Population data
How does MoonRust [261 Devblog] compare in the rankings?
Player hours over seven days put MoonRust [261 Devblog] at #15,962, in the top 71% of the ranked set.
How full does MoonRust [261 Devblog] run?
MoonRust [261 Devblog] returns no live count at this refresh, having last been seen 22 days 12 hours ago.
About the server
What Rust version does MoonRust [261 Devblog] run?
Version Rust network protocol 2332 on Windows is reported by MoonRust [261 Devblog]. Joining needs the same protocol on your game; Steam handles the update.
How reliable is MoonRust [261 Devblog], and is it up?
The latest sample has MoonRust [261 Devblog] offline, with a last sighting 22 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 30 September 2026.
Which location does MoonRust [261 Devblog] run from?
For MoonRust [261 Devblog], 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. 217.87.231.46:28015 is its address.
Map and rules
What rules and settings are recorded for MoonRust [261 Devblog]?
No gather rate appears in the name: MoonRust [261 Devblog]. Group limits do not appear in its data. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. VAC, Valve's anti-cheat, is enabled.
Which map has MoonRust [261 Devblog] selected?
A procedural map runs on MoonRust [261 Devblog], generated by the game.
Wipe data
When does MoonRust [261 Devblog] wipe, and how often?
MoonRust [261 Devblog] wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 24 days 15 hours ago.
What is wipe day on MoonRust [261 Devblog] like?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does MoonRust [261 Devblog] appear among Rust Data lists and filters?
The Rust Data lists that MoonRust [261 Devblog] fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded.
How should you read the server tags on MoonRust [261 Devblog]?
Read by the game's server browser, the tags MoonRust [261 Devblog] publishes are: gmrust (Game mode): Survival play, standard Rust; mp25 (Max players): Slot count: 25; v2332 (Protocol): To join, your game must run protocol 2332; ptrak (Networking): Network traffic runs over RakNet, the game standard; oxide (Oxide): Runs on Oxide (uMod) for plugins; modded (Modded): The Modded section lists it, because plugins or settings change the game; h955eb6e7 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; stok (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into MoonRust [261 Devblog]?
The manual route: launch Rust, F1, then client.connect 217.87.231.46:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.