12 h a line, newest at the bottomeach line drawn about its own mean; the figure at its end is the reading thenthe ink shakes with each hour's changeCAL step = 2 players
Now
2of 100 slots
Motion · 24 h
M0.2▲rising+2 players
Sharpest hour
−2into Wed 21:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Channel 2 · instrument health
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Channel 3 · rank movement
Rank
daily · 1 is best
RankRank in region
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Expected events
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 gap
1.5 daysbetween real wipes
on rhythm
25%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 2
The first 48 hours of its last wipes
Thu 22 OctSat 17 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.
Event catalogue
Wipes
newest first
Wiped
M
Peak
First 48 h
Crowd
Lasted
Players before
Thu 22 Oct, 10:47 UTC7d ago
M0.0▲rising
1
–
running
0
Sat 17 Oct, 09:42 UTC12d ago
M0.5▲rising
4
halved by day 2
5 days
1
Fri 16 Oct, 15:05 UTC13d ago
M0.0▲rising
2
–
0.8 days
1
Thu 15 Oct, 00:53 UTC14d ago
M0.5▲rising
3
–
1.6 days
0
Mon 5 Oct, 12:33 UTC24d ago
M0.3▲rising
3
halved by day 2
9.5 days
1
Sat 3 Oct, 18:29 UTC25d ago
M0.8▲rising
7
–
1.8 days
0
Fri 2 Oct, 09:53 UTC27d ago
M0.6▲rising
4
–
1.4 days
0
Fri 2 Oct, 01:06 UTC27d ago
M0.5▲rising
3
–
0.4 days
0
Thu 1 Oct, 12:43 UTC28d ago
M0.3▲rising
3
–
0.5 days
1
Fri 25 Sep, 10:03 UTC34d ago
M0.7▲rising
5
halved by day 3
6.1 days
0
Thu 24 Sep, 10:04 UTC35d ago
M0.5▲rising
3
–
1 days
0
Tue 22 Sep, 11:44 UTC37d ago
M0.5▲rising
4
–
1.9 days
1
Sun 13 Sep, 16:38 UTC46d ago
M0.3▲rising
2
held half
8.8 days
0
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Nearby stations
Similar servers
the same kind of game, then region, group limit, rate and wipes
HAPER #1 runs a procedural map of size 4,000 with seed 2006006615, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on HAPER #1?
No gather rate appears in the name of HAPER #1. Up to 10 players can be in a group. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on HAPER #1?
A reading taken now shows 2 players on HAPER #1, which has 100 slots. The seven-day average is 0 players, with a peak of 4. Averaged over the last 48 hours, the busiest hour was 19:00 UTC at 4 players.
How does HAPER #1 rank against other Rust servers?
On player hours for the past week, HAPER #1 sits at #4,120, which puts it inside the top 18% of every ranked server.
Operator and location
How reliably does HAPER #1 stay online?
Right now, you can reach HAPER #1. Its reported uptime points to a restart about 14 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. 13 September 2026 is when Rust Server Trends first recorded it.
Does HAPER #1 hold a steady tick rate?
The 48-hour average is 85 server fps; 67 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 93,449. Its highest memory use was 2,981 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does HAPER #1 run from?
A region is not published by HAPER #1. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 185.189.255.128:35400 is the address it uses.
Which Rust version is HAPER #1 running?
Rust network protocol 2635 and build 168909 on Windows is what HAPER #1 runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on HAPER #1?
2 players, on average, was the busiest crowd at its recent wipes. 31 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half in the wipes where it didn't hold.
How often does HAPER #1 wipe, and on which days?
There is no next wipe to predict at HAPER #1, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 7 days 6 hours.
Server tags
What do the server tags on HAPER #1 mean?
Tags published by HAPER #1 and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts10 (Group limit): Teams are capped at 10 players; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does HAPER #1 appear?
You will find HAPER #1 on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to join
How do you connect to HAPER #1?
To join, enter client.connect 185.189.255.128:35400 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://discord.com/invite/MN5qPd5JDZ is where its website lives.
Instrument codes
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts10
Group limitTeams are capped at 10 players.
v2635
ProtocolGame protocol 2635: to join, your game must match this version.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet is the standard network layer for the game, and it's used here.
$r?
Region codeThe server has no region code.
Mods and access
^o
OxideOxide (uMod) is the plugin framework running here.
^z
ModdedThe game is changed by plugins or settings, placing it 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.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.
