Skip to the page
Network live 11,848 servers online 93,384 players aboard 381 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

HAPER #1

Online 185.189.255.128:35400 checked 13m ago

moddedoxide
Tracking number · connect
Launch Rust and join Website
Wipe progress · wiped 7d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
3/ 100 players now 3% full
07-day averagepeak 4
#4,236ranktop 19%
7d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
0123416:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

05010015020016:0001:0010:0020:0005:0014: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.

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.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

1.5 daysusual gapbetween real wipes
25%on rhythmof its recent wipes
2wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 2

The first 48 hours of its last wipes

Thu 22 OctSat 17 OctFri 16 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.

Wipes

every wipe as a delivery, newest first
  1. Thu 22 Oct, 10:47 UTC 11:47 UK · 7d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Sat 17 Oct, 09:42 UTC 10:42 UK · 12d ago
    Wipe delivered
    Peak
    4
    Crowd
    halved by day 2
    Lasted
    5 days
    Players before
    1
  3. Fri 16 Oct, 15:05 UTC 16:05 UK · 13d ago
    Wipe delivered
    Peak
    2
    Crowd
    –
    Lasted
    0.8 days
    Players before
    1
  4. Thu 15 Oct, 00:53 UTC 01:53 UK · 14d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    1.6 days
    Players before
    0
  5. Mon 5 Oct, 12:33 UTC 13:33 UK · 24d ago
    Wipe delivered
    Peak
    3
    Crowd
    halved by day 2
    Lasted
    9.5 days
    Players before
    1
  6. Sat 3 Oct, 18:29 UTC 19:29 UK · 25d ago
    Wipe delivered
    Peak
    7
    Crowd
    –
    Lasted
    1.8 days
    Players before
    0
  7. Fri 2 Oct, 09:53 UTC 10:53 UK · 27d ago
    Wipe delivered
    Peak
    4
    Crowd
    –
    Lasted
    1.4 days
    Players before
    0
  8. Fri 2 Oct, 01:06 UTC 02:06 UK · 27d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    0.4 days
    Players before
    0
  9. Thu 1 Oct, 12:43 UTC 13:43 UK · 28d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    0.5 days
    Players before
    1
  10. Fri 25 Sep, 10:03 UTC 11:03 UK · 34d ago
    Wipe delivered
    Peak
    5
    Crowd
    halved by day 3
    Lasted
    6.1 days
    Players before
    0
Show all 13 wipes
  1. Thu 24 Sep, 10:04 UTC 11:04 UK · 35d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    1 days
    Players before
    0
  2. Tue 22 Sep, 11:44 UTC 12:44 UK · 37d ago
    Wipe delivered
    Peak
    4
    Crowd
    –
    Lasted
    1.9 days
    Players before
    1
  3. Sun 13 Sep, 16:38 UTC 17:38 UK · 45d ago
    Wipe delivered
    Peak
    2
    Crowd
    held half
    Lasted
    8.8 days
    Players before
    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 parcels

Similar servers

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

  1. ShockRust | Blue | NoLimitno group limit · 149 on average 183 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 127 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average 182 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average 85 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average 343 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 86 on average 246 / 700
Help desk

Quick answers

From the figures on this page.

Player activity

How does HAPER #1 compare with other Rust servers in the rankings?

A seven-day player-hours count places HAPER #1 at #4,236: the top 19% of every ranked server.

Is HAPER #1 busy at the moment?

The current count is 3 players on 100 slots for HAPER #1. Averaged over the past week: 0 players, peaking at 4. The busiest hour over the last 48 hours was 19:00 UTC, averaging 4 players.

Map and rules

What is the current map on HAPER #1?

Generated by the game with seed 2006006615, the procedural map on HAPER #1 is size 4,000. You can see the map on RustMaps from this page, since one size and seed give one map.

What settings and rules should you know for HAPER #1?

The name of HAPER #1 gives no gather rate. The group limit is 10 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both on. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Oxide. VAC, Valve's anti-cheat, is switched on.

Operator and location

What is the location of HAPER #1?

You will find no region published by HAPER #1. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. The address to connect to is 185.189.255.128:35400.

What is the performance like on HAPER #1?

Averaged over the last 48 hours, server fps was 86, with a low of 67. The world held as many as 92,982 entities: buildings, deployables and the rest. Memory use peaked at 2,981 MB. What players call lag is the mix of low fps and an entity count that keeps climbing.

How reliable is HAPER #1, and is it currently online?

HAPER #1 is up and online at the moment. About 12 hours ago is when it last restarted, judged by the uptime it gives. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.

What Rust version is HAPER #1 using?

The version on HAPER #1 is Rust network protocol 2635 and build 168909, running on Windows. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

What should you expect from wipe day on HAPER #1?

2 players is the average peak across its recent wipes. After 31 hours the latest wipe's crowd hit its peak. Half the peak or more was held until the next wipe in 0% of recent wipes. Where that did not hold, it dropped below half by day 2.

On what schedule does HAPER #1 reset its map?

HAPER #1 wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. The world it is running was made 7 days 4 hours.

Tags and listings

On Rust Wipe Tracker, which lists and filters is HAPER #1 part of?

The Rust Wipe Tracker lists that include HAPER #1 are: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What is the meaning of the server tags on HAPER #1?

gmvanilla (Game mode): Survival in vanilla form; mp100 (Max players): Slot count: 100; ts10 (Group limit): Team size caps at 10; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded are the tags HAPER #1 publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

What steps do you take to join HAPER #1?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 185.189.255.128:35400. Its website can be found at https://discord.com/invite/MN5qPd5JDZ.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp100
Max players Slot count: 100.
ts10
Group limit Team size caps at 10.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it's listed 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.