RUST METRICSFlight deck · live data
Data live Servers11,682 Players54,903 Populated3,147 Fresh wipes 3 h122 Scan5 min
‹ All servers185.189.255.128:35400
Online Full Queue Fresh wipe Wipe due No query

HAPER #1

Online 185.189.255.128:35400 checked 7m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Fri 00:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 88 SERVER FPS

Server fps

48 h low 68 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 92,630 ×1000

Entities

48 h range 90,164–93,513 · memory 2,948 MB
1239 ET SINCE RESTART 22:58

Uptime

22 h 58 min since its last restart, at the last reading
7-day average1peak 5
Rank#3,868top 17%
Last wipe7d agono schedule published
Next wipe–no rhythm it keeps
Memory2,948MB48 h peak 5 players
REC 1

Players

AveragePeak
0246802:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

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.

PLAN

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.

LOG

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What happens on HAPER #1 when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. 31 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 2 it fell below half.

When does HAPER #1 wipe?

No next wipe can be predicted for HAPER #1, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 7 days 14 hours ago the current world was made.

Tags

Which tags does HAPER #1 carry, and what do they mean?

These are the tags HAPER #1 publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): The server holds 100 slots; ts10 (Group limit): You may team up with at most 10; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does HAPER #1 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry HAPER #1: Modded Rust servers, checked live. These filters 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.

Player count

Where does HAPER #1 sit in the rankings?

Ranking for HAPER #1: #3,868 on seven-day player hours, top 17% of all ranked servers.

What is the population on HAPER #1?

Current headcount on HAPER #1: 0 players, 100 slots available. Check: players over seven days. Average 1, peak 5. Average at the busiest hour was 4 players, at 18:00 UTC over the last 48 hours.

Operator and location

Which location does HAPER #1 run from?

Reading: location. HAPER #1 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.189.255.128:35400.

What Rust version is HAPER #1 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by HAPER #1. Matching protocol is required to join. Let Steam update your game.

Is performance on HAPER #1 within range?

Over the last 48 hours the average was 85 server fps; the floor was 68. Reading: 93,513 entities at the highest. That covers buildings, deployables and everything else. Reading: 2,972 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

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

HAPER #1 reports online. Status: normal. By its reported uptime, the last restart was roughly 22 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

How is HAPER #1 configured, and what rules are in force?

No gather rate appears in the name: HAPER #1. Group size, maximum: 10 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on HAPER #1?

Size 4,000 and seed 2006006615: the game generates the procedural map on HAPER #1 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join HAPER #1?

Check: join. Open Rust, press F1, then enter client.connect 185.189.255.128:35400. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/MN5qPd5JDZ is where its website sits.

PLACARDS

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 The server holds 100 slots.
ts10
Group limit You may team up with at most 10.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.