[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28018 checked 8m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 10% of all ranked servers, top 43% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 29 October, 14:47 UTC, in 1d 17h. Its biweekly schedule tag · low confidence
- usual gap
- 14 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 14players, last three wipes
- crowd held
- 0%else halves by day 9
Coming wipes
- in 1d 17hThu 29 Oct, 14:47 UTC
- in 8d 22hThu 5 Nov, 19:00 UTCFW
- in 15d 17hThu 12 Nov, 14:47 UTC
- in 29d 17hThu 26 Nov, 14:47 UTC
- in 36d 22hThu 3 Dec, 19:00 UTCFW
- in 43d 17hThu 10 Dec, 14:47 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
15 OCT 2026Thu 15 Oct, 14:47 UTC12d ago |
17 | – | running | 4 |
2 OCT 2026Fri 2 Oct, 13:17 UTC25d ago |
12 | halved by day 7 | 13.1 days | 0 |
17 SEP 2026Thu 17 Sep, 14:50 UTC40d 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.
Quick answers
From the figures on this page.
Map and rules
What settings and rules does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?
You will find no gather rate in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. 8 players per group is the default limit. Filed under pve, no PvP fighting. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Size 4,000, custom map. The file is published on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and can be downloaded from this page.
Tags and filters
Which lists and filters on Rust Server Index is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] filed under?
These lists on Rust Server Index take [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. Filed 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; Last wipe: In the last 2 weeks.
Whose server is [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 tracked servers, since all publish a ikkunn53.com hostname.
What is meant by the tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
These are the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): 40 slots are available; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): The game build here is 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): A region code is absent; ^b (Biweekly): Every second week brings a wipe; ^p (PvE): No fighting between players: the danger comes from the world; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Modded: the game is changed by plugins or settings; EA (East Asia): Server browser region: East Asia; rustmaps (Custom tag): Set outside Rust's standard tags, by the owner or through a plugin. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
What happens on wipe day at [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
At their busiest, its recent wipes drew 14 players on average. 46 hours into the latest wipe, the crowd reached its peak. The crowd held above half the peak until the next wipe in 0% of its recent wipes. By day 9 the crowd had fallen below half when it didn't hold.
When does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe?
Too few wipes of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are recorded to confirm its schedule, so the tag sets the prediction. Dated for Thursday 29 October at 14:47 UTC: its next wipe. Its present world dates from 12 days 6 hours. Its tags state wipes every two weeks.
Player counts
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] sit in the rankings?
The seven-day player-hours ranking places [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #2,259 and #236 in Asia, among the top 10% of ranked servers.
How many players are on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at the moment?
The live count for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] stands at 0 players, out of 40 slots. Filed under seven-day figures: an average of 2 players and a peak of 8. Over the last 48 hours, 08:00 UTC drew the highest average: 6 players.
Server details
What version does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] use?
Rust network protocol 2635 and build 168909 on Windows is what you will find on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. To join you need the same protocol; Steam handles the update.
How reliable is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it online now?
The server is live at this moment: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. The uptime it reports puts the last restart at about 10 hours ago. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. It was first recorded by Rust Server Index on 13 September 2026.
Is the performance on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] good?
The last 48 hours give an average of 56 server fps and a floor of 19. The entity count reached 129,693, covering buildings, deployables and all else in the world. The peak memory figure stood at 3,654 MB. A climbing entity count and low fps are felt by players as lag.
Which region is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] in?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] gives Asia as its location and the tag EA. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 222.224.192.138:28018.
Connecting
How can you connect to [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Two ways in. Type client.connect 222.224.192.138:28018 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. https://www.ikkunn53.com/rust is where its website lives.
Server tags
What each one means.
Published as mp40,ptrak,$r?,v2635,^b,EA,^p,gmrust,cs168909,ts8,^o^z,rustmaps
Game
gmrust
mp40
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Gameplay
^p
Mods and access
^o
^z
Region
EA
Other
rustmaps
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.