Local forecast · EA
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28018 checked 7m ago
Current conditions
observed 7m agoplayers now
0% full
- 7-day average
- 2
- peak 8
- Rank
- #2,263
- top 10% · #223 in EA
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 17h
- Thu 29 Oct, 14:47 UK · 14:47 UTC
Next wipe
from its schedule tagThursday 29 October, 14:47 UK · 14:47 UTC
in 17h
Its biweekly schedule tag · low confidence
Coming wipes
- Thu 29 Oct 14:47 UK · 14:47 UTC 17h
- Thu 5 Nov 19:00 UK · 19:00 UTC 7d 21h FW
- Thu 12 Nov 14:47 UK · 14:47 UTC 14d 17h
- Thu 26 Nov 14:47 UK · 14:47 UTC 28d 17h
- Thu 3 Dec 19:00 UK · 19:00 UTC 35d 21h FW
- Thu 10 Dec 14:47 UK · 14:47 UTC 42d 17h
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
daily · 1 is bestTop 10% of all ranked servers, top 40% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 14:47 UK · 14:47 UTC, in 17h. Its biweekly schedule tag · low confidence
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 15:47 UKThu 15 Oct, 14:47 UTC · 13d ago | 17 | – | running | 4 |
| Fri 2 Oct, 14:17 UKFri 2 Oct, 13:17 UTC · 26d ago | 12 | halved by day 7 | 13.1 days | 0 |
| Thu 17 Sep, 15:50 UKThu 17 Sep, 14:50 UTC · 41d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer details
How smoothly does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run?
Its average over the last 48 hours was 57 server fps, and it never dropped below 33. Buildings, deployables and all else in the world took the entity count to a peak of 129,693. At most it drew 3,568 MB of memory. Players feel lag when fps drops and the entity count climbs.
How reliable is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it online now?
Right now [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is up and running. The uptime it reports puts the last restart about 6 hours ago. In the last 7 full days it stayed up 168 of 168 hours, 100% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run from?
In Asia is where [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself, using its EA tag. Rust Wipe Stats does not look up where the machine stands; it shows where the server says it is. 222.224.192.138:28018 is its address.
What Rust version is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] on?
On [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] you will find Rust network protocol 2635 and build 168909, hosted on Windows. The protocol must match for you to join, and Steam keeps it updated.
Lists and tags
Who operates [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.
What do [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s tags tell you?
For the game's server browser, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] publishes these tags: gmrust (Game mode): The mode is plain Rust survival; mp40 (Max players): 40 player slots are available; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909 is installed here; ptrak (Networking): RakNet is the network layer, as standard for the game; $r? (Region code): This server carries no region code; ^b (Biweekly): The cycle is two weeks between wipes; ^p (PvE): Player fighting is off; the world supplies the danger; ^o (Oxide): Oxide, known too as uMod, provides the plugin framework; ^z (Modded): Modded is its category, with plugins or settings changing the game; EA (East Asia): Its place in the server browser is East Asia; rustmaps (Custom tag): A plugin or the owner set this tag; it is not one of Rust's standard ones. At the top of this page you can see the player count now, the queue and the world's creation time, all from the tags.
Which Rust Wipe Stats filters and lists carry [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] appears in the following Rust Wipe Stats lists: Modded Rust servers and Rust PvE servers, live. These filters on the server list will bring it up: 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.
Rules and settings
Which map is in use on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is custom, size 4,000, with its file published for download on this page.
What settings does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] use, and what rules does it enforce?
The name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] says nothing about gather rate. The default of 8 players is the group limit here. pve is the game mode, no player fighting. Plugins or settings change the game here, and the browser files it under Modded. Plugin frameworks in use: Oxide. This server has VAC switched on.
Wipe schedule
On what schedule does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe?
Its tag sets the prediction, because the record of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes is too thin to confirm the schedule. Thursday 29 October at 14:47 UTC is when its next wipe is due. 13 days 6 hours is how long the current world has been running. A fortnightly wipe schedule appears in its tags.
What happens on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
Its recent wipes drew an average peak of 14 players. 46 hours after the latest wipe, the crowd hit its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. The fall below half came by day 9 when the crowd did not hold.
Population history
How many players does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is carrying 0 players at the moment, out of 40 slots. Averaged over seven days: 2 players, peaking at 8. The last 48 hours peak at 13:00 UTC, when the average was 4 players.
What position does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold among Rust servers?
Seven-day player hours place [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] at #2,263, inside the top 10% of ranked servers and at #223 in Asia.
Getting in
What steps let you join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28018 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you. https://www.ikkunn53.com/rust is its website.