Skip to the page
RUST ANALYTICS
LIVE98,785PLY11,697SRV
QUOTE 222.224.192.138:28018 Online EA checked 14m ago

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

biweekly wipes moddedoxidepve
Players · last
2/ 40
+124h
5% full
Day range 0 7
7-day avg 2 peak 12
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
2/ 40
5% full
Change · 24h
+1
no reading a day ago
7-day average
2
peak 12
Rank
#2,387
top 11% · #238 in EA
Rank · 7d ago
#2,128
259 places down
Last wipe
4h ago
biweekly schedule
Next wipe
13d 19h
Thu 29 Oct, 14:47 UTC
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
323
player hours, last seven days
Map
4000
Custom Map · seed 130303
First seen
13 Sep 2026
game.ikkunn53.com

Players

AveragePeakWipe
0246819:0004:0013:0023:0008:0017:00Wiped Thu 15 Oct, 14:47 UTCWIPE

Hourly average and peak, UTC. Busiest hour of the two days: 7 players.

Server performance

Server fpsWipe
02040608019:0004:0013:0023:0008:0017:00Wiped Thu 15 Oct, 14:47 UTCWIPE

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.

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

Wipe schedule

from its schedule tag
Next wipeThursday 29 October, 14:47 UTCin 13d 19h

Its biweekly schedule tag · low confidence

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

Coming wipes

  1. 13d 19hThu 29 Oct, 14:47 UTC
  2. 21d 0hThu 5 Nov, 19:00 UTCFW
  3. 27d 19hThu 12 Nov, 14:47 UTC
  4. 41d 19hThu 26 Nov, 14:47 UTC

The first 48 hours of its last wipes

Fri 2 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 12, 39 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:47 UTC4h ago – – running 4
Fri 2 Oct, 13:17 UTC13d ago 12 – – 0
Thu 17 Sep, 14:50 UTC28d 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 14+ · biweekly · 54 on average27/200+6+26.6%
2[喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 7 on average1/100−1−52.0%
3[JP][PvE]mameserver初心者おいで!EA · groups of 8+ · biweekly · 6 on average0/65+0
4[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 3 on average2/50+0+20.0%
5『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average2/100+1
6『蓝天PVE』 原倍 | 仿官 | 突袭 | 萌新 | 养老EA · groups of 8+ · biweekly · 1 on average1/100−1−50.0%

Quick answers

from the figures on this page

Map and Rules

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

No gather rate appears in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The default group size of 8 players applies here. pve is the mode, no combat against other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.

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

Custom map, size 4,000, in use on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: the file is published and downloadable from this page.

Player Count

What is the rank of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

On seven-day player hours, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] sits at #2,387, in the top 11% across ranked servers and #238 in Asia.

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

2 of 40 slots on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are filled right now. The mean over the last seven days is 2 players, reaching 12 at its highest. At 17:00 UTC in the last 48 hours, it averaged 4 players, the busiest hour.

Wipe Frequency

What happens on wipe day at [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The average peak across its recent wipes is 13 players. 39 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The crowd fell below half by day 9 when it did not hold.

How often does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe?

The schedule at [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] cannot be confirmed from the few wipes on record, so the prediction follows its tag. On Thursday 29 October at 14:47 UTC the next wipe is due. This world has been running for 4 hours. The tags show wipes every two weeks.

Server Info

What is the server location for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

In Asia, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself with the EA tag. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 222.224.192.138:28018.

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

Server fps over the last 48 hours: 57 on average, 2 at the lowest. At its peak it held 127,268 entities: buildings, deployables and the rest of the world. Up to 3,759 MB of memory was used. Low fps and growing entities are the source of felt lag.

What Rust version is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] running?

The build is Rust network protocol 2634 and build 166652 on Windows, running on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The protocol has to match for you to join, and Steam applies that update.

What is the uptime and reliability of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Online at this moment: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The reported uptime puts its last restart at about 2 hours ago. 100% is its uptime for the last 7 full days, 168 of 168 hours. First sighting by Rust Analytics: 13 September 2026.

Tags and Rankings

What is the meaning of the tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Published by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp40 (Max players): Slot count: 40; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs166652 (Build): It runs build 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^b (Biweekly): A fortnight between wipes; ^p (PvE): The world is the danger here, not other players; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): This tag is custom, applied by the owner or a plugin rather than by Rust itself. The tags also carry its current players, queue and world creation time; this page shows them at the top.

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

A ikkunn53.com hostname is published by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and by 5 other servers we track, which indicates one operator.

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] appears in which of the lists and filters on Rust Analytics?

These Rust Analytics lists include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers and Best Rust PvE servers. It appears under these filters 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 24 hours.

Connection

What steps do I take to join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The console route: start Rust, press F1, enter client.connect 222.224.192.138:28018. The page's Launch Rust button opens Rust through Steam and connects you instead. You can visit its website at https://www.ikkunn53.com/rust.

Server tags

what each one means

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

Game

gmrust
Game mode Rust's standard survival mode.
mp40
Max players Slot count: 40.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol To join, your game needs protocol 2634.
cs166652
Build It runs build 166652.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code The region code is absent.

Wipe schedule

^b
Biweekly A fortnight between wipes.

Gameplay

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

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

Region

EA
East Asia The server browser files it under East Asia.

Other

rustmaps
Custom tag This tag is custom, applied by the owner or a plugin rather than by Rust itself.

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.