StatusLive Servers online11,856 Players101,030 Populated3,903 Wiped · 3 h542 Interval5 min Date29 OCT 2026

DWG RG-S4321Server sheetchecked 10m ago

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits

Online 217.114.180.19:28015 checked 10m ago

2x biweekly wipes vanillamoddedoxide
Connect
Players now 1/ 200 0% full
7-day average0peak 4
Rank#4,321top 19%
Last wipe14d agobiweekly schedule
Next wipe6d 22hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0123421:0006:0015:0000:0009:0018:00

Hourly average and peak, UTC.

Fig. 1Players on [RU] #1 HMAORUST|Classic +|Rate x2|Events|...
Fig. 2

Server performance

010020030040021:0006:0015:0000:0009:0018:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 19% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. The force wipe · high confidence

usual gap13.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 3.5

Coming wipes

  1. 6d 22hThu 5 Nov, 19:00 UTCFW
  2. 13d 22hThu 12 Nov, 19:08 UTC
  3. 27d 22hThu 26 Nov, 19:08 UTC
  4. 34d 22hThu 3 Dec, 19:00 UTCFW
  5. 41d 22hThu 10 Dec, 19:08 UTC

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctFri 18 Sep
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 4, 47 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Atlas - EU 2X Medium | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · biweekly · 140 on average
1449 / 1550
02
ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10EU · groups of 10+ · 2x · biweekly · 52 on average
19 / 200
03
PROSTOJ #6 | Ресурсы x2 | Компоненты x1EU · groups of 8+ · 2x · biweekly · 50 on average
4 / 200
04
РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2xEU · groups of 300+ · 2x · biweekly · 45 on average
450 / 550
05
Magic Rust #22 — Vanilla 2x (Biweekly) | PyccкийEU · groups of 150+ · 2x · biweekly · 35 on average
11 / 200
06
Россия | Классика X2 | IMBA RUST 23.10EU · groups of 100+ · 2x · biweekly · 30 on average
11 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

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 is up at this moment. About 18 hours ago is when it last restarted, measured from the uptime it reports. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

Is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits stable in the figures recorded?

Average server fps over the last 48 hours is 200; the lowest was 169. Counted at its highest: 154,485 entities, buildings, deployables and the rest of the world included. 4,824 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

Its name points to Europe, though [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits publishes no region tag. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 217.114.180.19:28015 is its address.

On which Rust version is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits running?

On Linux, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Counts

What does the population history show for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

At the last refresh, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits recorded 1 players across 200 slots. Averaged across seven days, the player count is 0, with a peak of 4. The 48-hour peak falls at 16:00 UTC, averaging 3 players.

Against other Rust servers, where is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits placed?

Over the last seven days, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits records #4,321 for player hours: the top 19% of all ranked servers.

Wipe times

On [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, what does the data show for wipe day?

An average of 4 players was recorded at the busiest point of its recent wipes. 47 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. On the wipes where it did not hold, the crowd dropped below half by day 3.5.

What wipe schedule has been recorded for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

Too few of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. 14 days 1 hours ago the current world was made. Its tags give a wipe schedule of one wipe every two weeks.

Rules and settings

What settings and rules apply on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

2x gather is stated in the name of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Oxide. Vanilla is the label it uses: no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.

On which map is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits played?

Size 4,900 with seed 1739618184: that is the procedural map [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Filters

Where does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits are: Servers with a 2x gather rate, Europe servers, plotted and Modded Rust servers. On the server list, these filters bring it up: 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.

On [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, what is meant by each tag?

Tags published by [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, and read by the game's server browser: gmvanilla (Game mode): Survival, vanilla style; mp200 (Max players): The slot count is 200; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

By what method do you join [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

In Rust, press F1 and type client.connect 217.114.180.19:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^b,^v,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival, vanilla style.
mp200
Max players The slot count is 200.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

KeyTag string decoded