Online EA 222.224.192.138:28024 checked 10m ago
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]
Connect
srv = rust.server("222.224.192.138:28025")
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, 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 best
Top 10% of all ranked servers, top 40% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 6h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 6h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 15, 18 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 13:18 UTC26d ago | 15 | 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
4000 · seed 130303
- map
- Custom Map
- size
- 4000
- seed
- 130303
- custom map
- download
Server
srv.info()- address
- 222.224.192.138:28024
- region
- EA
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 13:49 UTC
- hostname
- game.ikkunn53.com
- first seen
- 13 Sep 2026
Operator · ikkunn53.com
rust.servers(operator="ikkunn53.com").sort_values("players")
6 servers publish a ikkunn53.com hostname.
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 | [坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 | EA · groups of 8+ · monthly · 35 on average | 37/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 21/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 15/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 21/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 19/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 14/100 |
Quick answers
From the figures on this page.
Population data
How does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] compare in the rankings?
Player hours over the last seven days: #2,264 for [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], #216 in Asia, within the top 10% of the ranked set.
How full does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] run?
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] reports 6 players at this refresh, with 40 slots configured. Over the last seven days it averaged 2 players and peaked at 9. Peak hour in the last 48 hours: 13:00 UTC, mean 7 players.
Server facts
What does performance look like on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
The 48-hour average is 57 server fps, with a low of 39. Entity numbers reached 117,104, and that includes buildings, deployables and the rest. The memory field tops out at 3,494 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], and is it up?
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] reports itself online at the current refresh. Count back 1 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
In which location is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] hosted?
The EA tag is what [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] uses to list itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 222.224.192.138:28024.
Rules, settings, map
Which rules apply on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], and what settings?
No gather rate appears in the name: [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] runs a custom map, size 4,000. The published file is on this page for download.
Wipe data
When does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] wipe, and how often?
The only wipe [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 26 days 23 hours ago. Its tags carry a monthly wipe schedule.
What is wipe day on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] like?
Recent wipes averaged 15 players at their peak. 18 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] appear among Rust Data lists and filters?
These Rust Data lists include [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which operator runs [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] and 5 other servers we track both publish a ikkunn53.com hostname, so the same operator most likely runs them.
Which meanings do the tags on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] hold?
The game's server browser reads these tags from [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it sits under East Asia; rustmaps (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
In Rust, F1 opens the console: type client.connect 222.224.192.138:28024. Launch Rust on this page does the same by opening the game through Steam and connecting. https://www.ikkunn53.com/rust is the website recorded for it.