1UP
11659servers on
Hi-score
48364players now
2UP
117fresh wipes · 3h
Player select Ready

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

Online EA 222.224.192.138:28027 checked 11m ago

monthly wipes moddedoxidepve

Stats

Players
0/ 40
0% full
Slots
40open
40 max players
7-day avg
1
7-day average · peak 6
FPS
60
server frames a second, the latest hour; the bar fills at 60
Uptime
9h 58m
since its last restart; the bar fills at a day
Rank
#3,083
top 14% · #280 in EA
Last wipe · new game
23d ago
monthly schedule
Next wipe · continue?
7d 9h
Thu 5 Nov, 19:00 UTC FW

Players

AveragePeak
0123410:0019:0004:0012:0022:0007:00

Hourly average and peak, UTC.

Server performance

02040608010:0019:0004:0012:0022:0007: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
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.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence

7.6 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
3
wipe-day peak
players, last three wipes
50%
crowd held
else halves by day 1

Coming wipes

7d 9h
Thu 5 Nov, 19:00 UTC
FW
35d 9h
Thu 3 Dec, 19:00 UTC
FW

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.

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本
EA · groups of 8+ · monthly · 35 on average
35 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
EA · groups of 8+ · monthly · 20 on average
16 / 88
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服
EA · groups of 8+ · monthly · 12 on average
14 / 100
[JP]ちょっぴりHard-PvE RiSu Server
EA · groups of 8+ · monthly · 11 on average
12 / 100
【青岩-PVE服】原倍/萌新/突袭据点
EA · groups of 8+ · monthly · 11 on average
13 / 200
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简
EA · groups of 16+ · monthly · 10 on average
11 / 100

Quick answers

from the figures on this page

Settings and map

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

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs a procedural map of size 4,000 with seed 130303, generated by the game. Look at it on RustMaps from this page: identical size and seed give an identical map. Under map name it shows Custom Map.

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

No gather rate appears in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. 8 players is the group cap, unchanged from the game's default. no player-versus-player combat: that is pve. Plugins or settings change the game, and the browser files it under Modded. Oxide plugins are running. VAC is on, Valve's anti-cheat.

Wipe days

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

The force wipe is the only wipe [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] takes, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, the same date every Rust server wipes. This world has been running since 23 days 19 hours. Monthly wipes are what the tags promise.

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

Its recent wipes drew an average of 3 players at peak. On the latest wipe, 46 hours in, the crowd hit its peak. Half the peak or more lasted until the next wipe in 50% of recent wipes. Day 1 is when it dropped under half on the wipes that failed to hold.

Tags

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

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

What do the server tags on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] mean?

The server browser reads these tags from [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): Slot count: 40; ts8 (Group limit): Team size is capped at 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the game's standard network layer, and it is what runs here; $r? (Region code): Region: not set; ^m (Monthly): Facepunch's force wipe sets the monthly wipe here; ^p (PvE): Player combat is off; the world itself is the threat; ^o (Oxide): It runs Oxide (uMod), a framework for plugins; ^z (Modded): Plugins or settings make changes, so it sits under Modded; EA (East Asia): East Asia is the region it appears under in the server browser. Player count now, queue length and world creation time sit at the top of this page, taken from the tags.

Which Rust Leaderboard lists and filters include [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] appears on the following Rust Leaderboard lists: Best modded Rust servers and Rust PvE servers leaderboard. You can find it through these server list filters: 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.

Server details

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

The build behind [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: Rust network protocol 2635 and build 168909 on Windows. Matching the protocol is what joining needs; Steam handles the update.

Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] up right now, and how steady is it?

[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is up, live and reachable this moment. Going by the uptime it reports, the last restart was about 9 hours ago. The last 7 full days saw it online for 167 of 168 hours, 99% of the time. 17 September 2026 is when Rust Leaderboard first logged it.

How well does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] perform?

The 48-hour average is 59 server fps; the floor was 54. Buildings, deployables and all the rest of the world took the entity count as high as 124,425. The top memory figure was 3,273 MB. What reads as lag to players: fps falling and entities piling up.

Where in the world is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] hosted?

In Asia, says [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], with a EA tag. Where a server says it is, that is what Rust Leaderboard displays, without looking up where the machine stands. Connect to 222.224.192.138:28027.

Player count

Where does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] sit in the rankings?

Player hours over seven days give [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] #3,083 worldwide, #280 in Asia, and the top 14% of ranked servers.

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

0 players fill 40 slots on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] right now. 6 was the high point over seven days, with 1 players on average. In the last 48 hours, 06:00 UTC drew the highest average: 2 players.

Connect

How do I join [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?

In the Rust console (F1) enter client.connect 222.224.192.138:28027. Launch Rust from this page instead and it opens the game through Steam and joins for you. You can find it at https://www.ikkunn53.com/rust.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players Slot count: 40.
ts8
Group limit Team size is capped at 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the game's standard network layer, and it is what runs here.
$r?
Region code Region: not set.

Wipe schedule

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

Gameplay

^p
PvE Player combat is off; the world itself is the threat.

Mods and access

^o
Oxide It runs Oxide (uMod), a framework for plugins.
^z
Modded Plugins or settings make changes, so it sits under Modded.

Region

EA
East Asia East Asia is the region it appears under in the server browser.

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.