Rust HeatmapInfrared · players
IR live Players93,847 Servers11,851 Warm3,878 Fresh wipes · 3h391 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–40° · slots

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]

Online EA 222.224.192.138:28018 checked 9m ago

biweekly wipes moddedoxidepve
Sp1 · players now 0/ 40
0% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 6°
Tue 16:00flare: a wipe in that hourThu 14:00
2
7-day average
peak 8
#2,217
rank
top 10% · #210 in EA
14d ago
last wipe
biweekly schedule
7d 3h
next wipe
Thu 5 Nov, 19:00 UTC FW
UTC checked 9m ago

Li2Players

AveragePeak
0246816:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Li3Server performance

02040608016:0001:0010:0020:0005:0014:00

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.

Li4Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.

Bx1Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

14 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
14
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 9

Coming wipes

7d 3h
Thu 5 Nov, 19:00 UTC
FW
13d 23h
Thu 12 Nov, 14:47 UTC
27d 23h
Thu 26 Nov, 14:47 UTC
35d 3h
Thu 3 Dec, 19:00 UTC
FW
41d 23h
Thu 10 Dec, 14:47 UTC

The first 48 hours of its last wipes

Thu 15 OctFri 2 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能
EA · groups of 16+ · biweekly · 58 on average
77 / 200
[JP][PvE]mameserver初心者おいで!
EA · groups of 8+ · biweekly · 8 on average
6 / 65
JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド
EA · groups of 1000+ · 1x · biweekly · 7 on average
4 / 123
[喜相逢] PVE丨仿官原倍丨萌新养老
EA · groups of 12+ · biweekly · 5 on average
7 / 100
[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎
EA · groups of 16+ · biweekly · 4 on average
1 / 50
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老
EA · groups of 8+ · biweekly · 3 on average
1 / 100

LogQuick answers

from the figures on this page

Wipe schedule

What does wipe day look like on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

At their busiest, its recent wipes averaged 14 players. 46 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 9 it was below half in the wipes that did not hold.

What is the wipe schedule on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Too few wipes are recorded on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] to confirm its schedule; the tag is what the prediction follows. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, when all Rust servers wipe. The world in play now was made 14 days ago. A fortnightly wipe is listed in the tags.

Population

How busy is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The current population of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is 0, against 40 slots. Averaged over the past week: 2 players, peaking at 8. Its busiest point in the last 48 hours was 13:00 UTC, averaging 4 players.

How does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?

Seven-day player hours place [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #2,217, in the top 10% of ranked servers; within Asia it is #210.

Settings and rules

Which map does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?

The custom map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] has size 4,000, and its file is published for download from this page.

What are the rules and settings on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The name [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] does not specify a gather rate. 8 players is the default group size, and that is the limit here. pve is the game mode, player combat is disabled. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins are in use. VAC is on, which is Valve's anti-cheat.

Location and uptime

Which version of Rust does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?

Rust network protocol 2635 and build 168909 is the build [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs, on Windows. Steam updates your game for you, and the protocol has to match for you to join.

Is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] online, and how reliable is it?

The server is up at the moment: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is online. Its reported uptime dates the last restart to about 4 hours ago. 167 of 168 hours up over the last 7 full days, which is 99%. Rust Heatmap has had it on record since 13 September 2026.

Where is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] located?

With its EA tag, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself in Asia. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 222.224.192.138:28018 is its address.

Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run smoothly?

It averaged 56 server fps over the last 48 hours, with a low of 31. Entities peaked at 131,792, counting buildings, deployables and all the rest of the world. The highest memory use was 3,568 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Tags

Which Rust Heatmap lists and filters include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

These Rust Heatmap lists include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, by live population and Best Rust PvE servers. These are the filters that return it on the 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.

What do the server tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] mean?

gmrust (Game mode): Survival in the standard Rust form; mp40 (Max players): Slot count: 40; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): This build is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^b (Biweekly): It wipes on a two-week cycle; ^p (PvE): PvE: the danger is the world, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; EA (East Asia): East Asia is where the server browser puts it; rustmaps (Custom tag): This is not a standard Rust tag: a plugin or the owner set it are the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Who runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

One operator most likely runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and the 5 other servers we track that publish a ikkunn53.com hostname.

Connect

How do I join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Press F1 in Rust to open the console, then enter client.connect 222.224.192.138:28018. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you. You can find it online at https://www.ikkunn53.com/rust.

KeyServer tags

what each one means

Published as mp40,ptrak,$r?,v2635,^b,EA,^p,gmrust,cs168909,ts8,^o^z,rustmaps

Game

gmrust
Game mode Survival in the standard Rust form.
mp40
Max players Slot count: 40.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol Your game must match protocol 2635 to get in.
cs168909
Build This build is 168909.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code The region code is blank.

Wipe schedule

^b
Biweekly It wipes on a two-week cycle.

Gameplay

^p
PvE PvE: the danger is the world, not other players.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The game is changed by settings or plugins, so it sits under Modded.

Region

EA
East Asia East Asia is where the server browser puts it.

Other

rustmaps
Custom tag This is not a standard Rust tag: a plugin or the owner set it.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.