[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28021 checked 14m 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 8% of all ranked servers, top 31% 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 7h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 35d 7h | 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 32, 23 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 13:18 UTC26d ago | 32 | – | 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.
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 | 41 / 100 |
| 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 18 / 88 |
| [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 13 / 100 |
| [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 20 / 100 |
| 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 13 / 200 |
| 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 12 / 100 |
Quick answers
from the figures on this pageWipe data
When does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe?
Once a month [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 26 days 22 hours ago the current world was made. A monthly wipe schedule is published in its tags.
Wipe day on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: what should you expect?
The average busiest count over recent wipes is 32 players. 23 hours after the latest wipe the crowd peaked.
Server details
In which region does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit?
Its EA tag puts [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] in Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 222.224.192.138:28021 is its address.
Which Rust version is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] on?
On Windows, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.
How reliable is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and is it online now?
The current status of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is online. Its reported uptime indicates a restart roughly 55 minutes ago. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 13 September 2026.
Does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] perform well?
The 48-hour average was 55 server fps; the low was 2. Entity count reached 156,405, covering buildings, deployables and the rest of the world. Memory use reached 3,556 MB at peak. Lag, for players, means low fps alongside a growing entity count.
Lists and tags
What do [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]'s tags stand for?
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): To join, your game version must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): A region code is not set; ^m (Monthly): Monthly wipes, aligned with the force wipe; ^p (PvE): Player combat is off; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): Its browser listing sits in East Asia; rustmaps (Custom tag): Not one of Rust's standard tags; the owner or a plugin applied it are the tags [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
On Rust Server Analytics, which lists and filters feature [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
These Rust Server Analytics lists include [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: 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 C (Tokyo) |Japan PvE [ASIA]?
The same operator most likely runs [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and the 5 other servers we track that also publish a ikkunn53.com hostname.
Population
Against other Rust servers, how does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] compare?
For player hours over the last seven days, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] places #1,713 globally and #169 in Asia, in the top 8% of all ranked servers.
What is the population of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] holds 5 players of its 40 slots as of the latest update. The seven-day mean is 3 players, against a peak of 13. Across the last 48 hours, 12:00 UTC shows the highest average: 5 players.
Map and rules
What settings and rules does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] use?
The name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] does not state a gather rate. The default group cap of 8 players applies. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
Size 4,000: a custom map runs on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], with its file published for download here.
Connection
How can a player join [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
In the Rust console (F1), enter client.connect 222.224.192.138:28021. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://www.ikkunn53.com/rust is its website.