Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO L SRV11,617online PAX32,693playing OCC2,804with players WIPED 3H68
MODModded traffic
Callsign

JPN3083=

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

Online EA 222.224.192.138:28027 checked 9m ago

monthly wipes moddedoxidepve
Clearance · join
Players now 0/ 40 0% full
7-day average1peak 6
Rank#3,083top 14% · #280 in EA
Last wipe23d agomonthly schedule
Next wipe7d 12hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0123407:0016:0001:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

02040608007:0016:0001:0009:0019:0004: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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Flight plan

Wipe schedule

force wipes only
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h.

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

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

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
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 13:53 UTC23d ago 7 – running 1
Sat 3 Oct, 12:17 UTC25d ago 1 held half 2.1 days 0
Sun 20 Sep, 11:27 UTC38d 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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign PVE015EA · groups of 8+ · monthly · 35 on average [坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼
    Players 33/100
  2. 02MOD
    Callsign PVE002EA · groups of 8+ · monthly · 20 on average 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
    Players 18/88
  3. 03MOD
    Callsign PVE016EA · groups of 8+ · monthly · 12 on average [熊猫PVE]修仙升级/召唤/据点/10月新档正式服
    Players 13/100
  4. 04MOD
    Callsign RSI017EA · groups of 8+ · monthly · 11 on average [JP]ちょっぴりHard-PvE RiSu Server
    Players 10/100
  5. 05MOD
    Callsign PVE032EA · groups of 8+ · monthly · 11 on average 【青岩-PVE服】原倍/萌新/突袭据点
    Players 10/200
  6. 06MOD
    Callsign PVE018EA · groups of 16+ · monthly · 10 on average 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简
    Players 12/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

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

These Rust Tracker lists carry [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: PvE servers, tracked live and Modded servers, tracked live. On the server list, these filters bring it up: 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.

What do the tags mean that [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is listed under?

These tags are published by [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] for the game's server browser to read: 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): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset; ^m (Monthly): Follows Facepunch's force wipe: one wipe per month; ^p (PvE): PvE: the world threatens you, not other players; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings; EA (East Asia): Server browser: listed under East Asia. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

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

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

Wipe Times

What should you expect on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] when wipe day lands?

At their busiest, recent wipes averaged 3 players. 46 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. In the other cases, half the peak was lost by day 1.

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

One wipe a month for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: the force wipe. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. Its world went live 23 days 16 hours. Its tags carry a monthly wipe schedule.

Server Details

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

Tracking shows [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] online as of now. About 6 hours ago it restarted last, based on reported uptime. Uptime stood at 99% for the last 7 full days, 167 of 168 hours online. First contact for Rust Tracker: 17 September 2026.

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

Confirmed for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: Rust network protocol 2635 and build 168909, Windows. The same protocol is required to join, and Steam updates it for you.

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

Server fps held an average of 59 across the last 48 hours, never below 53. Maximum entities carried: 124,425, from buildings and deployables to everything else. It drew as much as 3,273 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.

What location is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] hosted in?

The EA tag places [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] in Asia, by its own listing. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 222.224.192.138:28027.

Population

How many players are on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] right now?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is at 0 players, capacity 40. Over seven days: average 1, peak 6 players. At 06:00 UTC it drew its highest average of the last 48 hours: 2 players.

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

Top 14% of all ranked servers and #280 in Asia: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] ranks #3,083 on player hours over the last seven days.

Map and Rules

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

Nothing in [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]'s name states a gather rate. 8 players per group is the game's default, and the cap holds. pve is the game mode, other players cannot be fought. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

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

A procedural map of size 4,000 runs on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], generated by the game from seed 130303. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Custom Map.

How to Join

Which steps join [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

Open the console in Rust with F1 after starting the game, then type client.connect 222.224.192.138:28027. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://www.ikkunn53.com/rust.

Transponder codes

Server tags

What each one means.

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

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 RakNet is the network layer — the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^m
Monthly Follows Facepunch's force wipe: one wipe per month.

Gameplay

^p
PvE PvE: the world threatens you, not other players.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

Region

EA
East Asia Server browser: listed under East Asia.

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.