[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28027 checked 13m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 14% of all ranked servers, top 50% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 35d 9h | 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 7, 46 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 5 Oct, 13:53 UTC23d ago | 7 | – | running | 1 |
| Sat 3 Oct, 12:17 UTC25d ago | 1 | held half | 2.1 days | 0 |
| Sun 20 Sep, 11:27 UTC38d ago | 1 | halved by day 1 | 13 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本 | EA · groups of 8+ · monthly · 35 on average | 30 / 100 |
| 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 13 / 88 |
| [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 14 / 100 |
| [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 10 / 100 |
| 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 8 / 200 |
| 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 11 / 100 |
Quick answers
from the figures on this pageWipe data
On what cycle does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipe?
The force wipe is the only wipe for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world now in play was created 23 days 19 hours ago. A monthly wipe schedule is published in its tags.
On [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. 46 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 50% of recent wipes. By day 1 it had fallen below half where the hold failed.
Server details
What is the hosting location of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Its EA tag puts [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] in Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 222.224.192.138:28027.
Which Rust version is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] on?
On Windows, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. The protocol has to match before you can join; Steam updates it automatically.
Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] up, and how steady is its uptime?
As of the latest refresh, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is online. The uptime it reports puts the last restart at about 10 hours ago. 99% uptime over the last 7 full days, equal to 167 of 168 hours. It entered Rust Server Analytics records on 17 September 2026.
Does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] perform well?
Server fps averaged 59 over the last 48 hours, with a floor of 54. At its highest the entity count was 124,425, including buildings, deployables and all else. Memory use reached 3,273 MB at peak. Lag, for players, means low fps alongside a growing entity count.
Lists and tags
How should the tags on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] be read?
gmrust (Game mode): Survival in the standard Rust format; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^m (Monthly): Monthly wipes, aligned with the force wipe; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play; EA (East Asia): East Asia is the region it appears under in the browser are the tags [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: Modded Rust servers: live data and PvE Rust servers by live population. These filters bring it up 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.
Whose server is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
5 other servers we track publish a ikkunn53.com hostname too, and so does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], which points to a shared operator.
Player numbers
Against other Rust servers, how does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] compare?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] holds #3,083 on seven-day player hours and #280 in Asia, inside the top 14% of the ranked field.
How many players does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] carry?
Population at the current refresh: 2 players on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], against 40 slots. The seven-day mean is 1 players, against a peak of 6. Averaged over 48 hours, activity is highest at 06:00 UTC with 2 players.
Map and rules
What are the settings on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], and its rules?
Gather rate is not mentioned in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. The game's default 8-player group limit is in force. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. Anti-cheat status: VAC on.
What is the map for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
A procedural map of size 4,000 with seed 130303, generated by the game, runs on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Because size and seed determine the map, it can be viewed on RustMaps via this page. The name of the map is Custom Map.
How to join
How can a player join [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 222.224.192.138:28027. https://www.ikkunn53.com/rust is its website.