Station XX-4327 · recording
[RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits
Online 217.114.180.19:28015 checked 10m ago
- Players now
- 1/ 200
- 0% full
- Motion · 24 h
- M0.0▲rising
- +1 players on the day
- 7-day average
- 0
- peak 4
- Rank
- #4,327
- top 19%
- Last wipe
- 14d ago
- biweekly schedule
- Next wipe
- 6d 11h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 200 slots
- Motion · 24 h
- M0.0▲rising+1 players
- Sharpest hour
- +2into Wed 10:00 UTC
- Peak · 48 h
- 4most players in any hour
Players
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 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 11h. The force wipe · high confidence
- usual gap
- 13.9 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 4players, last three wipes
- crowd held
- 0%else halves by day 3.5
Coming wipes
- 6d 11hThu 5 Nov, 19:00 UTCFW
- 13d 11hThu 12 Nov, 19:08 UTC
- 27d 11hThu 26 Nov, 19:08 UTC
- 34d 11hThu 3 Dec, 19:00 UTCFW
- 41d 11hThu 10 Dec, 19:08 UTC
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 19:08 UTC14d ago | M0.6▲rising | 4 | – | running | 0 | |
| Thu 1 Oct, 19:10 UTC FW28d ago | M0.5▲rising | 3 | halved by day 6 | 14 days | 0 | |
| Fri 18 Sep, 02:16 UTC42d ago | M0.6▲rising | 4 | halved by day 1 | 13.7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
[RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits runs a procedural map of size 4,900 with seed 1739618184, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
2x gather is what [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits runs, judging by its name. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. By its own description it is vanilla: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
1 of the 200 slots on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits are filled right now. Across seven days this server recorded an average of 0 players and a peak of 4. The busiest point in the last 48 hours came at 16:00 UTC, averaging 3 players.
How does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits rank against other Rust servers?
The last seven days of player hours place [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits at #4,327, in the top 19% of all ranked servers.
Operator and location
How reliably does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits stay online?
As recorded now, [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits is running. The uptime it reports puts its last restart about 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits hold a steady tick rate?
The 48-hour average is 200 server fps; 169 is the lowest observed. At its highest, it carried 154,485 entities: buildings, deployables and the world's other contents. It reached a ceiling of 5,064 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits hosted?
The name of [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits points to Europe, even though it publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 217.114.180.19:28015.
What build of Rust does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits use?
On Linux, [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
4 players, on average, was the busiest crowd at its recent wipes. 47 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 3.5 in the wipes where it didn't hold.
How often does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits wipe, and on which days?
The prediction is taken from its tag, since [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits has too few wipes on record to confirm the schedule. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 14 days 12 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Lists and tags
What do the server tags on [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits mean?
Tags published by [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): It wipes once a fortnight; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits appear?
The Rust Server Trends lists that take in [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits are: 2x Rust servers, listed live, EU Rust servers and Modded Rust servers, tracked live. You will find it under these filters 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.
Connecting
How do you connect to [RU] #1 HMAORUST|Classic +|Stack x2|Events| Team no limits?
To join, enter client.connect 217.114.180.19:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.