Station EA-3091 · recording
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28027 checked 13m ago
- Players now
- 0/ 40
- 0% full
- Motion · 24 h
- M0.1▲rising
- +1 players on the day
- 7-day average
- 1
- peak 6
- Rank
- #3,091
- top 14% · #280 in EA
- Last wipe
- 23d ago
- monthly schedule
- Next wipe
- 7d 5h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 40 slots
- Motion · 24 h
- M0.1▲rising+1 players
- Sharpest hour
- −1into Wed 08:00 UTC
- Peak · 48 h
- 4most players in any hour
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 51% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 5h. The force wipe · high confidence
- usual gap
- 7.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 3players, last three wipes
- crowd held
- 50%else halves by day 1
Coming wipes
- 7d 5hThu 5 Nov, 19:00 UTCFW
- 35d 5hThu 3 Dec, 19:00 UTCFW
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 13:53 UTC23d ago | M0.8▲rising | 7 | – | running | 1 | |
| Sat 3 Oct, 12:17 UTC26d ago | M0.0▲rising | 1 | held half | 2.1 days | 0 | |
| Sun 20 Sep, 11:27 UTC39d ago | M0.0▲rising | 1 | halved by day 1 | 13 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs a procedural map of size 4,000 with seed 130303, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is Custom Map.
Which settings and rules apply on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
You will find no gather rate in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]. The group limit is 8 players, the game's default. In pve mode, no player-versus-player fighting. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
A reading taken now shows 0 players on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA], which has 40 slots. Across seven days this server recorded an average of 1 players and a peak of 6. The last 48 hours show their highest activity at 10:00 UTC, averaging 2 players.
How does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?
For player hours across the last seven days, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] takes #3,091 overall and #280 in Asia, inside the top 14% of all ranked servers.
Server facts
How reliably does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] stay online?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is up at the moment. Going by the uptime figure it reports, it restarted about 1 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 17 September 2026 it was recorded for the first time by Rust Server Trends.
How well does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] perform under load?
Its average server fps over the last 48 hours was 59, and it never dropped below 57. At its highest, it carried 124,425 entities: buildings, deployables and the world's other contents. It reached a ceiling of 3,273 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Where in the world is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] hosted?
In Asia [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] lists itself, with the tag EA. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 222.224.192.138:28027.
Which Rust version is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] running?
On Windows, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
3 players, on average, was the busiest crowd at its recent wipes. 46 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 50% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
How often does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipe, and on which days?
Once a month [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipes, at the force wipe. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 23 days 23 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Server tags
What do the server tags on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] mean?
The game's server browser reads the tags [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] publishes: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EA (East Asia): East Asia is the region it's listed under in the browser. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] appear?
The Rust Server Trends lists that take in [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] are: Modded Rust servers, tracked live and Rust PvE servers. These filters bring it up on the server list: 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.
Which person or group runs [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
One operator most likely runs these: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, all publishing a ikkunn53.com hostname.
Connecting
How do you connect to [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
You can connect by pressing F1 in Rust and typing client.connect 222.224.192.138:28027 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://www.ikkunn53.com/rust.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.