Online 185.189.255.128:35400 checked 10m ago
HAPER #1
Connect
srv = rust.server("185.189.255.128:35410")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 10:47 UTC7d ago | 1 | NaN | running | 0 |
| 1 | Sat 17 Oct, 09:42 UTC12d ago | 4 | halved by day 2 | 5 days | 1 |
| 2 | Fri 16 Oct, 15:05 UTC13d ago | 2 | NaN | 0.8 days | 1 |
| 3 | Thu 15 Oct, 00:53 UTC15d ago | 3 | NaN | 1.6 days | 0 |
| 4 | Mon 5 Oct, 12:33 UTC24d ago | 3 | halved by day 2 | 9.5 days | 1 |
| 5 | Sat 3 Oct, 18:29 UTC26d ago | 7 | NaN | 1.8 days | 0 |
| 6 | Fri 2 Oct, 09:53 UTC27d ago | 4 | NaN | 1.4 days | 0 |
| 7 | Fri 2 Oct, 01:06 UTC28d ago | 3 | NaN | 0.4 days | 0 |
| 8 | Thu 1 Oct, 12:43 UTC28d ago | 3 | NaN | 0.5 days | 1 |
| 9 | Fri 25 Sep, 10:03 UTC34d ago | 5 | halved by day 3 | 6.1 days | 0 |
| 10 | Thu 24 Sep, 10:04 UTC35d ago | 3 | NaN | 1 days | 0 |
| 11 | Tue 22 Sep, 11:44 UTC37d ago | 4 | NaN | 1.9 days | 1 |
| 12 | 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.
display(srv.map, srv.info())Map
4000 · seed 2006006615
- map
- Procedural Map
- size
- 4000
- seed
- 2006006615
Server
srv.info()- 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
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 22/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 8/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 28/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 50/200 |
Quick answers
From the figures on this page.
Population data
How does HAPER #1 compare in the rankings?
Player hours over seven days put HAPER #1 at #3,861, in the top 17% of the ranked set.
How many players does HAPER #1 hold at once?
HAPER #1 reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 1 players and peaked at 5. The 48-hour sample puts the busiest hour at 18:00 UTC, averaging 4 players.
About the server
How smoothly does HAPER #1 run?
Averaged over 48 hours: 86 server fps, never under 68. The entity count peaked at 93,513, covering buildings, deployables and the rest of the world. The memory field tops out at 2,972 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on HAPER #1?
The build is Rust network protocol 2635 and build 168909 on Windows, run by HAPER #1. Joining needs the same protocol on your game; Steam handles the update.
How reliable is HAPER #1, and is it online now?
Online is the state at the latest refresh for HAPER #1. A restart about 40 minutes ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does HAPER #1 sit?
No region is published by HAPER #1. Rust Data does not look up where the machine stands; it shows where a server says it is. 185.189.255.128:35400 is its address.
Settings and map
Which settings and rules does HAPER #1 run?
You will not find a gather rate in the string HAPER #1. Group size tops out at 10 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on HAPER #1?
Size 4,000, seed 2006006615: the procedural map on HAPER #1, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does HAPER #1 wipe, and on what schedule?
Irregular wipe times on HAPER #1 leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 7 days 17 hours ago.
What is wipe day on HAPER #1 like?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 31 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 2.
Tags, lists
Where does HAPER #1 appear among Rust Data lists and filters?
These Rust Data lists include HAPER #1: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on HAPER #1 hold?
Read by the game's server browser, the tags HAPER #1 publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts10 (Group limit): The team cap is 10; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to HAPER #1?
Enter client.connect 185.189.255.128:35400 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/MN5qPd5JDZ.