Skip to the page
RUST ANALYTICS
LIVE41,879PLY11,465SRV
QUOTE 222.224.192.138:28027 Online EA checked 14m ago

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

monthly wipes moddedoxidepve
Players · last
0/ 40
−4−100.0%24h
0% full
Day range 0 7
7-day avg 2 peak 8
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 40
0% full
Change · 24h
−4
−100.0% from 4
7-day average
2
peak 8
Rank
#2,229
top 10% · #228 in EA
Rank · 7d ago
#3,895
1666 places up
Last wipe
8d ago
monthly schedule
Next wipe
22d 9h
Thu 5 Nov, 19:00 UTC FW
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
380
player hours, last seven days
Map
4000
Custom Map · seed 130303
First seen
17 Sep 2026
game.ikkunn53.com

Players

AveragePeak
0246810:0019:0004:0013:0022:0007:00

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

Server performance

02040608010:0019:0004:0013:0022:0007: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

force wipes only
Next wipeThursday 5 November, 19:00 UTCin 22d 9h

The force wipe · high confidence

usual gap
7.6 days
between real wipes
on rhythm
0%
of its recent wipes
wipe-day peak
3
players, last three wipes
crowd held
50%
else halves by day 1

Coming wipes

  1. 22d 9hThu 5 Nov, 19:00 UTCFW

The first 48 hours of its last wipes

Mon 5 OctSat 3 OctSun 20 Sep
02468+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 13:53 UTC8d ago 7 – running 1
Sat 3 Oct, 12:17 UTC10d ago 1 held half 2.1 days 0
Sun 20 Sep, 11:27 UTC23d ago 1 halved by day 1 13 days 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 75 on average26/100−54−67.5%
2[坚果PVE]升级/BOSS/副本/任务/种植/堆肥/拍卖EA · groups of 8+ · monthly · 40 on average45/100−12−21.3%
3爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average18/88−6−24.2%
4[JP][PvE]ゆるラス☮YURU RUSTEA · groups of 12+ · monthly · 19 on average15/75+0−2.2%
5[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 16 on average18/100+8+80.0%
6【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 14 on average11/200−8−41.3%

Quick answers

from the figures on this page

Server Rules

How is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] configured in terms of rules and settings?

No gather rate is given in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Up to 8 players per group, which is the game's default. It runs pve, player-versus-player combat is absent. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched on.

Which map is played on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] uses a procedural map of size 4,000 with seed 130303, generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page. The map in use is Custom Map.

Population

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

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

How many players does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] have?

On [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], 0 players are in now, out of 40 slots. The mean over the last seven days is 2 players, reaching 8 at its highest. At 12:00 UTC in the last 48 hours, it averaged 5 players, the busiest hour.

Wipe Cycle

What can you expect on wipe day for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

The average peak across its recent wipes is 3 players. 46 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 50% of its recent wipes. Below half by day 1 is where the crowd fell when it did not hold.

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

A single monthly wipe is what [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs: the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes at that time. 8 days 19 hours ago the current world was created. Its tags list a wipe each month.

Server Info

Where can [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] be found?

In Asia, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] lists itself with the EA tag. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 222.224.192.138:28027.

What is the performance like on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

Server fps over the last 48 hours: 57 on average, 49 at the lowest. At its peak it held 112,799 entities: buildings, deployables and the rest of the world. The memory ceiling reached 3,328 MB. What players feel as lag is low fps together with a rising entity count.

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs which version of Rust?

The build is Rust network protocol 2634 and build 166652 on Windows, running on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Your game needs the same protocol to get in; Steam takes care of the update.

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

Online at this moment: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. 10 hours ago is when it last restarted, judging by the uptime it reports. 100% is its uptime for the last 7 full days, 168 of 168 hours. The earliest Rust Analytics saw it was 17 September 2026.

Tags & Filters

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

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166652 (Build): It runs build 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^m (Monthly): A single wipe each month, alongside Facepunch's force wipe; ^p (PvE): No fighting between players: the world is the threat; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play; EA (East Asia): East Asia is its browser listing, which [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes. The top of this page and the tags both show its players now, its queue and when its world was made.

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

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

On Rust Analytics, which lists and filters feature [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

The following Rust Analytics lists feature [JPN] IKKUNN Server BP (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: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.

Connection

What is the process to join [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

The console route: start Rust, press F1, enter client.connect 222.224.192.138:28027. 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,^m,EA,^p,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp40
Max players Capacity: 40 slots.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol Protocol 2634: matching game versions are required to join.
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

^m
Monthly A single wipe each month, alongside Facepunch's force wipe.

Gameplay

^p
PvE No fighting between players: the world is the threat.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded The Modded listing applies: plugins or settings change play.

Region

EA
East Asia East Asia is its browser listing.

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.