Offline 180.148.98.73:28015 checked 32d ago
My Solo PvE Mega World
Connect
srv = rust.server("180.148.98.73:28016")
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 best
Top 61% 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 | Fri 25 Sep, 23:25 UTC33d ago | 1 | NaN | running | 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
- 180.148.98.73:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Sep 2026, 23:25 UTC
- hostname
- –
- first seen
- 25 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 248 on average | 315/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 239 on average | 159/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 103 on average | 154/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 60 on average | 8/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 65/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 18/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does My Solo PvE Mega World rank?
Player hours over seven days put My Solo PvE Mega World at #14,165, in the top 61% of the ranked set.
How many players does My Solo PvE Mega World hold at once?
Offline now for My Solo PvE Mega World, with the last sample 32 days 20 hours ago.
Server facts
Which Rust version is My Solo PvE Mega World on?
Version Rust network protocol 2633 and build 165217 on Windows is reported by My Solo PvE Mega World. Steam updates your game for you, but the protocol must match to join.
How reliable is My Solo PvE Mega World, and is it online now?
My Solo PvE Mega World is offline at this refresh; the last response came 32 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 25 September 2026.
Which location does My Solo PvE Mega World run from?
For My Solo PvE Mega World, 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. 180.148.98.73:28015 is its address.
Map and rules
Which rules apply on My Solo PvE Mega World, and what settings?
You will not find a gather rate in the string My Solo PvE Mega World. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has My Solo PvE Mega World selected?
A procedural map runs on My Solo PvE Mega World, generated by the game.
Wipe data
On what schedule does My Solo PvE Mega World wipe?
A rhythm cannot be read from the wipes of My Solo PvE Mega World on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 33 days 1 hours ago, and that is the one in play.
What is wipe day on My Solo PvE Mega World like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold My Solo PvE Mega World, and which filters?
The Rust Data lists that My Solo PvE Mega World fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on My Solo PvE Mega World hold?
The game's server browser reads these tags from My Solo PvE Mega World: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to My Solo PvE Mega World?
The manual route: launch Rust, F1, then client.connect 180.148.98.73:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.