Station EA-2237 · recording
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28018 checked 9m ago
- Players now
- 3/ 40
- 8% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 2
- peak 8
- Rank
- #2,237
- top 10% · #216 in EA
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 6h
- Thu 29 Oct, 14:47 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 3of 40 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −3into Tue 14:00 UTC
- Peak · 48 h
- 6most 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 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 14:47 UTC, in 6h. 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
- 6hThu 29 Oct, 14:47 UTC
- 7d 11hThu 5 Nov, 19:00 UTCFW
- 14d 6hThu 12 Nov, 14:47 UTC
- 28d 6hThu 26 Nov, 14:47 UTC
- 35d 11hThu 3 Dec, 19:00 UTCFW
- 42d 6hThu 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 14:47 UTC13d ago | M1.1▲rising | 17 | – | running | 4 | |
| Fri 2 Oct, 13:17 UTC26d ago | M1.1▲rising | 12 | halved by day 7 | 13.1 days | 0 | |
| Thu 17 Sep, 14:50 UTC41d ago | M1.1▲rising | 14 | halved by day 11 | 14.9 days | 2 |
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 pageServer rules
Which map is running on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
At size 4,000, the map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is custom and its published file can be downloaded from this page.
Which settings and rules apply on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
You will find no gather rate in the name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
3 of the 40 slots on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] are filled right now. The seven-day average is 2 players, with a peak of 8. Averaged over the last 48 hours, the busiest hour was 13:00 UTC at 4 players.
How does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is #216 in Asia and #2,237 worldwide on the past week's player hours, within the top 10% of ranked servers.
Operator and location
How reliably does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] stay online?
As recorded now, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is running. Its reported uptime points to a restart about 8 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] hold a steady tick rate?
Its average server fps over the last 48 hours was 56, and it never dropped below 31. At its highest, it carried 129,693 entities: buildings, deployables and the world's other contents. Memory use peaked at 3,568 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] run from?
The EA tag is how [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 222.224.192.138:28018 is the address it uses.
What build of Rust does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] use?
[JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
14 players, on average, was the busiest crowd at its recent wipes. 46 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 9 in the wipes where it didn't hold.
How often does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe, and on which days?
Its schedule cannot be confirmed, as too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes are on record; the prediction follows its tag instead. The date of its next wipe is Thursday 29 October at 14:47 UTC. 13 days 17 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Tags
What do the server tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] mean?
Tags published by [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp40 (Max players): The server has 40 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] appear?
These Rust Server Trends lists include [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, tracked live and Rust PvE servers. You will find it 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.
Which person or group runs [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
One operator most likely runs these: [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, all publishing a ikkunn53.com hostname.
How to join
What steps get you onto [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
To join, enter client.connect 222.224.192.138:28018 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. For the website, go to 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.