[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits
Online 217.114.180.19:28015 checked 13m ago
Server instruments
last reading Thu 13:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 169 · below 20 is lag, below 10 is badEntities
48 h range 151,718–154,485 · memory 4,124 MBUptime
13 h 55 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 19:08 UTC, in 4h. Its biweekly schedule tag · low confidence
Coming wipes
- WPT 1Thu 29 Oct, 19:08 UTC4h
- WPT 2Thu 5 Nov, 19:00 UTC7d 4hFW
- WPT 3Thu 12 Nov, 19:08 UTC14d 4h
- WPT 4Thu 26 Nov, 19:08 UTC28d 4h
- WPT 5Thu 3 Dec, 19:00 UTC35d 4hFW
- WPT 6Thu 10 Dec, 19:08 UTC42d 4h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 47 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 19:08 UTC13d ago | 4 | – | running | 0 |
| Thu 1 Oct, 19:10 UTC FW27d ago | 3 | halved by day 6 | 14 days | 0 |
| Fri 18 Sep, 02:16 UTC41d ago | 4 | halved by day 1 | 13.7 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- 53/100
- 29/200
- 13/200
- 18/200
- 14/200
- 548/700
Quick answers
from the figures on this pageWipe timing
What happens on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits when wipe day comes?
The busiest point of its recent wipes drew 4 players on average. Peak crowd on the latest wipe: 47 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 3.5 it fell below half when it didn't.
How often does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits wipe, and when?
Its tag guides the prediction: too few of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits's wipes are on record to confirm its schedule. Due on Thursday 29 October at 19:08 UTC is its next wipe. The world it runs now was made 13 days 19 hours ago. A wipe schedule of every two weeks is published in its tags.
Lists and filters
How should you read the tags on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
Tags published by [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): Slots: 200; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
These Rust Metrics lists carry [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits: 2x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Player count
What position does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits hold among Rust servers?
Player hours over seven days put [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits at #4,439, in the top 20% of all ranked servers.
How full does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits get?
1 of 200 slots are filled on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits right now. Seven-day check: 0 players on average. Peak reading: 3. Average at the busiest hour was 2 players, at 16:00 UTC over the last 48 hours.
Operator and location
Where does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits sit?
The name of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits points to Europe, though it publishes no region tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 217.114.180.19:28015.
What Rust version is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits within range?
Check: fps. Average 200 server fps over the last 48 hours, low of 169. Within range. Reading: 154,485 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,786 MB of memory at the highest. Expect lag when fps falls and entities climb.
How reliable is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, and is it online now?
[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 13 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits configured, and what rules are in force?
Gather rate check: 2x. That comes from the name [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. It describes itself as vanilla. The meaning given: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.
What map is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits on?
Check: map. Procedural, size 4,900, seed 1739618184, generated by the game on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
How can you get onto [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
Press F1 in Rust and enter client.connect 217.114.180.19:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.