RUST METRICSFlight deck · live data
Data live Servers11,617 Players34,993 Populated2,836 Fresh wipes 3 h74 Scan5 min
‹ All servers222.224.192.138:28027
Online Full Queue Fresh wipe Wipe due No query

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

Online EA 222.224.192.138:28027 checked 11m ago

monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

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

Players now

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

Server fps

48 h low 53 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 121,808 ×1000

Entities

48 h range 101,492–124,425 · memory 2,694 MB
1239 ET SINCE RESTART 07:58

Uptime

7 h 58 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,083top 14% · #280 in EA
Last wipe23d agomonthly schedule
Next wipe7d 12hThu 5 Nov, 19:00 UTC FW
Memory2,694MB48 h peak 3 players
REC 1

Players

AveragePeak
0123407:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608007:0016:0001:0010:0020:0005: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
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.

PLAN

Wipe schedule

force wipes only

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. WPT 1Thu 5 Nov, 19:00 UTC7d 12hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 12hFW

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.

LOG

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

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

The busiest point of its recent wipes drew 3 players on average. Peak crowd on the latest wipe: 46 hours in. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. It fell below half by day 1 when it didn't.

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

Once a month [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 23 days 16 hours ago the current world was made. Its tags carry a monthly wipe schedule.

Lists and filters

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

Tags published by [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): Slots: 40; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; EA (East Asia): The server browser files it under East Asia. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

Most likely the same operator runs them: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes a ikkunn53.com hostname, and so do 5 other servers we track.

Which lists and filters on Rust Metrics show [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

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

Occupancy

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

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

What player count does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] carry?

Current headcount on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: 0 players, 40 slots available. Check: players over seven days. Average 1, peak 6. The last 48 hours peaked at 06:00 UTC, averaging 2 players at that hour.

Server

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

Reading: location. The EA tag puts [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 222.224.192.138:28027.

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

Rust network protocol 2635 and build 168909 on Windows is the build [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: 59 server fps on average across the last 48 hours. It never dropped below 53. Check: entities. The peak was 124,425, counting buildings, deployables and the rest of the world. Reading: 3,273 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] up, and how often does it stay up?

Reading: online. [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] answers right now. Reading: uptime. About 7 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 17 September 2026.

Map and rules

What settings and rules apply on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

Check: gather rate. The name [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] does not state one. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: other players are not fought. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

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

Size 4,000 and seed 130303: the game generates the procedural map on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.

How to join

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

To join: start Rust, press F1 and type client.connect 222.224.192.138:28027. Or press Launch Rust here and Steam opens the game and connects you. https://www.ikkunn53.com/rust is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players Slots: 40.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.