Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 104,075 players on 11,902 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOnline

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

217.114.180.19:28015 checked 10m ago

2x biweekly wipes vanillamoddedoxide
Release date
Next release
In five minutes (18:45 UTC)
Source
Live server queries
Server address
217.114.180.19:28015
First recorded
13 September 2026

Connect to this server

Launch Rust and join

1. Main points

Players now

1/ 200

0% full

7-day average

0

peak 4

Rank

#4,360

top 20%

Last wipe

13d ago

biweekly schedule

Next wipe

17m

Thu 29 Oct, 19:08 UTC

Main points

  • There were 1 players on it, 0% of its 200 slots.
  • Over the last seven days it averaged 0 players, with a peak of 4.
  • It ranks #4,360 of all ranked servers, the top 20%, on player hours over the last seven days.
  • Its current map went up 13d ago; the next wipe is expected Thursday 29 October, 19:08 UTC, its biweekly schedule tag.

2. Players

Figure 1: Players on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits

Players now and over time, UTC

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

010020030040019:0004:0013:0023:0008:0017:00

Note

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.

4. Rank

Figure 3: Rank among all servers, daily

1 is best

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Source: Live server queries, Rust Census

5. Wipe schedule

Patternfrom its schedule tag

Next wipe Thursday 29 October, 19:08 UTC, in 17m. Its biweekly schedule tag · low confidence

Usual gap

13.9 days

between real wipes

On rhythm

100%

of its recent wipes

Wipe-day peak

4

players, last three wipes

Crowd held

0%

else halves by day 3.5

Table 1: Coming wipes

Expected from its own rhythm and the force wipe

InDate and timeKind
17mThu 29 Oct, 19:08 UTCOwn schedule
7d 0hThu 5 Nov, 19:00 UTCForce wipe FW
14d 0hThu 12 Nov, 19:08 UTCOwn schedule
28d 0hThu 26 Nov, 19:08 UTCOwn schedule
35d 0hThu 3 Dec, 19:00 UTCForce wipe FW
42d 0hThu 10 Dec, 19:08 UTCOwn schedule

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

Thu 15 OctThu 1 OctFri 18 Sep
01234+0h+9h+19h+28h+38h+47h

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

Source: Live server queries, Rust Census

6. Wipes

Table 2: Wipes, newest first

Every wipe seen on this server

WipedPeakCrowdLastedPlayers 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

Notes

  1. 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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits

4900 · seed 1739618184

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

Table 3: The world

As the server publishes it

MapProcedural Map
Size4900
Seed1739618184
Open on RustMaps

8. Server characteristics

Table 4: Characteristics of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits

What the server publishes and what was recorded

Address217.114.180.19:28015
Region–
Max players200
Group limit8, the default
Wipe schedulebiweekly
Last wipe15 Oct 2026, 19:08 UTC
Hostname–
First seen13 Sep 2026

9. About this server

In its own words: the description the server publishes, unedited.

Сервер HMAORUST|Classic +. Размер карты на данный вайп 4900. Вайп краты каждые две недели в пятницу в 00:00. Глобал вайп каждый первый четверг месяца Читеры, хакеры, софтеры, багоюзеры будут улетать в бан пожизненно. Токсики отлетают на месяц. Увеличен световой день: 75 - минут, ночь - 3 минуты.Содержание дома 75%.

10. Similar servers

Table 5: Servers like this one

The same kind of game, then region, group limit, rate and wipes

ServerCharacteristicsPlayers
Atlas - EU 2X Medium | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · biweekly · 131 on average1573 / 1650
ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10EU · groups of 10+ · 2x · biweekly · 52 on average33 / 200
PROSTOJ #6 | Ресурсы x2 | Компоненты x1EU · groups of 8+ · 2x · biweekly · 50 on average7 / 200
РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2xEU · groups of 300+ · 2x · biweekly · 39 on average520 / 600
Magic Rust #22 — Vanilla 2x (Biweekly) | PyccкийEU · groups of 150+ · 2x · biweekly · 36 on average14 / 200
Россия | Классика X2 | IMBA RUST 23.10EU · groups of 100+ · 2x · biweekly · 30 on average13 / 200

11. Quick answers

From the figures on this page.

Wipe details

When does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits wipe, and how often?

The prediction for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits follows its tag, since too few of its wipes are on record to confirm the schedule. On Thursday 29 October at 19:08 UTC the next wipe is expected. 13 days 23 hours have passed since this world was made. The tags list a fortnightly wipe schedule.

On [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, what happens on wipe day?

The average busiest point of its recent wipes drew 4 players. The peak of the latest wipe's crowd came 47 hours after it began. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases, half the peak was lost by day 3.5.

About the server

What does the record show for the uptime and current status of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is online at the time of this release. About 17 hours ago is when it last restarted, according to the uptime it reports. Of the 168 hours in the last 7 full days, it was up 167 of them, or 99%. It was first seen by Rust Census on 13 September 2026.

What does the performance record of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits show?

Over the last 48 hours, server fps averaged 200; the lowest reading was 169. Buildings, deployables and everything else in the world took the entity count to 154,485. Memory use reached 4,824 MB at its peak. What players experience as lag is low fps combined with a climbing entity count.

Which location does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits run from?

Pointing to Europe is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits's name, though no region tag is published. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 217.114.180.19:28015 is its address.

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

The version in use on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is Rust network protocol 2635 and build 168909 on Linux. To join, your game has to be on the same protocol; Steam handles the update.

Population

What are the current player figures for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits stands at 1 players from 200 slots in this release. Averaged over seven days: 0 players, with a peak of 4. The busiest hour in the last 48 hours was 16:00 UTC, with an average of 3 players.

In the rankings of Rust servers, where is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits placed?

The rank for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is #4,360 on seven-day player hours, in the top 20% of ranked servers.

Lists and tags

On Rust Census, which lists and filters carry [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

The Rust Census lists that [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits fits are: Rust 2x servers, counted, EU Rust servers: the regional count and Modded Rust servers, counted. Under these filters it comes 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; Last wipe: In the last 2 weeks; Gather rate: 2x.

The tags on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits: what do they indicate?

Read by the game's server browser, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits publishes these tags: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe interval is two weeks; ^v (Vanilla): This is the unmodified game: rates, kits and rules as Facepunch ships them; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.

Settings and map

Which map is in use on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs a procedural map of size 4,900 with seed 1739618184, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.

How is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits configured, and what rules does it keep?

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits carries a 2x gather rate, as stated in its name. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Plugins or settings change the game, and the browser lists it under Modded. Oxide plugins are recorded on it. Its own label is vanilla: this is the unmodified game: rates, kits and rules as Facepunch ships them. Anti-cheat is active: VAC, Valve's system, is on.

Connecting

What is the way to join [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

You can open the console in Rust with F1 and enter client.connect 217.114.180.19:28015; or press Launch Rust and join on this page, and you are connected through Steam.

12. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmvanillaGame mode The mode is vanilla survival.
mp200Max players 200 slots are available.
ts8Group limit This is the game default: 8 to a team.
v2635Protocol Protocol 2635 is required; a different version cannot join.
cs168909Build Game build: 168909.
ptrakNetworking Networking is handled by RakNet, which the game uses by default.
$r?Region code A region code has not been set.

Wipe schedule

^bBiweekly The wipe interval is two weeks.

Difficulty

^vVanilla This is the unmodified game: rates, kits and rules as Facepunch ships them.

Mods and access

^oOxide Plugins are handled by Oxide (uMod) on this server.
^zModded Plugins or settings alter the game on this modded server.

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.