Offline 84.32.176.18:28015 checked 11d ago
HMAOCLASSIC
Connect
srv = rust.server("84.32.176.18: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 62% 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
- 84.32.176.18:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 18:11 UTC
- hostname
- –
- first seen
- 16 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 · 159 on average | 46/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 9/1000 |
Quick answers
From the figures on this page.
Population data
What position does HMAOCLASSIC take in the server rankings?
Rank #13,441 on seven-day player hours for HMAOCLASSIC, within the top 62% of all ranked servers.
How full does HMAOCLASSIC run?
The current row shows HMAOCLASSIC offline; the last response was 11 days 11 hours ago.
Server data
What Rust version does HMAOCLASSIC run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by HMAOCLASSIC. Joining needs the same protocol on your game; Steam handles the update.
Is HMAOCLASSIC up, and what does its uptime show?
The latest sample has HMAOCLASSIC offline, with a last sighting 11 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 16 October 2026.
Which location does HMAOCLASSIC run from?
No region is published by HMAOCLASSIC. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 84.32.176.18:28015 is its address.
Rules, settings, map
What rules and settings are recorded for HMAOCLASSIC?
No gather rate appears in the name: HMAOCLASSIC. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has HMAOCLASSIC loaded?
The game generates its map: procedural, on HMAOCLASSIC.
Wipes and dates
On what schedule does HMAOCLASSIC wipe?
The record for HMAOCLASSIC 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 11 days 10 hours ago.
Lists and tags
Which lists on Rust Data hold HMAOCLASSIC, and which filters?
These Rust Data lists include HMAOCLASSIC: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on HMAOCLASSIC hold?
These tags are published by HMAOCLASSIC and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
How can I connect to HMAOCLASSIC?
In Rust, F1 opens the console: type client.connect 84.32.176.18:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.