[RU] #2 HMAORUST|HARDCORE
Online 217.114.180.19:28025 checked 11m ago
Server instruments
last reading Thu 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 174 · below 20 is lag, below 10 is badEntities
48 h range 95,406–115,322 · memory 3,301 MBUptime
18 h 2 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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, measured since 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 39% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Wednesday 4 November, 09:20 UTC, in 5d 13h. Its biweekly schedule tag · low confidence
Coming wipes
- WPT 1Wed 4 Nov, 09:20 UTC5d 13h
- WPT 2Thu 5 Nov, 19:00 UTC6d 23hFW
- WPT 3Wed 18 Nov, 09:20 UTC19d 13h
- WPT 4Wed 2 Dec, 09:20 UTC33d 13h
- WPT 5Thu 3 Dec, 19:00 UTC34d 23hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 09:20 UTC8d ago | 1 | – | running | 0 |
| Thu 15 Oct, 19:06 UTC14d ago | 1 | halved by day 2 | 5.6 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 7/200
- 12/200
- 24/50
- 10/200
- 3/300
- 0/50
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on [RU] #2 HMAORUST|HARDCORE?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 2 it fell below half.
When does [RU] #2 HMAORUST|HARDCORE wipe?
Its tag guides the prediction: too few of [RU] #2 HMAORUST|HARDCORE's wipes are on record to confirm its schedule. On Wednesday 4 November at 09:20 UTC its next wipe is due. 8 days 6 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.
Tag meanings
Which tags does [RU] #2 HMAORUST|HARDCORE carry, and what do they mean?
Check: tags. The game's server browser reads gmhardcore (Game mode): Hardcore ruleset, the harsher one; mp150 (Max players): 150 slots in total; ts0 (Group limit): Team play is disabled; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^h (Hardcore): Hardcore mode, as Facepunch defines it: less help, tougher survival; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game from [RU] #2 HMAORUST|HARDCORE. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show [RU] #2 HMAORUST|HARDCORE?
On Rust Metrics, [RU] #2 HMAORUST|HARDCORE sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Europe; Type: Modded; Game mode: Hardcore; Server tag: Biweekly ^b, Hardcore ^h, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Player count
Where does [RU] #2 HMAORUST|HARDCORE sit in the rankings?
Player hours over seven days put [RU] #2 HMAORUST|HARDCORE at #8,672, in the top 39% of all ranked servers.
What player count does [RU] #2 HMAORUST|HARDCORE carry?
0 of 150 slots are filled on [RU] #2 HMAORUST|HARDCORE right now. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 0 players, at 05:00 UTC over the last 48 hours.
Server
Which location does [RU] #2 HMAORUST|HARDCORE run from?
Reading: location. Nothing in the tags, but the name of [RU] #2 HMAORUST|HARDCORE points to Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 217.114.180.19:28025.
What Rust version is [RU] #2 HMAORUST|HARDCORE on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by [RU] #2 HMAORUST|HARDCORE. Matching protocol is required to join. Let Steam update your game.
How does [RU] #2 HMAORUST|HARDCORE perform?
Check: fps. Average 222 server fps over the last 48 hours, low of 174. Within range. Peak entity count: 115,322. Buildings, deployables and all else included. Reading: 3,863 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is [RU] #2 HMAORUST|HARDCORE, and is it online now?
Check: connection. [RU] #2 HMAORUST|HARDCORE is online at this moment. By its reported uptime, the last restart was roughly 18 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 4 October 2026.
Rules and settings
What rules does [RU] #2 HMAORUST|HARDCORE enforce, and what are its settings?
No gather rate appears in the name: [RU] #2 HMAORUST|HARDCORE. The group limit is not published. Mode check gives hardcore; Facepunch's most punishing mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
Which map is live on [RU] #2 HMAORUST|HARDCORE?
Check: map. Procedural, size 4,500, generated by the game, on [RU] #2 HMAORUST|HARDCORE.
How to join
How do you connect to [RU] #2 HMAORUST|HARDCORE?
Press F1 in Rust and enter client.connect 217.114.180.19:28025. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.