At press time 11,841 servers73,926 players221 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 2,201

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

Online EA 222.224.192.138:28018 checked 7m ago

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is a Rust server in Asia, one of the ikkunn53.com servers. At the last count it had 0 players of a possible 40; over the past week it averaged 2, with a peak of 8. It stands at No. 2,201 of the ranked servers, the top 10%, and No. 208 in Asia. It last wiped 13d ago, on a biweekly schedule, and the next wipe is expected on Thursday 29 October. Its own tags class it as modded, oxide, pve.

§ 1Attendance

AveragePeak
0246814:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

§ 2Performance

02040608014:0023:0008:0017:0003:0012: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.

§ 3Standingthe 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.

§ 4The wipe schedulefrom its schedule tag

Next wipe Thursday 29 October, 14:47 UTC, in 1h. Its biweekly schedule tag · low confidence

The rhythm
Usual gap14 days

between real wipes

On rhythm100%

of its recent wipes

Wipe-day peak14

players, last three wipes

Crowd held0%

else halves by day 9

Coming wipes
Date, UTCHence
Thu 29 Oct, 14:471h
Thu 5 Nov, 19:00 FW7d 5h
Thu 12 Nov, 14:4714d 1h
Thu 26 Nov, 14:4728d 1h
Thu 3 Dec, 19:00 FW35d 5h
Thu 10 Dec, 14:4742d 1h

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.

§ 5The record of wipesnewest first

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

§ 6In its own wordsas the server describes itself

Japan PvE Server Tokyo This server is currently in a 24-hour run.Please join the Discord server for more information discord discord.gg/6qtWzqrkGX Rules.No attacking or harassing players.Do not spam or overload the server.

§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes

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

§ 8Questions answeredfrom the figures in this entry

The record

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

Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs. To join, your game must be on the same protocol; Steam handles the update.

What does uptime look like on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it up?

The records show [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] online at the time of this check. The uptime it reports puts the last restart at about 2 hours ago. Of note: 167 of 168 hours up in the last 7 full days, or 99% of the time. Rust Server Stats records a first sighting on 13 September 2026.

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

The records show an average of 56 server fps over 48 hours, never below 31. The entity count reached 131,792: buildings, deployables and all else in the world. The memory peak was 3,568 MB. What players feel as lag: fps running low and entities climbing.

Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] operate from?

The EA tag places [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] in Asia, as the server lists itself. Rust Server Stats records the stated location of a server, not the location of the machine. 222.224.192.138:28018 — that is the address.

Settings and map

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

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs a custom map of size 4,000. Its map file is published, so it can be downloaded from this page.

What does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] set down in the way of rules and settings?

Nothing in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] gives a gather rate. Groups are capped at 8 players, the standard default. pve is the game mode, no combat against other players. It sits in the Modded section, with plugins or settings that change play. The plugin set is Oxide. VAC is enabled: Valve's anti-cheat.

Player record

What population does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] carry?

The record for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] shows 0 players, against a capacity of 40. The seven-day record: an average of 2 players and a peak of 8. At 13:00 UTC, over the last 48 hours, the mean was 4 players, the highest of any hour.

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

For seven-day player hours [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is #2,201 overall and #208 in Asia, in the top 10% of ranked servers.

Tags, lists

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] sits in which Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers and Rust PvE servers. On the server list it comes up under these filters: 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.

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

The game's server browser reads the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes: gmrust (Game mode): The standard survival game; mp40 (Max players): 40 is the number of slots; ts8 (Group limit): 8 to a team, which is the default; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): Region code absent; ^b (Biweekly): A wipe comes once a fortnight; ^p (PvE): Player against player combat is off; the world supplies the danger; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Modded: settings or plugins have changed the game; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): Not a standard Rust tag. A plugin or the owner is responsible. The tags include current players, queue and the time the world was made; the top of this page shows them.

Which operator stands behind [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The ikkunn53.com hostname of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is also published by 5 other servers we track; most likely the same operator runs them.

Wipe record

What is the shape of wipe day on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Across its recent wipes, the busiest point averaged 14 players. 46 hours into the latest wipe the crowd reached its peak. Above half that peak until the next wipe: the crowd held in 0% of recent wipes. By day 9, in the wipes that did not, the crowd fell below half.

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

Too few wipes of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are on record to confirm the schedule; the tag guides the prediction. Thursday 29 October at 14:47 UTC is when the next wipe is due. The present world dates from 13 days 22 hours. Its tags set out a fortnightly wipe schedule.

Connection

How does one connect to [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

To connect, open the console with F1 in Rust and enter client.connect 222.224.192.138:28018. The Launch Rust and join button on this page does the same through Steam. https://www.ikkunn53.com/rust carries the server's website.

§ 9Key to the tagswhat each one means

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

Game

gmrust
Game mode The standard survival game.
mp40
Max players 40 is the number of slots.
ts8
Group limit 8 to a team, which is the default.
v2635
Protocol Join only on protocol 2635; other versions cannot connect.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code Region code absent.

Wipe schedule

^b
Biweekly A wipe comes once a fortnight.

Gameplay

^p
PvE Player against player combat is off; the world supplies the danger.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Modded: settings or plugins have changed the game.

Region

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

Other

rustmaps
Custom tag Not a standard Rust tag. A plugin or the owner is responsible.

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.