Offline 31.173.100.148:28015 checked 10d ago
HMAOCLASSIC
Connect
srv = rust.server("31.173.100.148: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 bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 31.173.100.148:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 21:53 UTC
- hostname
- –
- first seen
- 18 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 | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does HMAOCLASSIC rank?
Player hours over seven days put HMAOCLASSIC at #12,981, in the top 59% of the ranked set.
What population does HMAOCLASSIC carry?
Offline now for HMAOCLASSIC, with the last sample 10 days ago.
Server data
What Rust version does HMAOCLASSIC run?
Rust network protocol 2634 and build 167781 on Windows is what HMAOCLASSIC runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is HMAOCLASSIC, and is it up?
HMAOCLASSIC is offline at this refresh; the last response came 10 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 18 October 2026.
Where does HMAOCLASSIC sit?
For HMAOCLASSIC, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 31.173.100.148:28015.
Rules, settings, map
Which rules apply on HMAOCLASSIC, and what settings?
You will not find a gather rate in the string HMAOCLASSIC. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has HMAOCLASSIC selected?
HMAOCLASSIC runs a procedural map, which the game generates.
Wipe schedule
When does HMAOCLASSIC wipe, and on what schedule?
The record for HMAOCLASSIC holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 21 hours ago.
Tags and filters
Which lists on Rust Data hold HMAOCLASSIC, and which filters?
The Rust Data lists that HMAOCLASSIC fits are: 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 2 weeks.
How should you read the server tags on HMAOCLASSIC?
The game's server browser reads these tags from HMAOCLASSIC: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Join steps
What is the way into HMAOCLASSIC?
The manual route: launch Rust, F1, then client.connect 31.173.100.148:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.