Local forecast · EA
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28027 checked 12m ago
Current conditions
observed 12m agoplayers now
0% full
- 7-day average
- 1
- peak 6
- Rank
- #3,055
- top 14% · #292 in EA
- Last wipe
- 23d ago
- monthly schedule
- Next wipe
- 7d 16h
- Thu 5 Nov, 19:00 UK · 19:00 UTC FW
Next wipe
force wipes onlyThursday 5 November, 19:00 UK · 19:00 UTC
in 7d 16h · FW the force wipe
The force wipe · high confidence
Coming wipes
- Thu 5 Nov 19:00 UK · 19:00 UTC 7d 16h FW
- Thu 3 Dec 19:00 UK · 19:00 UTC 35d 16h FW
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 14% of all ranked servers, top 52% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UK · 19:00 UTC, in 7d 16h. The force wipe · high confidence
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 7, 46 hours in.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 5 Oct, 14:53 UKMon 5 Oct, 13:53 UTC · 23d ago | 7 | – | running | 1 |
| Sat 3 Oct, 13:17 UKSat 3 Oct, 12:17 UTC · 25d ago | 1 | held half | 2.1 days | 0 |
| Sun 20 Sep, 12:27 UKSun 20 Sep, 11:27 UTC · 38d 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. 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 pageAbout the server
Is performance good on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Across the last 48 hours the average was 59 server fps, with a floor of 53. At its peak the world had 124,216 entities, counting buildings, deployables and the rest. The peak memory draw was 3,273 MB. Lag is what players call it when fps is low and entities are piling up.
How reliable is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], and is it online now?
You will find [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] online at the moment. The uptime it reports puts the last restart about 2 hours ago. In the last 7 full days it stayed up 167 of 168 hours, 99% of the time. The first sighting by Rust Wipe Stats was on 17 September 2026.
Where does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] run from?
With its EA tag, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Rust Wipe Stats does not look up where the machine stands; it shows where the server says it is. 222.224.192.138:28027 is its address.
What version of Rust is running on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs. The protocol must match for you to join, and Steam keeps it updated.
Lists and tags
Which operator is responsible for [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
The same operator most likely runs [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, as all publish a ikkunn53.com hostname.
Which meaning sits behind each tag on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
For the game's server browser, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp40 (Max players): Capacity: 40; ts8 (Group limit): This is the standard limit: 8 to a team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): This server carries no region code; ^m (Monthly): Wipes follow Facepunch's monthly force wipe; ^p (PvE): Player fighting is off; the world supplies the danger; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Modded is its category, with plugins or settings changing the game; EA (East Asia): You will find it listed in East Asia. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Which Rust Wipe Stats filters and lists carry [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
These Rust Wipe Stats lists include [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: 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: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What map is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] on?
The game generates the map on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], procedural, size 4,000, seed 130303. From this page RustMaps opens it, since equal size and seed give an equal map. You will see the map named Custom Map.
What settings does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] use, and what rules does it enforce?
The name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] says nothing about gather rate. No group setting is published, so the game default of 8 players applies. pve is the game mode, no combat between players. The server browser lists it as Modded, where plugins or settings alter the game. Oxide are the plugin frameworks it runs. Valve anti-cheat (VAC) runs on this server.
Wipe days
When does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipe?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipes with the force wipe and at no other time, once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server takes it. 23 days 12 hours is how long the current world has been running. A monthly wipe schedule is set out in its tags.
What happens on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
The average peak across its recent wipes was 3 players. Peak numbers on the latest wipe arrived 46 hours after the reset. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. The fall below half came by day 1 when the crowd did not hold.
Population
What sort of population does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] carry?
Out of 40 slots, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] has 0 filled right now. Across the past week it peaked at 6 and averaged 1 players. Its busiest point in the last 48 hours was 06:00 UTC, averaging 2 players.
Where does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] sit in the rankings?
Player hours over the last seven days rank [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] at #3,055, top 14% overall and #292 in Asia.
Getting in
What steps let you join [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28027 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.