Open every day, at every hour Admission free 11,894 servers and 99,159 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 2,228Acc. 2026.2228

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

Rust server, EA · in the archive since 13 September 2026

Online EA 222.224.192.138:28018 checked 13m ago

biweekly wipes moddedoxidepve
To visit
Players now 0/ 40
0% full
7-day average2peak 8
Rank#2,228top 10% · #212 in EA
Last wipe14d agoThu 15 Oct, 14:47 UTC · biweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 16:55 UTCAll times UTC.

The record of each wipe

  1. Thu 15 Oct 202614:47 UTC14d ago
    Peak
    17
    Crowd
    –
    Lasted
    running
    Players before
    4
  2. Fri 2 Oct 202613:17 UTC27d ago
    Peak
    12
    Crowd
    halved by day 7
    Lasted
    13.1 days
    Players before
    0
  3. Thu 17 Sep 202614:50 UTC42d ago
    Peak
    14
    Crowd
    halved by day 11
    Lasted
    14.9 days
    Players before
    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.

The rhythm

Wipe schedule

from its schedule tag

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

14 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
14wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 9

Coming wipes

  1. 7d 1hThu 5 Nov, 19:00 UTCFW
  2. 13d 21hThu 12 Nov, 14:47 UTC
  3. 27d 21hThu 26 Nov, 14:47 UTC
  4. 35d 1hThu 3 Dec, 19:00 UTCFW
  5. 41d 21hThu 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

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

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
0246818:0003:0012:0021:0006:0015:00

Hourly average and peak, UTC.

Folder 2

Server performance

02040608018:0003:0012:0021:0006:0015: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.

Folder 3

Rank

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.

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags and filters

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

The same operator most likely runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, as all publish a ikkunn53.com hostname.

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

The game's server browser reads these tags published by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are set on this server; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): The server runs game protocol 2635; matching it is required to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The server has no region code; ^b (Biweekly): Every two weeks the server wipes; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Oxide, also known as uMod, is the plugin framework in use; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; EA (East Asia): Its entry in the server browser sits under East Asia; rustmaps (Custom tag): Standard Rust does not define this tag; the owner or a plugin added it. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

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

These Rust Server History lists include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers: the record and Rust PvE servers, on record. It appears under 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.

Server entry

Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run smoothly?

Across the last 48 hours it averaged 56 server fps; the low was 31. As many as 131,792 entities were in the world: buildings, deployables and the rest. Memory use peaked at 3,568 MB. Lag, as players feel it, has two sources: low fps and a rising entity count.

Which version of Rust does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?

Rust network protocol 2635 and build 168909 is the build [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs, on Windows. The protocol must match to join, and Steam handles that update.

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

At this moment [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is online. About 5 hours ago is when it last restarted, judged by the uptime it reports. 167 of 168 hours, or 99% of the time, over the last 7 full days. 13 September 2026 is when Rust Server History first saw it.

Where is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] located?

With its EA tag, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Rust Server History does not look up where the machine stands; it shows where a server says it is. Its entry gives 222.224.192.138:28018 as the address.

Wipe record

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

14 players on average was the busiest its recent wipes drew. 46 hours into the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 9 it fell below half in the wipes where it did not hold.

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

Its schedule cannot be confirmed from the record, too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes being on record, so the prediction follows its tag. On Thursday 5 November at 19:00 UTC comes the force wipe, its next wipe, when every Rust server wipes. 14 days 2 hours ago its current world was made. Its tags carry a wipe schedule of every two weeks.

Population

How does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?

Seven days of player hours rank [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #2,228, in the top 10% of all ranked servers; within Asia it is #212.

How busy is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?

Against 40 slots, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] records 0 players right now. The seven-day average stands at 2 players; the peak is 8. An average of 4 players at 13:00 UTC made that the busiest hour of the last 48.

Map and rules

What are the rules and settings 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]. At 8 players, the group limit matches the game's default. pve is the game mode, no combat against other players. Plugins or settings alter the game here, and the browser lists the server under Modded. Oxide plugins are running. The anti-cheat VAC from Valve is active.

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

Size 4,000, custom map: that is what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs. The published file is downloadable here.

Joining the server

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

Entering client.connect 222.224.192.138:28018 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf. https://www.ikkunn53.com/rust is where its website is.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players 40 slots are set on this server.
ts8
Group limit The default cap of 8 per team applies here.
v2635
Protocol The server runs game protocol 2635; matching it is required to join.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^o
Oxide Oxide, also known as uMod, is the plugin framework in use.
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

Region

EA
East Asia Its entry in the server browser sits under East Asia.

Other

rustmaps
Custom tag Standard Rust does not define this tag; the owner or a plugin added it.

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.