Fig. 1Players on HAPER #1RG-S3963-01 · Sheet 1 of 11
Fig. 2
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.
Fig. 2FPS, entities and memoryRG-S3963-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S3963-03 · Sheet 3 of 11
Schedule
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
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.
ScheduleExpected wipesRG-S3963-04 · Sheet 4 of 11
Log
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.
Table 1Wipe logRG-S3963-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is HAPER #1 online, and what uptime has been recorded?
HAPER #1 is up at this moment. About 17 hours ago is when it last restarted, measured from the uptime it reports. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
Is HAPER #1 stable in the figures recorded?
86 server fps on average over the last 48 hours, and never under 68. Counted at its highest: 93,513 entities, buildings, deployables and the rest of the world included. 2,981 MB is the memory peak. Players feel low fps and a climbing entity count as lag.
3.
What location is recorded for HAPER #1?
A region is not published by HAPER #1. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 185.189.255.128:35400.
4.
On which Rust version is HAPER #1 running?
The platform is Windows and the version is Rust network protocol 2635 and build 168909 on HAPER #1. Steam updates your game, which must be on the same protocol for you to join.
Player data
5.
How many players are plotted on HAPER #1?
Current player count on HAPER #1: 2, of 100 slots. Averaged across seven days, the player count is 1, with a peak of 5. Averaged over the last 48 hours, the player count is highest at 18:00 UTC: 4 players.
6.
What rank has been recorded for HAPER #1?
Player hours over seven days place HAPER #1 at #3,963, within the top 18% of ranked servers.
Wipe data
7.
What happens on HAPER #1 on the day of a wipe?
An average of 2 players was recorded at the busiest point of its recent wipes. 31 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. By day 2 the crowd had fallen below half on the wipes where it did not hold.
8.
Which times and days are wipes plotted at on HAPER #1?
There is no next wipe to predict at HAPER #1, which wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 7 days 9 hours ago.
Map and rules
9.
Which settings does HAPER #1 run, and what rules?
Gather rate for HAPER #1: not stated in the name. 10 players per group at most. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.
10.
What is the map for HAPER #1?
Seed 2006006615 and size 4,000 define the procedural map HAPER #1 generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Filters
11.
On Rust Graphs, which lists and filters contain HAPER #1?
These Rust Graphs lists include HAPER #1: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
12.
On HAPER #1, what is meant by each tag?
gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 player slots; ts10 (Group limit): Teams hold no more than 10; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags HAPER #1 publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Joining the server
13.
By what method do you join HAPER #1?
Enter client.connect 185.189.255.128:35400 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/MN5qPd5JDZ.
NotesAnswered from the figuresRG-S3963-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeThe mode is vanilla survival.
mp100
Max players100 player slots.
ts10
Group limitTeams hold no more than 10.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed 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.
