Source: every five minutes, from the Steam server list.
AveragePeak
Note: hourly average and peak, UTC.
AveragePeakWipe
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
RankRank in region
Note: Top 18% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
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 wipesPlayers each hour, from the hour of the wipe
Thu 22 OctSat 17 OctFri 16 Oct
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.
The record
Wipes
Every wipe we saw, newest first.
Wiped
Peak
Crowd
Lasted
Players 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 UTC14d 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 UTC25d ago
7
–
1.8 days
0
Fri 2 Oct, 09:53 UTC27d ago
4
–
1.4 days
0
Fri 2 Oct, 01:06 UTC27d 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
Thu 24 Sep, 10:04 UTC35d ago
3
–
1 days
0
Tue 22 Sep, 11:44 UTC37d ago
4
–
1.9 days
1
Sun 13 Sep, 16:38 UTC46d ago
2
held half
8.8 days
0
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
At their busiest, its recent wipes drew 2 players on average. 31 hours after the latest wipe, the crowd peaked. Half the peak held until the next wipe in 0% of its recent wipes. In the other cases, it dropped below half by day 2.
When does HAPER #1 wipe, and how often?
No next wipe can be predicted for HAPER #1, which wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. The world you are playing on now was made 7 days 7 hours ago.
Server details
Does HAPER #1 hold a steady frame rate?
Server fps averaged 86 over 48 hours; the lowest reading was 67. At its highest the entity count reached 93,449: buildings, deployables and everything else. Memory use peaked at 2,981 MB. A climbing entity count and low fps are what players experience as lag.
Which Rust version is HAPER #1 on?
Running on Windows, HAPER #1 is on Rust network protocol 2635 and build 168909. Joining needs your game on the same protocol, which Steam updates for you.
What does uptime look like for HAPER #1, and is it online?
Right now HAPER #1 is up and running. Going by the uptime figure it gives, its last restart was around 14 hours ago. The last 7 full days gave 167 of 168 hours up, or 99% of the time. Rust Insights first logged this server on 13 September 2026.
In which location does HAPER #1 sit?
A region is not published by HAPER #1. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. Connect through 185.189.255.128:35400.
Server tags
Which meanings sit behind the tags on HAPER #1?
These tags come from HAPER #1 and are read by the game's server browser: gmvanilla (Game mode): Vanilla survival is the mode; mp100 (Max players): It holds 100 slots; ts10 (Group limit): Team size is capped at 10; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.
Where does HAPER #1 turn up among the Rust Insights lists and filters?
These Rust Insights lists include HAPER #1: Modded Rust servers, explained. 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.
Population
What does the population of HAPER #1 look like?
Of its 100 slots, HAPER #1 currently has 4 filled. The seven-day average is 0 players, and the highest point in that week was 4. Look at the last 48 hours and the peak hour is 19:00 UTC, at 4 players on average.
How does HAPER #1 compare with other Rust servers in the ranking?
On player hours for the last seven days, HAPER #1 sits at #4,086, inside the top 18% of ranked servers.
Map and rules
What settings and rules apply on HAPER #1?
Nothing about gather rate is given in the name of HAPER #1. 10 players is the most a group can hold. survival is the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. It is a Modded entry: plugins or settings modify the game. It runs plugins, Oxide of them. The server has Valve's VAC anti-cheat switched on.
What is the map on HAPER #1?
HAPER #1 runs a procedural map of size 4,000 with seed 2006006615, generated by the game. Size and seed give the same map each time, so this page lets you look at it on RustMaps.
How to join
How do you connect to HAPER #1?
To connect, start Rust and enter client.connect 185.189.255.128:35400 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you. https://discord.com/invite/MN5qPd5JDZ is its website.
The small print
Server tags
What each one means.
Published asmp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeVanilla survival is the mode.
mp100
Max playersIt holds 100 slots.
ts10
Group limitTeam size is capped at 10.
v2635
ProtocolTo join you need the same version; protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRust's standard network layer, RakNet, carries it.
$r?
Region codeNo region code is set.
Mods and access
^o
OxideA plugin framework, Oxide (uMod), is in use.
^z
ModdedThe game is changed by plugins or settings, placing it under Modded.
Note: 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.
