Offline 121.109.233.182:28015 checked 18d ago
haruka
Connect
srv = rust.server("121.109.233.182:28016")
print(srv.connect_command)
Right now
srv.summary()
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. 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 best
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 11:23 UTC25d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 121.109.233.182:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:23 UTC
- hostname
- –
- first seen
- 13 Sep 2026
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 · 155 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 37/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Player counts
How does haruka compare in the rankings?
Player hours over seven days put haruka at #15,824, in the top 72% of the ranked set.
How many players does haruka hold at once?
Offline now for haruka, with the last sample 18 days 19 hours ago.
Server facts
What Rust version does haruka run?
The build is Rust network protocol 2634 and build 166652 on Windows, run by haruka. Joining needs the same protocol on your game; Steam handles the update.
How reliable is haruka, and is it online now?
The latest sample has haruka offline, with a last sighting 18 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does haruka run from?
No region is published by haruka. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 121.109.233.182:28015.
Map and rules
What rules and settings are recorded for haruka?
The name haruka carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has haruka selected?
haruka runs a procedural map, which the game generates.
Wipe data
When does haruka wipe, and how often?
A rhythm cannot be read from the wipes of haruka on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 25 days 15 hours ago.
On haruka, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold haruka, and which filters?
These Rust Data lists include haruka: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on haruka?
The game's server browser reads these tags from haruka: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to haruka?
In Rust, F1 opens the console: type client.connect 121.109.233.182:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.