StatusLive Servers online11,908 Players102,404 Populated3,970 Wiped · 3 h409 Interval5 min Date29 OCT 2026

DWG RG-S2228Server sheetchecked 10m ago

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

Online EA 222.224.192.138:28018 checked 10m ago

biweekly wipes moddedoxidepve
Connect
Players now 0/ 40 0% full
7-day average2peak 8
Rank#2,228top 10% · #212 in EA
Last wipe14d agobiweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0246818:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Fig. 1Players on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Fig. 2

Server performance

02040608018:0003:0012:0022:0007:0016: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. The force wipe · high 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. 7d 1hThu 5 Nov, 19:00 UTCFW
  2. 13d 20hThu 12 Nov, 14:47 UTC
  3. 27d 20hThu 26 Nov, 14:47 UTC
  4. 35d 1hThu 3 Dec, 19:00 UTCFW
  5. 41d 20hThu 10 Dec, 14:47 UTC

The first 48 hours of its last wipes

Thu 15 OctFri 2 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:47 UTC14d 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 UTC42d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 59 on average
43 / 200
02
[JP][PvE]mameserver初心者おいで!EA · groups of 8+ · biweekly · 7 on average
1 / 65
03
JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイドEA · groups of 1000+ · 1x · biweekly · 7 on average
2 / 69
04
[喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 5 on average
3 / 100
05
[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 4 on average
1 / 50
06
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average
0 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

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

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is up at this moment. Counted from its reported uptime, the last restart was about 6 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] show?

The last 48 hours give an average of 56 server fps and a floor of 31. Counted at its highest: 131,792 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,568 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

With its EA tag, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 222.224.192.138:28018.

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

On Windows, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Player data

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

Current player count on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: 0, of 40 slots. Averaged across seven days, the player count is 2, with a peak of 8. Over the last 48 hours the busiest hour was 13:00 UTC, at an average of 4 players.

Against other Rust servers, where is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] placed?

Across seven days, player hours give [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] #2,228 globally and #212 in Asia, a top 10% position among ranked servers.

Wipe times

On [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], what does the data show for wipe day?

At their busiest, its recent wipes drew 14 players on average. At 46 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 9.

What wipe schedule has been recorded for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 14 days 3 hours ago the current world was made. Its tags give a wipe schedule of one wipe every two weeks.

Settings

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

No gather rate is stated in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. Eight players per group: the default for the game. pve, no fighting other players, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.

Which map has [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] loaded?

Custom map at size 4,000 on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], with the file published for download from this page.

Tags

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

On Rust Graphs, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is placed in these lists: Modded Rust servers and PvE Rust servers, plotted. It is returned by these filters on the server list: 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.

Which meaning is attached to each tag on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): Slots: 40; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): Player fights are off; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EA (East Asia): The server browser lists it under East Asia; rustmaps (Custom tag): A non-standard tag, set by the owner or a plugin are the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

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

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes a ikkunn53.com hostname. 5 other servers we track publish one too, so the same operator most likely runs them.

Joining the server

By what method do you join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Enter client.connect 222.224.192.138:28018 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://www.ikkunn53.com/rust is its website.

NotesAnswered from the figures
Key

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 Standard survival, as Rust plays.
mp40
Max players Slots: 40.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Gameplay

^p
PvE Player fights are off; the world supplies the danger.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Region

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

Other

rustmaps
Custom tag A non-standard tag, set 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.

KeyTag string decoded