Skip to the page
Network live 11,618 servers online 39,799 players aboard 88 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 BP (Tokyo) |Japan PvE [ASIA]

Online EA 222.224.192.138:28027 checked 8m ago

monthly wipes moddedoxidepve
Tracking number · connect
Wipe progress · wiped 23d 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 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 7d 11h · high confidence
0/ 40 players now 0% full
17-day averagepeak 6
#3,084ranktop 14% · #280 in EA
23d agolast wipemonthly schedule
7d 11hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeak
0123408:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Server performance

02040608008:0017:0002:0011:0021:0006: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.

Wipe schedule

force wipes only
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 11h.

The force wipe · high confidence
7.6 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
3wipe-day peakplayers, last three wipes
50%crowd heldelse halves by day 1

Coming wipes

  1. 7d 11hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 35d 11hThu 3 Dec, 19:00 UTC19:00 UKFW

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

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 11h
    Next wipe expected · the force wipe
  2. Mon 5 Oct, 13:53 UTC 14:53 UK · 23d ago
    Wipe delivered
    Peak
    7
    Crowd
    –
    Lasted
    running
    Players before
    1
  3. Sat 3 Oct, 12:17 UTC 13:17 UK · 25d ago
    Wipe delivered
    Peak
    1
    Crowd
    held half
    Lasted
    2.1 days
    Players before
    0
  4. Sun 20 Sep, 11:27 UTC 12:27 UK · 38d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    13 days
    Players before
    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 parcels

Similar servers

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

  1. [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average 37 / 100
  2. 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average 18 / 88
  3. [熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average 12 / 100
  4. [JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average 11 / 100
  5. 【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average 13 / 200
  6. 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average 11 / 100
Help desk

Quick answers

From the figures on this page.

Player activity

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

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

Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] busy at the moment?

Checking now: 0 players on 40 slots at [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Averaged over the past week: 1 players, peaking at 6. Over the last 48 hours, the peak hour came at 06:00 UTC with an average of 2 players.

Map and rules

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

Size 4,000 and seed 130303 define the procedural map [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs, generated by the game. Identical size and seed give an identical map: view it on RustMaps from this page. Its name for the map: Custom Map.

What settings and rules should you know for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

You will not find a gather rate in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. Up to 8 players can join a group, the default for the game. It runs pve, fighting between players is off. Because plugins or settings change the game, it is filed under Modded in the server browser. Oxide supplies the plugins. VAC, Valve's anti-cheat, is switched on.

About the server

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

The EA tag is how [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] lists its location: 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:28027 is its address.

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

The 48-hour average for server fps stands at 59, never dipping below 53. Buildings, deployables and all the rest of the world pushed its entity count as high as 124,425. Memory use peaked at 3,273 MB. Players feel a rising entity count and low fps as lag.

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

Right now, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is online. The uptime it reports puts its last restart at about 8 hours ago. It was up 167 of 168 hours over the last 7 full days, 99% of the time. 17 September 2026 is when Rust Wipe Tracker first recorded it.

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

Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs. The same protocol is required to join, and Steam takes care of updating it.

Wipe schedule

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

The average busiest point of its recent wipes was 3 players. 46 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd stayed over half the peak in 50% of recent cases. By day 1 it had fallen below half where the crowd did not hold.

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

Once a month is all [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipes, along with the force wipe. On Thursday 5 November at 19:00 UTC comes its next wipe, the force wipe that every Rust server shares. 23 days 17 hours have passed since this world was made. A wipe every month is the schedule given in its tags.

Server tags

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

The Rust Wipe Tracker lists that include [JPN] IKKUNN Server BP (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: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly and it appears.

Which person or group runs [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] and 5 other servers we track both publish a ikkunn53.com hostname, which points to the same operator in all likelihood.

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

gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): It holds 40 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): A region code isn't set; ^m (Monthly): One wipe a month, alongside the force wipe; ^p (PvE): There's no player combat; the world itself is the threat; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EA (East Asia): The server browser files it under East Asia are the tags [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

How to join

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

Enter client.connect 222.224.192.138:28027 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. Its website can be found 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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players It holds 40 slots.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code A region code isn't set.

Wipe schedule

^m
Monthly One wipe a month, alongside the force wipe.

Gameplay

^p
PvE There's no player combat; the world itself is the threat.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Region

EA
East Asia The server browser files it 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.