[RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits
Online 217.114.180.19:28015 checked 38m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 6d 17h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 13d 17h | Thu 12 Nov, 19:08 UTC | its own |
| 27d 17h | Thu 26 Nov, 19:08 UTC | its own |
| 34d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 41d 17h | Thu 10 Dec, 19:08 UTC | its own |
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 UTC14d ago | 4 | – | running | 0 |
| Thu 1 Oct, 19:10 UTC FW28d 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| Server | Profile | Players now |
|---|---|---|
| Atlas - EU 2X Medium | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · biweekly · 168 on average | 781 / 850 |
| РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2x | EU · groups of 300+ · 2x · biweekly · 55 on average | 146 / 250 |
| ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10 | EU · groups of 10+ · 2x · biweekly · 53 on average | 14 / 200 |
| PROSTOJ #6 | Ресурсы x2 | Компоненты x1 | EU · groups of 8+ · 2x · biweekly · 50 on average | 2 / 200 |
| Magic Rust #22 — Vanilla 2x (Biweekly) | Pyccкий | EU · groups of 150+ · 2x · biweekly · 34 on average | 3 / 200 |
| Россия | Классика X2 | IMBA RUST 23.10 | EU · groups of 100+ · 2x · biweekly · 30 on average | 1 / 200 |
Quick answers
from the figures on this pageWipe data
When does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits wipe?
Its tag guides the prediction, since [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits has too few wipes on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world dates from 14 days 6 hours. Its tags publish a wipe schedule of every two weeks.
Wipe day on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits: what should you expect?
The average busiest count over recent wipes is 4 players. Peak population for the latest wipe came 47 hours after it began. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. By day 3.5 it had fallen below half where the hold failed.
Server details
Which location hosts [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
No region tag is published by [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits, but the name points to Europe. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 217.114.180.19:28015.
What Rust build does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits run?
On Linux, [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.
Is [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits up, and how steady is its uptime?
As of the latest refresh, [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits is online. About 22 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 99%, or 167 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
Is performance on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits stable?
The 48-hour average was 199 server fps; the low was 169. Buildings, deployables and all other world objects brought the entity total to 154,485. Peak memory was 5,064 MB. A climbing entity count and low fps are the lag players perceive.
Lists and tags
What do [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits's tags stand for?
Tags from [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits, as read by the game's server browser, are: gmvanilla (Game mode): Vanilla ruleset survival; mp200 (Max players): Player slots: 200; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): Nothing altered from Facepunch's release: rates, kits and rules are stock; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits fits are: Rust servers with a 2x gather rate, EU Rust servers: live population data and Modded Rust servers: live data. These filters bring it up on the server list: 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; Gather rate: 2x.
Population
Against other Rust servers, how does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits compare?
Player hours for the last seven days place [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits at #4,264, in the top 19% of the ranked field.
How many players does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits carry?
Of 200 slots, 0 are filled on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits at this refresh. Seven-day figures: an average of 0 players and a peak of 4. Across the last 48 hours, 16:00 UTC shows the highest average: 3 players.
Settings
How is [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits configured, and what rules apply?
[RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits names a 2x gather rate. The default group cap of 8 players applies. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. Its self-description is vanilla: nothing altered from Facepunch's release: rates, kits and rules are stock. Anti-cheat status: VAC on.
The map on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits: which one is it?
A procedural map of size 4,900 with seed 1739618184, generated by the game, runs on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits. Because size and seed determine the map, it can be viewed on RustMaps via this page.
How to join
How can a player join [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
In the Rust console (F1), enter client.connect 217.114.180.19:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.