Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO O SRV11,823online PAX72,372playing OCC3,652with players WIPED 3H214
MODModded traffic
Callsign

JPN2201=

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

Online EA 222.224.192.138:28018 checked 6m ago

biweekly wipes moddedoxidepve
Clearance · join
Players now 1/ 40 2% full
7-day average2peak 8
Rank#2,201top 10% · #208 in EA
Last wipe13d agobiweekly schedule
Next wipe1hThu 29 Oct, 14:47 UTC
Track history

Players

AveragePeak
0246814:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Server performance

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.

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 29 October, 14:47 UTC, in 1h.

Its biweekly schedule tag · low confidence

usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak14players, last three wipes
crowd held0%else halves by day 9

Coming wipes

  1. 1hThu 29 Oct, 14:47 UTC
  2. 7d 5hThu 5 Nov, 19:00 UTCFW
  3. 14d 1hThu 12 Nov, 14:47 UTC
  4. 28d 1hThu 26 Nov, 14:47 UTC
  5. 35d 5hThu 3 Dec, 19:00 UTCFW
  6. 42d 1hThu 10 Dec, 14:47 UTC

The first 48 hours of its last wipes

Thu 15 OctFri 2 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:47 UTC13d ago 17 – running 4
Fri 2 Oct, 13:17 UTC27d ago 12 halved by day 7 13.1 days 0
Thu 17 Sep, 14:50 UTC41d ago 14 halved by day 11 14.9 days 2

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 58 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 100/200
  2. 02MOD
    Callsign JPP159EA · groups of 8+ · biweekly · 8 on average [JP][PvE]mameserver初心者おいで!
    Players 9/65
  3. 03MOD
    Callsign JPX377EA · groups of 1000+ · 1x · biweekly · 7 on average JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド
    Players 4/123
  4. 04MOD
    Callsign PVE957EA · groups of 12+ · biweekly · 5 on average [喜相逢] PVE丨仿官原倍丨萌新养老
    Players 5/100
  5. 05MOD
    Callsign RDB017EA · groups of 16+ · biweekly · 4 on average [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎
    Players 4/50
  6. 06MOD
    Callsign PVE085EA · groups of 8+ · biweekly · 3 on average 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老
    Players 3/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] appear in Rust Tracker lists and filters?

On Rust Tracker, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] sits in these lists: PvE servers, tracked live and Modded servers, tracked live. It comes up under these filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

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

The game's server browser reads these tags from [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): Rust survival, standard mode; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): Default team size: 8; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): A wipe every fortnight; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded; EA (East Asia): The server browser lists it under East Asia; rustmaps (Custom tag): The owner or a plugin set it; it is not a standard Rust tag. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

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

A ikkunn53.com hostname is published by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], as it is by 5 other servers we track; same operator, most likely.

Wipe Times

What happens on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] on wipe day?

At their busiest, recent wipes averaged 14 players. 46 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The fall below half came by day 9 where it did not hold.

Which wipe times are confirmed for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The prediction for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] follows its tag, as too few wipes are on record to confirm the schedule. Thursday 29 October at 14:47 UTC is when the next wipe falls due. Its world went live 13 days 22 hours. Its tags carry an every-two-weeks wipe schedule.

Location and Status

What is the uptime on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it online?

Tracking shows [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] online as of now. By its own uptime figure, the last restart was roughly 2 hours ago. 167 of 168 hours up over the last 7 full days: 99% uptime. The first sighting by Rust Tracker was 13 September 2026.

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

Rust network protocol 2635 and build 168909 is the build on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]; the platform is Windows. To join, your game must be on the same protocol; Steam handles the update.

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

Server fps held an average of 56 across the last 48 hours, never below 31. Maximum entities carried: 131,792, from buildings and deployables to everything else. Memory peaked at 3,568 MB. A climbing entity count and low fps are what register as lag for players.

Which location is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] in?

Listed in Asia under EA: that is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] by its own tags. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 222.224.192.138:28018.

Population

What is the player count on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is at 1 players, capacity 40. Peak of 8 in the last seven days, average 2 players. Peak traffic in the last 48 hours came at 13:00 UTC, averaging 4 players.

What rank does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] carry among Rust servers?

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] places #2,201 on seven-day player hours, #208 in Asia and in the top 10% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

No gather rate appears in [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s name. The game's default applies: groups can have up to 8 players. pve is the game mode, fighting between players is off. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Oxide. On: VAC, Valve's anti-cheat.

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

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

Connect

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

Open the console in Rust with F1 after starting the game, then type client.connect 222.224.192.138:28018. Alternatively, Launch Rust here opens Rust via Steam and connects you. The server's website: https://www.ikkunn53.com/rust.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp40
Max players Capacity: 40 slots.
ts8
Group limit Default team size: 8.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed under Modded.

Region

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

Other

rustmaps
Custom tag The owner or a plugin set it; it is not a standard Rust tag.

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.