Rust Data

rustdata.spaceservers222.224.192.138:28028.ipynb

Run all rust-data · live

‹ All servers

Online EA 222.224.192.138:28027 checked 8m ago

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

monthly wipes moddedoxidepve

Connect

srv = rust.server("222.224.192.138:28028")
print(srv.connect_command)

Right now

srv.summary()
players now 1/40 # 2% full
7-day average 1 # peak 6
rank #3,093 # top 14% · #279 in EA
last wipe 23d ago # monthly schedule
next wipe 7d 7h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0123412:0021:0006:0015:0001:0010:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608012:0021:0006:0015:0001:0010: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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

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

usual gap7.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 1

Coming wipes

inatkind
07d 7hThu 5 Nov, 19:00 UTCFW force wipe
135d 7hThu 3 Dec, 19:00 UTCFW force wipe

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 13:53 UTC23d ago 7 NaN running 1
1 Sat 3 Oct, 12:17 UTC25d ago 1 held half 2.1 days 0
2 Sun 20 Sep, 11:27 UTC39d 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.

display(srv.map, srv.info())

Map

4000 · seed 130303
Map of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]
map
Custom Map
size
4000
seed
130303

Server

srv.info()
address
222.224.192.138:28027
region
EA
max players
40
group limit
8, the default
wipe schedule
monthly
last wipe
5 Oct 2026, 13:53 UTC
hostname
game.ikkunn53.com
first seen
17 Sep 2026

Operator · ikkunn53.com

rust.servers(operator="ikkunn53.com").sort_values("players")

About this server · in its own words

print(srv.description)
Japan PvE Server Tokyo This server is currently in a 24-hour run.Please join the Discord server for more information discord discord.gg/6qtWzqrkGX Rules.No attacking or harassing players.Do not spam or overload the server.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱EA · groups of 8+ · monthly · 35 on average42/100
1爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average20/88
2[熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average14/100
3[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average21/100
4【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average12/200
5新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average12/100

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] rank?

Ranked #3,093 on seven-day player hours, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is #279 in Asia and in the top 14% of all ranked servers.

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

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] reports 1 players at this refresh, with 40 slots configured. Over the last seven days it averaged 1 players and peaked at 6. Peak hour in the last 48 hours: 10:00 UTC, mean 2 players.

Server data

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

Averaged over 48 hours: 59 server fps, never under 57. Buildings, deployables and all else in the world took the count as high as 124,425 entities. The memory field tops out at 3,273 MB. Low fps plus an entity count on the way up is the lag players report.

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

The build is Rust network protocol 2635 and build 168909 on Windows, run by [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Joining needs the same protocol on your game; Steam handles the update.

How reliable is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], and is it online now?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] reports itself online at the current refresh. The uptime it reports puts the last restart about 59 minutes ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 17 September 2026.

Which location does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] run from?

The EA tag is what [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] uses to list itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 222.224.192.138:28027 is its address.

Map and rules

Which settings and rules does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] run?

No gather rate appears in the name: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] loaded?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs a procedural map of size 4,000 with seed 130303, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.

Wipes and dates

On what schedule does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipe?

A single wipe each month, the force wipe, is all [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 23 days 21 hours ago, and that is the one in play. The tags list wipes as monthly.

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

Across recent wipes the busiest point averaged 3 players. Peak population on the latest wipe came 46 hours in. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. The drop under half arrived by day 1 in the other cases.

Lists and tags

Where does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] appear among Rust Data lists and filters?

On Rust Data, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] appears in these lists: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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.

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

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

How should you read the server tags on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

These tags are published by [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): East Asia is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

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

Enter client.connect 222.224.192.138:28027 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://www.ikkunn53.com/rust is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players The server lists 40 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Gameplay

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

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EA
East Asia East Asia is its listing in the server browser.

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.

Rust Data 64,357 players 11,757 servers online