On the class lists: D (53), with population over 48 hours and no performance mark.
Players now4/ 1004% full
7-day average0peak 4
Rank#4,086top 18%
Last wipe7d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
82/ 100
B+
Holds a respectable place: #4,086 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 85 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
87/ 100
A−
Climbing fast: up 3,013 places this week.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
Rank
daily · 1 is best
RankRank in region
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
12 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·W·WW··
···WWW·
W······
···WWW·
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.
Wipes
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 UTC26d 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
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
classmates: the same kind of game, then region, group limit, rate and wipes
HAPER #1 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 185.189.255.128:35400.
How reliable is HAPER #1, and is it up?
The server is up: HAPER #1 is online now. According to its reported uptime, the last restart was about 15 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does HAPER #1 run?
The average over the last 48 hours was 85 server fps, and it never went below 67. At its peak, it held 93,513 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,981 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is HAPER #1 running?
The server HAPER #1 is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does HAPER #1 reset?
HAPER #1 wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 7 days 7 hours.
What should you expect from wipe day on HAPER #1?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 31 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 2.
Player numbers
Where does HAPER #1 sit among Rust servers?
Over the last seven days, HAPER #1 has #4,086 for player hours, in the top 18% of all ranked servers.
What does the population on HAPER #1 look like?
HAPER #1 is showing 4 players right now, with 100 slots in total. The seven-day average is 0 players, with a peak of 4. The busiest time in the last 48 hours was 19:00 UTC, with an average of 4 players.
Tags and filters
How should you read the tags on HAPER #1?
You'll see HAPER #1 tagged with gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): The server holds 100 slots; ts10 (Group limit): No team may go above 10; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does HAPER #1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count HAPER #1 among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is HAPER #1 set up, and what rules does it keep?
The name of HAPER #1 gives no gather rate. A group here can reach 10 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on HAPER #1?
HAPER #1 runs a game-generated procedural map at size 4,000, seed 2006006615. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto HAPER #1?
Enter client.connect 185.189.255.128:35400 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/MN5qPd5JDZ.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersThe server holds 100 slots.
ts10
Group limitNo team may go above 10.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).