Rust HeatmapInfrared · players
IR live Players45,747 Servers11,667 Warm2,969 Fresh wipes · 3h96 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–100° · slots

HAPER #1

Online 185.189.255.128:35400 checked 6m ago

moddedoxide
Sp1 · players now 0/ 100
0% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 5°
Wed 04:00flare: a wipe in that hourFri 01:00
1
7-day average
peak 5
#3,861
rank
top 17%
7d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 6m ago

Li2Players

AveragePeak
0246804:0013:0023:0007:0016:0001:00

Hourly average and peak, UTC.

Li3Server performance

05010015020004:0013:0023:0007:0016:0001: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.

Li4Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Bx1Wipe 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 days
usual gap
between real wipes
25%
on rhythm
of its recent wipes
2
wipe-day peak
players, last three wipes
0%
crowd held
else 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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 10:47 UTC7d ago 1 – running 0
Sat 17 Oct, 09:42 UTC12d ago 4 halved by day 2 5 days 1
Fri 16 Oct, 15:05 UTC13d ago 2 – 0.8 days 1
Thu 15 Oct, 00:53 UTC15d ago 3 – 1.6 days 0
Mon 5 Oct, 12:33 UTC24d ago 3 halved by day 2 9.5 days 1
Sat 3 Oct, 18:29 UTC26d ago 7 – 1.8 days 0
Fri 2 Oct, 09:53 UTC27d ago 4 – 1.4 days 0
Fri 2 Oct, 01:06 UTC28d ago 3 – 0.4 days 0
Thu 1 Oct, 12:43 UTC28d ago 3 – 0.5 days 1
Fri 25 Sep, 10:03 UTC34d ago 5 halved by day 3 6.1 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 151 on average
19 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
126 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 122 on average
32 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 97 on average
6 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 94 on average
21 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 86 on average
114 / 200

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on HAPER #1?

Its recent wipes drew an average peak of 2 players. 31 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 0% of its recent wipes. In the wipes that did not hold, numbers dropped below half by day 2.

What is the wipe schedule on HAPER #1?

Wipes come at irregular times on HAPER #1, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 7 days 16 hours ago.

Population

How busy is HAPER #1?

HAPER #1 currently has 0 of its 100 slots filled. A seven-day average of 1 players, with a peak of 5. Look at 18:00 UTC for the last 48 hours: that hour averaged 4 players.

How does HAPER #1 rank against other Rust servers?

Player hours over seven days put HAPER #1 at #3,861, in the top 17% of ranked servers.

Rules and settings

Which map does HAPER #1 run?

The map on HAPER #1 is procedural, size 4,000 with seed 2006006615, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map.

What are the rules and settings on HAPER #1?

A gather rate is not given in the name HAPER #1. The group limit is 10 players. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins run on this server. Anti-cheat: Valve's VAC is on.

Server details

Which version of Rust does HAPER #1 run?

The build on HAPER #1 is Rust network protocol 2635 and build 168909, running on Windows. To join, your game must match the protocol; Steam handles the update.

Is HAPER #1 online, and how reliable is it?

Online now: HAPER #1. The uptime it reports puts the last restart at about 11 minutes ago. 167 of 168 hours up over the last 7 full days, which is 99%. The first record of it on Rust Heatmap is 13 September 2026.

Where is HAPER #1 located?

No region is published by HAPER #1. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. You can reach it at 185.189.255.128:35400.

Does HAPER #1 run smoothly?

The last 48 hours brought an average of 85 server fps and a floor of 68. Buildings, deployables and the rest of the world came to as much as 93,513 entities. The highest memory use was 2,972 MB. What players call lag is low fps together with a growing entity count.

Lists and filters

Which Rust Heatmap lists and filters include HAPER #1?

Modded Rust servers, by live population are the Rust Heatmap lists that HAPER #1 fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What do the server tags on HAPER #1 mean?

The game's server browser reads the tags HAPER #1 publishes: gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): The slot count is 100; ts10 (Group limit): A team holds no more than 10; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

How to join

How do I join HAPER #1?

To join by console, open it with F1 in Rust and enter client.connect 185.189.255.128:35400. Or press Launch Rust on this page, which connects you through Steam. https://discord.com/invite/MN5qPd5JDZ is where its website is.

KeyServer tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp100
Max players The slot count is 100.
ts10
Group limit A team holds no more than 10.
v2635
Protocol The server runs game protocol 2635, so your game has to match it.
cs168909
Build The game build here is 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The game is changed by settings or plugins, so it sits 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.