Rust Data

rustdata.spaceservers222.224.192.138:28022.ipynb

Run all rust-data · live

‹ All servers

Online EA 222.224.192.138:28021 checked 10m ago

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

monthly wipes moddedoxidepve

Connect

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

Right now

srv.summary()
players now 1/40 # 2% full
7-day average 3 # peak 13
rank #1,699 # top 8% · #167 in EA
last wipe 26d ago # monthly schedule
next wipe 7d 12h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
02.557.51007:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608007:0016:0001:0010:0020:0005: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
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 8% of all ranked servers, top 30% 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 12h. # The force wipe · high confidence

wipe-day peak32players, last three wipes

Coming wipes

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

The first 48 hours of its last wipes

010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 32, 23 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 13:18 UTC26d ago 32 NaN running 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 C (Tokyo) |Japan PvE [ASIA]
map
Custom Map
size
4000
seed
130303
custom map
download

Server

srv.info()
address
222.224.192.138:28021
region
EA
max players
40
group limit
8, the default
wipe schedule
monthly
last wipe
2 Oct 2026, 13:32 UTC
hostname
game.ikkunn53.com
first seen
13 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 average35/100
1爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average17/88
2[熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average13/100
3[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average10/100
4【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average10/200
5新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average11/100

Quick answers

From the figures on this page.

Population data

How does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] compare in the rankings?

Player hours over the last seven days: #1,699 for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], #167 in Asia, within the top 8% of the ranked set.

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

The sample now reads 1 players for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], out of 40 slots. Over the last seven days it averaged 3 players and peaked at 13. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 5 players.

About the server

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

Averaged over 48 hours: 54 server fps, never under 1. The entity count peaked at 156,721, covering buildings, deployables and the rest of the world. Memory peaked at 3,556 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] on?

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

How reliable is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and is it up?

Online is the state at the latest refresh for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. A restart about 7 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.

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

The EA tag is what [JPN] IKKUNN Server C (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:28021 is its address.

Rules, settings, map

Which rules apply on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and what settings?

The name [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] carries no gather rate. The group limit sits at the default of 8 players. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

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

Map size 4,000, custom, on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. Download the published file from this page.

Wipe schedule

When does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe, and how often?

A single wipe each month, the force wipe, is all [JPN] IKKUNN Server C (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 26 days 16 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.

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

Across recent wipes the busiest point averaged 32 players. Peak population on the latest wipe came 23 hours in.

Tags and filters

Which lists on Rust Data hold [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and which filters?

The Rust Data lists that [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] fits are: Modded Rust servers and 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.

Which operator runs [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

A ikkunn53.com hostname is published by [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and by 5 other servers we track, which suggests the same operator runs them.

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

The game's server browser reads these tags from [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; 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): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Enter client.connect 222.224.192.138:28021 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,rustmaps

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players Slot count: 40.
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 Region code: not set.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

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

Other

rustmaps
Custom tag This tag comes from the owner or a plugin, not from 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.

Rust Data 33,784 players 11,611 servers online