Offline 178.176.113.92:28015 checked 28d ago
HMAOCLASSIC
Connect
srv = rust.server("178.176.113.92: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 66% 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
- 178.176.113.92:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 18:21 UTC
- hostname
- –
- first seen
- 29 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 · 163 on average | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 64/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 59/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 15/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does HMAOCLASSIC rank?
Rank #15,679 on seven-day player hours for HMAOCLASSIC, within the top 66% of all ranked servers.
How full does HMAOCLASSIC run?
Offline now for HMAOCLASSIC, with the last sample 28 days 5 hours ago.
Server data
Which Rust version is HMAOCLASSIC on?
The build is Rust network protocol 2633 and build 165217 on Windows, run by HMAOCLASSIC. Steam updates your game for you, but the protocol must match to join.
How reliable is HMAOCLASSIC, and is it online now?
Offline now for HMAOCLASSIC, last seen 28 days 5 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 29 September 2026.
Which location does HMAOCLASSIC run from?
No region is published by HMAOCLASSIC. Rust Data does not look up where the machine stands; it shows where a server says it is. 178.176.113.92:28015 is its address.
Settings and map
Which settings and rules does HMAOCLASSIC run?
You will not find a gather rate in the string HMAOCLASSIC. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on HMAOCLASSIC?
The game generates its map: procedural, on HMAOCLASSIC.
Wipe data
When does HMAOCLASSIC wipe, and how often?
Too few wipes are on record for HMAOCLASSIC to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 28 days 5 hours ago, and that is the one in play.
Tags and filters
Where does HMAOCLASSIC appear among Rust Data lists and filters?
The Rust Data lists that HMAOCLASSIC fits are: 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.
How should you read the server tags on HMAOCLASSIC?
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): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into HMAOCLASSIC?
In Rust, F1 opens the console: type client.connect 178.176.113.92:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.