Online EA 222.224.192.138:28015 checked 7m ago
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]
Connect
srv = rust.server("222.224.192.138: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, 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 6% of all ranked servers, top 24% 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 6d 17h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 17h | 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 35, 23 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 13:17 UTC27d ago | 35 | 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:28015
- region
- EA
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 13:32 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 · 34 on average | 30/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 17/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 13/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 12/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 7/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 11/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] rank?
Player hours over the last seven days: #1,291 for [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA], #131 in Asia, within the top 6% of the ranked set.
How many players does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] hold at once?
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] reports 2 players at this refresh, with 40 slots configured. Over the last seven days it averaged 6 players and peaked at 16. Peak hour in the last 48 hours: 10:00 UTC, mean 11 players.
Server data
What does performance look like on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
Averaged over 48 hours: 57 server fps, never under 41. Buildings, deployables and all else in the world took the count as high as 152,818 entities. Memory peaked at 3,413 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] on?
Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] runs. Steam updates your game for you, but the protocol must match to join.
How reliable is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA], and is it up?
The current sample puts [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] online. A restart about 3 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] hosted?
With its EA tag, [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. 222.224.192.138:28015 is its address.
Map and rules
What rules and settings are recorded for [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
The name [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: no combat between players. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] loaded?
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] runs a custom map, size 4,000. The published file is on this page for download.
Wipes and dates
When does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] wipe, and how often?
The only wipe [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 27 days 12 hours ago. A monthly wipe schedule is published in its tags.
What is wipe day on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] like?
Recent wipes averaged 35 players at their peak. 23 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
These Rust Data lists include [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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 A (Tokyo) |Japan PvE [ASIA]?
A ikkunn53.com hostname is published by [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] and by 5 other servers we track, which suggests the same operator runs them.
Which meanings do the tags on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] hold?
Read by the game's server browser, the tags [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; EA (East Asia): In the server browser it sits under East Asia; rustmaps (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://www.ikkunn53.com/rust is the website recorded for it.