Rust Data LabData lab · live
Live readings Servers11,841 Players73,926 Populated3,704 Fresh wipes · 3h221 Sampled every 5 min

Element card · group PvE · atomic number 1,713, its rank

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

Online EA 222.224.192.138:28021 checked 11m ago

monthly wipes moddedoxidepve
Join the experiment
Atomic mass · players now 6/ 40 15% full Room to join
7-day average3peak 13
Rank · atomic number#1,713top 8% · #168 in EA
Last wipe27d agomonthly schedule
Next wipe7d 5hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0246814:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608014:0023:0008:0017:0003:0012: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Reaction kinetics

Wipe schedule

force wipes only

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

wipe-day peak32players, last three wipes

Coming wipes

  1. 7d 5hThu 5 Nov, 19:00 UTCFW
  2. 35d 5hThu 3 Dec, 19:00 UTCFW

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:18 UTC27d ago 32 – 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
  1. 1 宗门 [坚果PVE]宗门师徒/每日… 38
    [坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 EA · groups of 8+ · monthly · 35 on average 38/ 100
  2. 2 爱酱 爱酱PVE|1服|十倍|死亡… 21
    爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average 21/ 88
  3. 3 修仙 [熊猫PVE]修仙升级/召唤… 15
    [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 EA · groups of 8+ · monthly · 12 on average 15/ 100
  4. 4 ちょ [JP]ちょっぴりHard-… 20
    [JP]ちょっぴりHard-PvE RiSu Server EA · groups of 8+ · monthly · 11 on average 20/ 100
  5. 5 原倍 【青岩-PVE服】原倍/萌新… 20
    【青岩-PVE服】原倍/萌新/突袭据点 EA · groups of 8+ · monthly · 11 on average 20/ 200
  6. 6 新问 新问仙PVE/死亡不掉/萌新… 13
    新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 EA · groups of 16+ · monthly · 10 on average 13/ 100

Quick answers

from the figures on this page

Settings and map

What map is in play on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Custom map on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], size 4,000: the map file is published, so this page offers it for download.

What rules has [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] set, and what settings are in force?

Nothing in the name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] gives a gather rate. With no change from the default, groups can hold up to 8 players. Play runs as pve, other players cannot be fought. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running on it. Anti-cheat is on: Valve's VAC.

Server facts

In what location does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit?

The EA tag is how [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] lists itself, in Asia. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 222.224.192.138:28021 is the address it uses.

What Rust version does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] currently run?

On Windows, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] stay online?

[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is live as of now. According to the uptime it reports, the last restart was about 2 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

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

The last 48 hours show an average of 55 server fps and a minimum of 2. The entity count reached 156,405, including buildings, deployables and all other world items. The highest memory usage was 3,556 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipes and resets

How often does a wipe happen on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and at what time?

Once a month is all [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes, with the force wipe. The next time this server wipes will be the force wipe on Thursday 5 November at 19:00 UTC, which wipes every Rust server. 27 days ago the current world was made. Wipes monthly, according to the schedule in its tags.

What does a typical wipe day on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] involve?

Averaged across its recent wipes, the busiest point drew 32 players. 23 hours after the latest wipe, the crowd peaked.

Tags, lists

Which meanings sit behind the tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

The game's server browser reads the tags [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Player slots: 40; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): No region code is set; ^m (Monthly): Wipes happen monthly, at the force wipe; ^p (PvE): The threat comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded; EA (East Asia): In the browser it sits under East Asia; rustmaps (Custom tag): A plugin or the owner set this tag; it is not standard Rust. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] come up?

These themed Rust Data Lab lists carry [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, measured and Best Rust PvE servers, measured live. These filters bring it up 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.

Whose server is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Sharing its ikkunn53.com hostname with 5 other servers we track, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is most likely run by the same operator as those.

Player numbers

What position does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] hold among Rust servers?

Player hours for the past seven days give [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] #1,713, #168 in Asia, and a place in the top 8% of ranked servers.

What does the current player count on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] tell you?

At the moment [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] has 6 of its 40 slots filled. A seven-day sample gives 3 players on average and 13 at the top. Peak time in the past 48 hours: 12:00 UTC, when the average was 6 players.

Getting on

How can you connect to [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Open the console with F1 in Rust and type client.connect 222.224.192.138:28021. The Launch Rust button on this page does the same job through Steam. You can find its website 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 Survival in the standard Rust style.
mp40
Max players Player slots: 40.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Wipes happen monthly, at the force wipe.

Gameplay

^p
PvE The threat comes from the world, not from other players.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under Modded.

Region

EA
East Asia In the browser it sits under East Asia.

Other

rustmaps
Custom tag A plugin or the owner set this tag; it is not standard Rust.

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.