Rust Server Analytics 52,148 players11,694 servers
All servers
Drill-through Server detail

HAPER #1

Online 185.189.255.128:35400 checked 11m ago

Drill-through
FilterServeris HAPER #1
Attributes
moddedoxide
Last refreshed
Players now 0/ 100
7-day average 1 peak 5
Rank #3,868 top 17%
Last wipe 7d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0246802:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020002:0011:0021:0006:0015:0000: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 Oct14 Oct22 Oct30 Oct

Top 17% 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.

usual gap1.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%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.

Wipes

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

Similar servers

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

Quick answers

from the figures on this page

Wipe data

When does HAPER #1 wipe?

The next wipe on HAPER #1 cannot be predicted, because it wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 7 days 15 hours ago.

Wipe day on HAPER #1: what should you expect?

Recent wipes averaged a busiest count of 2 players. The highest player count on the latest wipe arrived 31 hours in. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. By day 2 it had fallen below half where the hold failed.

Server

What is the hosting location of HAPER #1?

No region appears in what HAPER #1 publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 185.189.255.128:35400.

Which Rust version is HAPER #1 on?

Rust network protocol 2635 and build 168909 on Windows is the setup for HAPER #1. Your game must match the protocol to join, and Steam applies that update.

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

HAPER #1 reports online at the current check. The uptime it reports puts the last restart at about 22 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. The first sighting of it by Rust Server Analytics was on 13 September 2026.

What performance does HAPER #1 show?

Over 48 hours the average held at 85 server fps, and the minimum was 68. Entity count reached 93,513, covering buildings, deployables and the rest of the world. At its highest, memory use was 2,972 MB. Players experience lag as low fps combined with a rising entity count.

Lists and tags

What do HAPER #1's tags stand for?

Tags from HAPER #1, as read by the game's server browser, are: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): 100 slots in total; ts10 (Group limit): Team size is capped at 10; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Modded listing, where plugins or settings change the game. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does HAPER #1 appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include HAPER #1: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does HAPER #1 sit among Rust servers?

Player hours for the last seven days place HAPER #1 at #3,868, in the top 17% of the ranked field.

What is the population of HAPER #1?

Of 100 slots, 0 are filled on HAPER #1 at this refresh. Averaging 1 players across seven days, the server reached a peak of 5. Averaged over 48 hours, activity is highest at 18:00 UTC with 4 players.

Settings

What are the settings on HAPER #1, and its rules?

Gather rate is not mentioned in the name of HAPER #1. The cap on group membership is 10 players. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. Anti-cheat status: VAC on.

What is the map for HAPER #1?

HAPER #1 uses a procedural map of size 4,000 with seed 2006006615, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

How can a player join HAPER #1?

In the Rust console (F1), enter client.connect 185.189.255.128:35400. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://discord.com/invite/MN5qPd5JDZ is its website.

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players 100 slots in total.
ts10
Group limit Team size is capped at 10.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code The region code is blank.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded Modded listing, where plugins or settings change the game.

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.