Skip to the page
Network live 11,814 servers online 72,000 players aboard 206 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online EA 222.224.192.138:28018 checked 7m ago

biweekly wipes moddedoxidepve
Tracking number · connect
Launch Rust and join Website
Wipe progress · wiped 13d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 29 Oct, 14:47 UK Thu 29 Oct, 14:47 UTC in 1h · low confidence
1/ 40 players now 2% full
27-day averagepeak 8
#2,201ranktop 10% · #208 in EA
13d agolast wipebiweekly schedule
1hnext wipeThu 29 Oct, 14:47 UTC
Delivery history

Players, performance and rank

Players

AveragePeak
0246814:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Server performance

02040608014:0023:0008:0016:0002:0011: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.

Wipe schedule

from its schedule tag
Next delivery expected

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

Its biweekly schedule tag · low confidence
14 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
14wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 9

Coming wipes

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

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

every wipe as a delivery, newest first
  1. Thu 29 Oct, 14:47 UTC14:47 UK · in 1h
    Next wipe expected · its biweekly schedule tag
  2. Thu 15 Oct, 14:47 UTC 15:47 UK · 13d ago
    Wipe delivered
    Peak
    17
    Crowd
    –
    Lasted
    running
    Players before
    4
  3. Fri 2 Oct, 13:17 UTC 14:17 UK · 27d ago
    Wipe delivered
    Peak
    12
    Crowd
    halved by day 7
    Lasted
    13.1 days
    Players before
    0
  4. Thu 17 Sep, 14:50 UTC 15:50 UK · 41d ago
    Wipe delivered
    Peak
    14
    Crowd
    halved by day 11
    Lasted
    14.9 days
    Players before
    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.

Similar parcels

Similar servers

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

  1. 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能EA · groups of 16+ · biweekly · 58 on average 102 / 200
  2. [JP][PvE]mameserver初心者おいで！EA · groups of 8+ · biweekly · 8 on average 9 / 65
  3. JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイドEA · groups of 1000+ · 1x · biweekly · 7 on average 4 / 123
  4. [喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 5 on average 5 / 100
  5. [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 4 on average 4 / 50
  6. 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average 4 / 100
Help desk

Quick answers

From the figures on this page.

Player activity

What is the ranking of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] against other Rust servers?

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

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

Checking now: 1 players on 40 slots at [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. Averaged over the past week: 2 players, peaking at 8. The busiest hour over the last 48 hours was 13:00 UTC, averaging 4 players.

Rules and settings

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

The custom map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is size 4,000. You can download its published map file from this page.

What are the rules on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and what settings does it run?

You will not find a gather rate in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. 8 players is the group limit, since the game's default applies. You get pve here, fighting between players is off. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. The VAC anti-cheat from Valve is enabled.

Server details

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

With its EA tag, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] places itself in Asia. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 222.224.192.138:28018 is its address.

Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] perform well?

Averaged over the last 48 hours, server fps was 56, with a low of 31. The world held as many as 131,792 entities: buildings, deployables and the rest. The highest memory reading was 3,568 MB. Players feel a rising entity count and low fps as lag.

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

You can find [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] online at present. Its reported uptime suggests a restart roughly 1 hours ago. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. It was first seen by Rust Wipe Tracker on 13 September 2026.

On what Rust version does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] operate?

On Windows, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. Steam keeps your game updated; it has to be on the same protocol to join.

Map resets

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

The average busiest point of its recent wipes was 14 players. 46 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd stayed over half the peak in 0% of recent cases. Where that did not hold, it dropped below half by day 9.

When does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe? What schedule does it follow?

The prediction follows its tag, because too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes are on record to confirm the schedule. Thursday 29 October at 14:47 UTC is when its next wipe is due. 13 days 22 hours have passed since this world was made. Its tags give the wipe schedule as every two weeks.

Server tags

On Rust Wipe Tracker, which lists and filters is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] part of?

The Rust Wipe Tracker lists that include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are: Modded Rust servers and Best Rust PvE servers. On the server list, apply 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 and it appears.

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

One operator most likely runs these: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes a ikkunn53.com hostname, as do 5 other servers we track.

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

Read off the game's server browser, the tags for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): A region code isn't set; ^b (Biweekly): A wipe comes every fortnight; ^p (PvE): The world provides the danger, not other players; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EA (East Asia): Server browser category: East Asia; rustmaps (Custom tag): This isn't a standard Rust tag; it comes from the owner or a plugin. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Getting started

What steps do you take to join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Enter client.connect 222.224.192.138:28018 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. https://www.ikkunn53.com/rust is its website.

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 Survival in standard Rust.
mp40
Max players Slot count: 40.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code A region code isn't set.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Gameplay

^p
PvE The world provides the danger, not other players.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Region

EA
East Asia Server browser category: East Asia.

Other

rustmaps
Custom tag This isn't a standard Rust tag; it comes from 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.