HAPER #1

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 7m ago · 185.189.255.128:35400

Abstract

We describe the public Rust server HAPER #1, reached at 185.189.255.128:35400. At the last check it held 3 of 100 places, against a seven-day mean of 1 and a peak of 5¹. It ranks #3,963 of all servers, the top 18%. It last wiped 7d ago.

Keywordsmodded oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	3/100	3% full
In the queue	0	no queue
Seven-day mean	1	peak 5, 48 h peak 5
Rank²	#3,963	top 18%
Last wipe	7d ago	no schedule published
Next wipe³	–	no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

Figure 2: Server performance. 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.

4Rank

The server stands in the top 18% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	1.5 days	between real wipes
On rhythm	25%	of its recent wipes
Wipe-day peak	2	players, last three wipes
Crowd held	0%	else halves by day 2

Thu 22 OctSat 17 OctFri 16 Oct

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 31 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Thu 22 Oct, 10:477d ago	1	–	running	0
Sat 17 Oct, 09:4212d ago	4	halved by day 2	5 d	1
Fri 16 Oct, 15:0513d ago	2	–	0.8 d	1
Thu 15 Oct, 00:5314d ago	3	–	1.6 d	0
Mon 5 Oct, 12:3324d ago	3	halved by day 2	9.5 d	1
Sat 3 Oct, 18:2926d ago	7	–	1.8 d	0
Fri 2 Oct, 09:5327d ago	4	–	1.4 d	0
Fri 2 Oct, 01:0627d ago	3	–	0.4 d	0
Thu 1 Oct, 12:4328d ago	3	–	0.5 d	1
Fri 25 Sep, 10:0334d ago	5	halved by day 3	6.1 d	0
Thu 24 Sep, 10:0435d ago	3	–	1 d	0
Tue 22 Sep, 11:4437d ago	4	–	1.9 d	1
Sun 13 Sep, 16:3846d ago	2	held half	8.8 d	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of HAPER #1 — Figure 5: The map: Procedural Map, size 4000, seed 2006006615. Open on RustMaps.

Table 4: The server's published settings.

Address	`185.189.255.128:35400`
Region	–
Max players	100
Group limit	10 max
Wipe schedule	–
Last wipe	22 Oct 2026, 10:47 UTC
Hostname	–
First seen	13 Sep 2026
Map	Procedural Map
Size	4000
Seed	2006006615

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 151 on average	88/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	133/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	145/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average	61/700
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average	161/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 85 on average	348/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of HAPER #1 smooth?

Its average server fps over the last 48 hours was 86, with a minimum of 68. Its entity count reached a maximum of 93,513, including buildings, deployables and all other world objects. Its highest memory usage was 2,981 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of HAPER #1?

No region is published by HAPER #1. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 185.189.255.128:35400 is its address.

A.3What is the reliability of HAPER #1, and is it online?

HAPER #1 is currently online. The uptime it reports indicates a restart about 16 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What is the Rust version for HAPER #1?

Rust network protocol 2635 and build 168909 is the version that HAPER #1 runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5What schedule does HAPER #1 follow for wipes?

With irregular wipe times, HAPER #1 offers no next wipe to predict. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 7 days 9 hours have passed since the current world was generated.

A.6What happens on HAPER #1 when wipe day arrives?

Across its recent wipes, the average peak population was 2 players. The peak on the latest wipe came 31 hours after it began. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. Otherwise, a fall below half took place by day 2.

Player count

A.7How does HAPER #1 compare with other Rust servers in the rankings?

Ranked by player hours across seven days, HAPER #1 holds #3,963, in the top 18% of all ranked servers.

A.8What is the population level of HAPER #1?

At this moment 3 players are on HAPER #1, which has 100 slots in total. The peak over seven days is 5, against an average of 1. Of the last 48 hours, the peak hour falls at 18:00 UTC, with an average of 4 players.

Tags, lists

A.9How should the tags on HAPER #1 be interpreted?

gmvanilla (Game mode): Survival on vanilla rules; mp100 (Max players): 100 slots are available; ts10 (Group limit): A team holds no more than 10; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags HAPER #1 publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can HAPER #1 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include HAPER #1: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.11Which settings and rules are in force on HAPER #1?

The name of HAPER #1 states no gather rate. A group holds at most 10 players. The mode is survival, which means gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

A.12What map is in use on HAPER #1?

The game generates HAPER #1's procedural map at size 4,000, from seed 2006006615. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13What steps are required to join HAPER #1?

Press F1 inside Rust to open the console and enter client.connect 185.189.255.128:35400. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. The website for this server is https://discord.com/invite/MN5qPd5JDZ.

Appendix BServer tags

What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts10,^o^z.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmvanilla`	Game mode. Survival on vanilla rules.
`mp100`	Max players. 100 slots are available.
`ts10`	Group limit. A team holds no more than 10.
`v2635`	Protocol. Joining requires the same game version: protocol 2635.
`cs168909`	Build. This server runs game build 168909.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. The region code is unset.
Mods and access
`^o`	Oxide. Oxide (uMod), a plugin framework, runs on this server.
`^z`	Modded. Modded listing: plugins or settings modify the 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.

Appendix CAbout this server, in its own words

# ДОБРО ПОЖАЛОВАТЬ НА СЕРВЕР! **Уважаемые игроки!** Если у вас возникают ошибки при подключении, особенно: > **Couldn't Download Level: proceduralmap... (Request timeout)** — не переживайте, это легко решается. Ниже всё расписано по шагам. --- ## Если не загружается карта Эта ошибка означает, что Rust не успел скачать файл карты сервера. Чаще всего проблема в интернете, кэше игры или антивирусе. ### Быстрое решение 1. Полностью закройте **Rust** и **Steam** 2. Откройте папку игры: ```text Steam\steamapps\common\Rust\maps ``` 3. Удалите **все файлы** из папки `maps` 4. Также очистите папку: ```text Steam\steamapps\common\Rust\temp ``` 5. В Steam откройте: **Настройки → Загрузки → Очистить кэш загрузок** 6. Запустите Rust и подключитесь к серверу снова --- ## Ручная установка карты Если карта всё равно не качается — установите её вручную. 1. Попросите файл карты в нашем **Discord** 2. Закройте **Rust** 3. Перейдите в папку: ```text Steam\steamapps\common\Rust\maps ``` 4. Поместите туда файл карты `.map` 5. Запустите Rust и подключитесь к серверу **Не переименовывайте файл карты** — имя должно остаться точно таким же. --- ## Нужна помощь? Если ошибка осталась или что-то не получается — заходите в наш **Discord**. Там вам помогут: - Разобраться с ошибками подключения - Выдать файл карты - Проверить настройки игры и интернета - Быстро вернуться на сервер > **Discord — самый быстрый способ получить помощь.** **Спасибо, что играете с нами!** **Увиди

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.