Artist page · Modded · on air
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28018 checked 14m ago
- Last week
- No. 1,786
- Peak
- No. 1,434
- Days on chart
- 40
Rank
- 24 Sep1,441
- 1 Oct1,873
- 8 Oct2,128
- 15 Oct2,355
- 22 Oct1,786
- now2,257
Top 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
Coming wipes
- 7d 2hThu 5 Nov, 19:00 UTCFW
- 13d 22hThu 12 Nov, 14:47 UTC
- 27d 22hThu 26 Nov, 14:47 UTC
- 35d 2hThu 3 Dec, 19:00 UTCFW
- 41d 22hThu 10 Dec, 14:47 UTC
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 14:47 UTC14d ago | 17 | – | running | 4 |
| Fri 2 Oct, 13:17 UTC27d ago | 12 | halved by day 7 | 13.1 days | 0 |
| Thu 17 Sep, 14:50 UTC42d 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
- 1 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 68/ 200
- 2 [JP][PvE]mameserver初心者おいで！ 6/ 65
- 3 JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド 4/ 123
- 4 [喜相逢] PVE丨仿官原倍丨萌新养老 10/ 100
- 5 [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 1/ 50
- 6 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 0/ 100
Quick answers
Wipe days
What should you expect on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] when wipe day comes?
Averaged over its recent wipes, the crowd reached 14 at the peak. It took 46 hours from the latest wipe for the crowd to peak. Above half the peak until the next wipe: that is what happened in 0% of its recent wipes. If the crowd did not hold, it was under half by day 9.
When does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s schedule cannot be confirmed from the wipes on record, which are too few; its tag guides the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 14 days 1 hours is how long the current world has been up. The tags say wipes come round every two weeks.
Lists and filters
Who is behind [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The same operator most likely runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, since they all publish a ikkunn53.com hostname.
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] appear in Rust Server Rank lists and filters?
These Rust Server Rank lists include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust server rankings and Rust PvE servers, ranked. Filter the server list by 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 and it shows up.
How should you read the tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The game's server browser picks up the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes, which are: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): The slot count is 40; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): To join, run the same version: protocol 2635; cs168909 (Build): Running game build 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code: none set; ^b (Biweekly): It wipes once a fortnight; ^p (PvE): The world is the danger here: players do not fight each other; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, and the browser files it under Modded; EA (East Asia): The server browser files this one under East Asia; rustmaps (Custom tag): A plugin or the owner set this tag, and it is not one of Rust's standard tags. You'll also find the current player count, the queue and when the world was made in the tags, shown at the top of this page.
Rules, map and settings
On what map does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] play?
A custom map of size 4,000 is what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs, and its file is published so you can download it from this page.
What settings and rules does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] have in place?
You will not find a gather rate in [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s name. 8 players is the group limit, the default in the game. pve is the game mode, no player-versus-player fighting. In the server browser it sits under Modded, where plugins or settings change the game. The plugins it runs are Oxide. Valve's VAC anti-cheat is switched on.
Server details
Which Rust build is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] running?
Rust network protocol 2635 and build 168909 is the version, Windows the system, and [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] the server. The same protocol is required to join, and Steam takes care of the update.
How dependable is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it online?
You will find [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] online at this moment. About 4 hours ago it restarted last, judged by its reported uptime. 167 of 168 hours is 99% of the time over the last 7 full days. The first sighting here was on 13 September 2026, logged by Rust Server Rank.
What is performance like on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Never below 31, it averaged 56 server fps across the last 48 hours. Buildings, deployables and everything else added up to as many as 131,792 entities. At its highest, memory use hit 3,568 MB. What you feel as lag is low fps and an entity count on the way up.
In which location is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hosted?
The EA tag is what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] uses to list itself in Asia. Rust Server Rank does not look up where the machine stands; it shows where a server says it is. 222.224.192.138:28018 is its address.
Player count
Is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] a busy server?
Of 40 slots on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], 0 are taken at the moment. Averaging 2 players over the last week, it hit a high of 8. Its busiest hour in the last 48 hours was 13:00 UTC, when it averaged 4 players.
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] place in the rankings?
In Asia the player-hours chart puts [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #212; across all ranked servers that is #2,222 and the top 10% over the last seven days.
Join details
How do you get into [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
In Rust, press F1 and enter client.connect 222.224.192.138:28018 in the console. Launch Rust on this page is the other way: it opens the game through Steam and connects you. Head to https://www.ikkunn53.com/rust for its website.