RUST METRICSFlight deck · live data
Data live Servers11,776 Players67,745 Populated3,535 Fresh wipes 3 h197 Scan5 min
‹ All servers222.224.192.138:28018
Online Full Queue Fresh wipe Wipe due No query

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

Online EA 222.224.192.138:28018 checked 12m ago

biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 10 20 30 40 PAX 1 /40

Players now

2% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 57 SERVER FPS

Server fps

48 h low 31 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 131,792 ×1000

Entities

48 h range 97,493–131,792 · memory 2,684 MB
1239 ET SINCE RESTART 01:56

Uptime

1 h 56 min since its last restart, at the last reading
7-day average2peak 8
Rank#2,197top 10% · #208 in EA
Last wipe13d agobiweekly schedule
Next wipe2hThu 29 Oct, 14:47 UTC
Memory2,684MB48 h peak 6 players
REC 1

Players

AveragePeak
0246813:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608013:0022:0007: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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 14:47 UTC, in 2h. 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. WPT 1Thu 29 Oct, 14:47 UTC2h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 6hFW
  3. WPT 3Thu 12 Nov, 14:47 UTC14d 2h
  4. WPT 4Thu 26 Nov, 14:47 UTC28d 2h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 6hFW
  6. WPT 6Thu 10 Dec, 14:47 UTC42d 2h

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:47 UTC13d ago 17 – running 4
Fri 2 Oct, 13:17 UTC26d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

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

At their busiest, its recent wipes drew 14 players on average. After the latest wipe, numbers topped out at 46 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 9 when it didn't.

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

The prediction follows its tag, because too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes are on record to confirm its schedule. Thursday 29 October at 14:47 UTC is when its next wipe is due. The world in play was created 13 days 21 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

Which tags does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] carry, and what do they mean?

These are the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): This tag is non-standard, added by the owner or a plugin. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Check: operator. [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes a ikkunn53.com hostname, and 5 other servers we track do too. Same operator, most likely.

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

Rust Metrics lists featuring [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under 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.

Occupancy

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

Player hours over the last seven days put [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #2,197, #208 in Asia, in the top 10% of all ranked servers.

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

Current headcount on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: 1 players, 40 slots available. Check: players over seven days. Average 2, peak 8. Check: 48-hour peak. 13:00 UTC, 4 players on average.

Server

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

Its EA tag places [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 222.224.192.138:28018.

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

Rust network protocol 2635 and build 168909 on Windows is the build [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Check: fps. Average 56 server fps over the last 48 hours, low of 31. Within range. Check: entities. The peak was 131,792, counting buildings, deployables and the rest of the world. Reading: 3,568 MB of memory at the highest. Expect lag when fps falls and entities climb.

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

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 1 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

How is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] configured, and what rules are in force?

Check: gather rate. The name [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives pve; no combat against other players. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

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

Check: map. A custom one of size 4,000, run by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The published file can be downloaded from this page.

Join

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

Press F1 in Rust and enter client.connect 222.224.192.138:28018. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://www.ikkunn53.com/rust is where its website sits.

PLACARDS

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 The game mode is plain Rust survival.
mp40
Max players The server holds 40 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

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

Other

rustmaps
Custom tag This tag is non-standard, added by 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.