Rust Data LabData lab · live
Live readings Servers11,829 Players86,322 Populated3,682 Fresh wipes · 3h405 Sampled every 5 min

Element card · group Vanilla · atomic number 4,299, its rank

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

Online 217.114.180.19:28015 checked 10m ago

2x biweekly wipes vanillamoddedoxide
Join the experiment
Atomic mass · players now 0/ 200 0% full Room to join
7-day average0peak 4
Rank · atomic number#4,299top 19%
Last wipe14d agobiweekly schedule
Next wipe6d 21hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
010020030040022:0007:0016:0002:0011:0020: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.

Result 03

Rank

Result

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.

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. 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 21hThu 5 Nov, 19:00 UTCFW
  2. 13d 21hThu 12 Nov, 19:08 UTC
  3. 27d 21hThu 26 Nov, 19:08 UTC
  4. 34d 21hThu 3 Dec, 19:00 UTCFW
  5. 41d 21hThu 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

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

Reaction 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 At Atlas - EU 2X … 1,148
    Atlas - EU 2X Medium | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · biweekly · 146 on average 1,148/ 1,250
  2. 2 Дл ДЛЯ НОВИЧКОВ |… 11
    ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10 EU · groups of 10+ · 2x · biweekly · 52 on average 11/ 200
  3. 3 Pr PROSTOJ #6 | Р… 6
    PROSTOJ #6 | Ресурсы x2 | Компоненты x1 EU · groups of 8+ · 2x · biweekly · 50 on average 6/ 200
  4. 4 Ро РОССИЙСКИЙ x2 … 355
    РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2x EU · groups of 300+ · 2x · biweekly · 48 on average 355/ 400
  5. 5 Ma Magic Rust #22… 8
    Magic Rust #22 — Vanilla 2x (Biweekly) | Pyccкий EU · groups of 150+ · 2x · biweekly · 35 on average 8/ 200
  6. 6 Ро Россия | Класс… 8
    Россия | Классика X2 | IMBA RUST 23.10 EU · groups of 100+ · 2x · biweekly · 30 on average 8/ 200

Quick answers

from the figures on this page

Map and rules

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

A procedural map of size 4,900 with seed 1739618184 runs on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

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

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits carries a 2x gather rate, as its name states. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Raids and player fights are part of play here. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Oxide. By its own description it is vanilla: nothing is changed: rates, kits and rules are as Facepunch ships them. VAC is on, Valve's anti-cheat.

About the server

In what location does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits sit?

No region tag is published by [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits; its name, though, points to Europe. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 217.114.180.19:28015 is the address it uses.

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

Rust network protocol 2635 and build 168909 on Linux is what [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits stay online?

At the moment, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is online. The uptime it reports suggests it restarted roughly 20 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

Does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits hold a steady performance?

Server fps averaged 199 over the last 48 hours, with 169 as the lowest. The maximum entity count was 154,485, covering buildings, deployables and all else in the world. The highest memory usage was 4,824 MB. What players experience as lag comes from low fps and a rising entity count.

Wipe schedule

What is the wiping pattern on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

The prediction for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits follows its tag, as too few wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC, this server wipes again: that is the force wipe that resets all Rust servers. 14 days 2 hours ago the current world was made. A two-weekly wipe schedule is published in its tags.

What does a typical wipe day on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits involve?

Averaged across its recent wipes, the busiest point drew 4 players. 47 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of recent wipes. Where it did not hold, the crowd dropped below half by day 3.5.

Lists and tags

Which meanings sit behind the tags on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): It has 200 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^b (Biweekly): The map wipes on a two-week cycle; ^v (Vanilla): Nothing is changed: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded: that is the tag list [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits appear in?

You will find [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits on the following Rust Data Lab lists: 2x gather rate servers, EU Rust servers, measured and Modded Rust servers, measured. You can find it on the server list by applying these filters: 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.

Player numbers

How does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits compare with other servers in the rankings?

Player hours over the last week put [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits at #4,299, inside the top 19% of ranked servers.

How many players does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits have at the moment?

[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits currently shows 0 players across 200 slots. The week's figures average 0 players and top out at 4. Over 48 hours, the highest average fell at 16:00 UTC, at 3 players.

How to join

How can you connect to [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?

In Rust, press F1 and enter client.connect 217.114.180.19:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp200
Max players It has 200 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

Wipe schedule

^b
Biweekly The map wipes on a two-week cycle.

Difficulty

^v
Vanilla Nothing is changed: rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under 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.