Station EA-2172 · recording
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28024 checked 11m ago
- Players now
- 2/ 40
- 5% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 2
- peak 12
- Rank
- #2,172
- top 10% · #205 in EA
- Last wipe
- 27d ago
- monthly schedule
- Next wipe
- 6d 17h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 40 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −6into Thu 15:00 UTC
- Peak · 48 h
- 12most 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 38% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 17h. The force wipe · high confidence
- wipe-day peak
- 15players, last three wipes
Coming wipes
- 6d 17hThu 5 Nov, 19:00 UTCFW
- 34d 17hThu 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 15, 18 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 13:18 UTC27d ago | M1.2▲rising | 15 | – | running | 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 pageServer rules
Which map is running on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
The custom map on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is size 4,000, and the published file downloads from this page.
Which settings and rules apply on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
The name of [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] gives no gather rate. The group limit is 8 players, the game's default. pve is the game mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
A reading taken now shows 2 players on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], which has 40 slots. Averaged across the last seven days the population was 2 players, reaching a peak of 12. The last 48 hours show their highest activity at 14:00 UTC, averaging 11 players.
How does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?
For player hours across the last seven days, [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] takes #2,172 overall and #205 in Asia, inside the top 10% of all ranked servers.
Server details
How reliably does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] stay online?
As recorded now, [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is running. The uptime it reports puts its last restart about 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] hold a steady tick rate?
The 48-hour average is 57 server fps; 39 is the lowest observed. At its highest, it carried 117,209 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,220 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] hosted?
With its EA tag, [JPN] IKKUNN Server D (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. The address it publishes is 222.224.192.138:28024.
What build of Rust does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] use?
[JPN] IKKUNN Server D (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 pattern
What does wipe day look like on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
15 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 18 hours after the wipe.
How often does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] wipe, and on which days?
At the force wipe each month [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] wipes, and at no other time. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 27 days 12 hours. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] mean?
These are the tags [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): The server has 40 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^p (PvE): You won't fight other players here; the world is what threatens you; ^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): In the server browser it appears under East Asia; rustmaps (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] appear?
These Rust Server Trends lists include [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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 D (Tokyo) |Japan PvE [ASIA]?
Both [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] and 5 other servers we track publish a ikkunn53.com hostname, so the same operator most likely runs them.
How to join
What steps get you onto [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
To join, enter client.connect 222.224.192.138:28024 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. https://www.ikkunn53.com/rust is where its website lives.
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.