[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28018 checked 11m 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 10% of all ranked servers, top 38% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 14:47 UTC, in 5h. Its biweekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 5h | Thu 29 Oct, 14:47 UTC | its own |
| 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 14d 5h | Thu 12 Nov, 14:47 UTC | its own |
| 28d 5h | Thu 26 Nov, 14:47 UTC | its own |
| 35d 9h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 42d 5h | Thu 10 Dec, 14:47 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 14:47 UTC13d ago | 17 | – | running | 4 |
| Fri 2 Oct, 13:17 UTC26d ago | 12 | halved by day 7 | 13.1 days | 0 |
| Thu 17 Sep, 14:50 UTC41d ago | 14 | halved by day 11 | 14.9 days | 2 |
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 16+ · biweekly · 58 on average | 59 / 200 |
| [JP][PvE]mameserver初心者おいで！ | EA · groups of 8+ · biweekly · 8 on average | 3 / 65 |
| JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド | EA · groups of 1000+ · 1x · biweekly · 7 on average | 10 / 69 |
| [喜相逢] PVE丨仿官原倍丨萌新养老 | EA · groups of 12+ · biweekly · 5 on average | 1 / 100 |
| [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 | EA · groups of 16+ · biweekly · 4 on average | 1 / 50 |
| 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 | EA · groups of 8+ · biweekly · 3 on average | 4 / 100 |
Quick answers
from the figures on this pageWipe data
On what cycle does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe?
The tag sets the prediction: too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes are on record to confirm its schedule. Thursday 29 October at 14:47 UTC is the date the next wipe falls on. 13 days 18 hours ago the current world was made. Its tags publish a wipe schedule of every two weeks.
On [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], what happens on wipe day?
Recent wipes averaged a busiest count of 14 players. 46 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. In the other cases the crowd dropped below half by day 9.
Server details
Which location hosts [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The EA tag on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists it in Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 222.224.192.138:28018.
Which Rust version is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] on?
The platform is Windows, with Rust network protocol 2635 and build 168909 running on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The protocol has to match before you can join; Steam updates it automatically.
What uptime does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] show, and is it up?
The current status of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is online. The uptime it reports puts the last restart at about 10 hours 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 B (Tokyo) |Japan PvE [ASIA] perform well?
Server fps averaged 56 over the last 48 hours, with a floor of 31. Entity count reached 129,989, covering buildings, deployables and the rest of the world. Memory use reached 3,568 MB at peak. Players experience lag as low fps combined with a rising entity count.
Tags
How should the tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] be read?
gmrust (Game mode): Rust survival, standard ruleset; mp40 (Max players): Capacity of 40 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks the server wipes; ^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): Outside the standard tag set, added by the owner or a plugin are the tags [JPN] IKKUNN Server B (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 B (Tokyo) |Japan PvE [ASIA]?
The following Rust Server Analytics lists count [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] among their servers: 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: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
By whom is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?
5 other servers we track publish a ikkunn53.com hostname too, and so does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], which points to a shared operator.
Player numbers
What position does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold in the server rankings?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] holds #2,221 on seven-day player hours and #213 in Asia, inside the top 10% of the ranked field.
How many players does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] carry?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] holds 0 players of its 40 slots as of the latest update. The seven-day mean is 2 players, against a peak of 8. Averaged over 48 hours, activity is highest at 13:00 UTC with 4 players.
Settings
What are the settings on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and its rules?
No gather rate is given in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The default group cap of 8 players applies. It runs pve, no fighting other players. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.
What is the map for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Size 4,000: a custom map runs on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], with its file published for download here.
Connection
What is the way onto [JPN] IKKUNN Server B (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:28018. https://www.ikkunn53.com/rust is its website.