Rust Server Analytics 54,249 players11,692 servers
All servers
Drill-through Server detail

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

Online EA 222.224.192.138:28024 checked 13m ago

Drill-through
FilterServeris [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]
Attributes
monthly wipes moddedoxidepve
Last refreshed
Players now 2/ 40
7-day average 2 peak 12
Rank #2,172 top 10% · #205 in EA
Last wipe 27d ago monthly schedule
Next wipe 6d 17h Thu 5 Nov, 19:00 UTC FW
Capacity 5% full

Players

average and peak, with its wipes marked
AveragePeak
0510152002:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
02040608002:0011:0021:0006:0015:0000: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
11k2k3k4k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Wipe schedule

force wipes only

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

wipe-day peak15players, last three wipes

Coming wipes

InWhen, UTCKind
6d 17hThu 5 Nov, 19:00 UTCFW force wipe
34d 17hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 15, 18 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:18 UTC27d ago 15 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 34 on average 30 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average 17 / 88
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服 EA · groups of 8+ · monthly · 12 on average 13 / 100
[JP]ちょっぴりHard-PvE RiSu Server EA · groups of 8+ · monthly · 11 on average 12 / 100
【青岩-PVE服】原倍/萌新/突袭据点 EA · groups of 8+ · monthly · 11 on average 7 / 200
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 EA · groups of 16+ · monthly · 10 on average 11 / 100

Quick answers

from the figures on this page

Wipe data

When does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] wipe?

The force wipe is the only wipe for [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 27 days 11 hours ago the current world was made. The tags carry a monthly wipe schedule.

On [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], what happens on wipe day?

Across recent wipes the busiest point averaged 15 players. 18 hours after the latest wipe the crowd peaked.

Server

Which location hosts [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?

Its EA tag puts [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] in Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 222.224.192.138:28024.

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

Rust network protocol 2635 and build 168909 on Windows is the setup for [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]. The protocol has to match before you can join; Steam updates it automatically.

Is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] up, and how steady is its uptime?

[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] reports online at the current check. Its reported uptime indicates a restart roughly 3 hours ago. 99% uptime over the last 7 full days, equal to 167 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.

Is performance on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] stable?

The 48-hour average was 57 server fps; the low was 39. At its highest the entity count was 117,209, including buildings, deployables and all else. At its highest, memory use was 3,220 MB. A climbing entity count and low fps are the lag players perceive.

Tags

How should the tags on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] be read?

The game's server browser reads the tags [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] publishes: gmrust (Game mode): Rust survival, standard ruleset; mp40 (Max players): Player slots: 40; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^p (PvE): Player combat is off; the world supplies the danger; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): Outside the standard tag set, added by the owner or a plugin. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

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

These Rust Server Analytics lists include [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: 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 D (Tokyo) |Japan PvE [ASIA]?

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

Population

Where does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] sit among Rust servers?

For player hours over the last seven days, [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] places #2,172 globally and #205 in Asia, in the top 10% of all ranked servers.

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

[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] holds 2 players of its 40 slots as of the latest update. The seven-day mean is 2 players, against a peak of 12. Across the last 48 hours, 14:00 UTC shows the highest average: 11 players.

Settings

What settings and rules does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] use?

The name of [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] does not state a gather rate. The default group cap of 8 players applies. pve is the game mode, no fighting other players. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.

The map on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: which one is it?

A custom map of size 4,000 is used on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]; its file is published and downloadable here.

Connection

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

In the Rust console (F1), enter client.connect 222.224.192.138:28024. Launch Rust on this page also works, opening Rust through Steam and connecting you. Find it online at https://www.ikkunn53.com/rust.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard ruleset.
mp40
Max players Player slots: 40.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Build number 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Wipe schedule

^m
Monthly A monthly cycle, with Facepunch's force wipe as the reset.

Gameplay

^p
PvE Player combat is off; the world supplies the danger.

Mods and access

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

Region

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

Other

rustmaps
Custom tag Outside the standard tag set, added by the owner or a plugin.

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.