RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOnline

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

EA 222.224.192.138:28018 checked 10m ago

biweekly wipes moddedoxidepve
Deploy
Zerg meter8%light
3/40 troops
7-day average2
peak 12
Rank#2,424
top 11% · #241 in EA
Last wipe12d ago
biweekly schedule
Next wipe · H-hour1d 5h
Fri 16 Oct, 13:17 UTC

Players

AveragePeak
0246809:0018:0003:0012:0021:0006:00

Hourly average and peak, UTC.

Server performance

02040608009:0018:0003:0012: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
11k2k3k4k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

Wipe schedule

from its schedule tag

Next wipe Friday 16 October, 13:17 UTC, in 1d 5h. Its biweekly schedule tag · low confidence

usual gap14.9 days
between real wipes
wipe-day peak13
players, last three wipes
crowd held0%
else halves by day 11

Coming wipes

1d 5hFri 16 Oct, 13:17 UTC
15d 5hFri 30 Oct, 13:17 UTC
21d 10hThu 5 Nov, 19:00 UTCFW
29d 5hFri 13 Nov, 13:17 UTC
43d 5hFri 27 Nov, 13:17 UTC

The first 48 hours of its last wipes

Fri 2 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 12, 39 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:17 UTC12d ago 12 – running 0
Thu 17 Sep, 14:50 UTC27d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Zergmax 14
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 14+ · biweekly · 53 on average
50/200
Zergmax 12
[喜相逢] PVE丨仿官原倍丨萌新养老 EA · groups of 12+ · biweekly · 8 on average
3/100
No limit8 · game default
[JP][PvE]mameserver初心者おいで! EA · groups of 8+ · biweekly · 6 on average
2/65
Zergmax 16
[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 EA · groups of 16+ · biweekly · 3 on average
2/50
No limit8 · game default
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 EA · groups of 8+ · biweekly · 3 on average
7/100
No limit8 · game default
『蓝天PVE』 原倍 | 仿官 | 突袭 | 萌新 | 养老 EA · groups of 8+ · biweekly · 1 on average
1/100

Quick answers

from the figures on this page

Rules and settings

What is the setup on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] when it comes to rules and settings?

There is no gather rate in the name [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. That is the game's default: groups of up to 8 players. It runs pve, other players cannot be fought. This one sits under Modded in the browser: the game is changed by plugins or settings. It runs plugins: Oxide. VAC is on, Valve's anti-cheat.

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

Size 4,000, custom map: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes the map file, downloadable from this page.

Server population

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

[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] has 3 of its 40 slots filled right now. The seven-day average is 2 players, with a peak of 12. The busiest time in the last 48 hours was 12:00 UTC, when it averaged 6 players.

What position does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold in the server rankings?

For player hours in the last week, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] ranks #2,424 overall and #241 in Asia, placing it in the top 11% of ranked servers.

Tags and filters

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

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

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

The game's server browser reads these tags from [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): Survival in the standard Rust mode; mp40 (Max players): It holds 40 players; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks the server wipes; ^p (PvE): No player-versus-player combat; the environment is the threat; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded category: the game is altered by plugins or settings; EA (East Asia): East Asia is the category it falls under in the server browser; rustmaps (Custom tag): The owner or a plugin set this tag; it's not part of standard Rust. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.

Which Rust Zerg Life filters and lists cover [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

The Rust Zerg Life lists that include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are Modded Rust servers for clans and zergs and Best Rust PvE servers. Under these filters it shows 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; Last wipe: In the last 2 weeks.

Server details

Is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] currently online and stable?

You can join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] now: it is online. Based on the uptime it reports, the last restart was about 9 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Its first appearance in Rust Zerg Life records is 13 September 2026.

Is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] smooth to play on?

Server fps held an average of 58 for the last 48 hours, with a minimum of 2. The world held as many as 127,268 entities, including buildings, deployables and everything else. The maximum memory it used was 3,860 MB. A climbing entity count and low fps are the source of the lag players feel.

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

On Windows, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2634 and build 166652. Joining requires your game to be on the same protocol, which Steam updates automatically.

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

With its EA tag, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Rust Zerg Life displays the location a server claims, not where the machine actually stands. You can reach it at 222.224.192.138:28018.

Wipe days

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

The average peak for its recent wipes was 13 players. 39 hours after the latest wipe, the crowd peaked. The crowd kept above half that peak until the next wipe in 0% of its recent wipes. If not, the crowd fell below half by day 11.

How often does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe, and on what days?

Its tag guides the prediction, as [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipe record is too sparse to confirm the schedule. On Friday 16 October at 13:17 UTC its next wipe is expected. 12 days 18 hours ago is when its present world was created. The tags hold a fortnightly wipe schedule.

Join the server

What is the process to join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Enter client.connect 222.224.192.138:28018 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you. You can find its website at https://www.ikkunn53.com/rust.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust mode.
mp40
Max players It holds 40 players.
ts8
Group limit Teams max out at 8—the default setting for Rust.
v2634
Protocol Protocol 2634—only players on that version can get in.
cs166652
Build The game build is 166652.
ptrak
Networking The network layer is RakNet, which is standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Gameplay

^p
PvE No player-versus-player combat; the environment is the threat.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Modded category: the game is altered by plugins or settings.

Region

EA
East Asia East Asia is the category it falls under in the server browser.

Other

rustmaps
Custom tag The owner or a plugin set this tag; it's not part of standard Rust.

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.