Server profile · EA
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online, with 0 of 40 players on; ranked #2,204 of every public Rust server, the top 10%. It last wiped 13d ago.
Online EA 222.224.192.138:28018 checked 8m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
From its schedule tag.
Next wipe Thursday 29 October, 14:47 UTC, in 38m. Its biweekly schedule tag · low confidence
Coming wipes
- 38mThu 29 Oct, 14:47 UTC
- 7d 4hThu 5 Nov, 19:00 UTCFW
- 14d 0hThu 12 Nov, 14:47 UTC
- 28d 0hThu 26 Nov, 14:47 UTC
- 35d 4hThu 3 Dec, 19:00 UTCFW
- 42d 0hThu 10 Dec, 14:47 UTC
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 14:47 UTC13d 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 UTC41d ago | 14 | halved by day 11 | 14.9 days | 2 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe cycle
On [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], what happens on wipe day?
At their busiest, its recent wipes drew 14 players on average. 46 hours into the latest wipe, the crowd on the server reached its peak. Half the peak held until the next wipe in 0% of its recent wipes. In the other cases, it dropped below half by day 9.
When does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe, and how often?
Its tag sets the prediction: too few wipes on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are on record to confirm the schedule. You can expect the next wipe on Thursday 29 October at 14:47 UTC. 13 days 23 hours have passed since its current world was created. According to its tags, wipes come every two weeks.
About the server
Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold a steady frame rate?
Average server fps over the last 48 hours was 56, with a floor of 31. Buildings, deployables and the rest took the entity count as high as 131,792. Memory use peaked at 3,568 MB. What players feel as lag comes from low fps and an entity count on the rise.
On what version does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] currently run?
Running on Windows, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is on Rust network protocol 2635 and build 168909. Joining needs your game on the same protocol, which Steam updates for you.
Has [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] stayed online, and is it up now?
Right now [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is up and running. Going by the uptime figure it gives, its last restart was around 2 hours ago. It spent 167 of the last 7 full days' 168 hours up, 99% of the time. The first record Rust Insights has of it is 13 September 2026.
What location is listed for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The EA tag is how [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] places itself in Asia. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. Connect through 222.224.192.138:28018.
Server tags
What is meant by each tag on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The tags gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): The slot count is 40; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): The world is the threat here, since players do not fight one another; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; EA (East Asia): Find it in the browser under East Asia; rustmaps (Custom tag): Owners and plugins can add tags, and this is one; it is not standard Rust are what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes, and the server browser in the game reads them. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.
Which person or group runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and 5 other servers we track all publish a ikkunn53.com hostname, so the same operator most likely runs them.
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] turn up among the Rust Insights lists and filters?
The Rust Insights lists that carry [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are Modded Rust servers, explained and Rust PvE servers, live. On the server list, the filters that surface it are 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.
Player counts
How many players are on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] right now, and how does that number move?
Of its 40 slots, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] currently has 0 filled. A weekly average of 2 players goes with a peak of 8. The busiest point of the last 48 hours fell at 13:00 UTC, averaging 4 players.
In the ranking of Rust servers, where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] place?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] holds #2,204 for player hours over the last seven days, #210 in Asia and in the top 10% of all ranked servers.
Map and rules
What are the settings and rules for [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Nothing about gather rate is given in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. No group limit is set, so the game's default of 8 players applies. pve is the game mode, no fighting other players. The server browser lists it under Modded: plugins or settings alter the game. Oxide is the plugin count it runs. Anti-cheat: VAC, from Valve, is on.
Which map is live on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
A custom map of size 4,000 is in use on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]; download its published file from this page.
Join
How do you connect to [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Open the console with F1 in Rust and enter client.connect 222.224.192.138:28018. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you. You will find its website at https://www.ikkunn53.com/rust.