Station EA-1734 · recording
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28021 checked 13m ago
- Players now
- 1/ 40
- 2% full
- Motion · 24 h
- M0.5▼falling
- −3 players on the day
- 7-day average
- 3
- peak 13
- Rank
- #1,734
- top 8% · #171 in EA
- Last wipe
- 27d ago
- monthly schedule
- Next wipe
- 7d 1h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 40 slots
- Motion · 24 h
- M0.5▼falling−3 players
- Sharpest hour
- −3into Thu 14:00 UTC
- Peak · 48 h
- 7most 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 8% of all ranked servers, top 32% 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 1h. The force wipe · high confidence
- wipe-day peak
- 32players, last three wipes
Coming wipes
- 7d 1hThu 5 Nov, 19:00 UTCFW
- 35d 1hThu 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 32, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 13:18 UTC27d ago | M1.5▲rising | 32 | – | 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 C (Tokyo) |Japan PvE [ASIA]?
At size 4,000, the map on [JPN] IKKUNN Server C (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 C (Tokyo) |Japan PvE [ASIA]?
The name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] gives no gather rate. The group limit is 8 players, the game's default. In pve mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] right now?
At this moment, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] records 1 players across 40 slots. Averaged across the last seven days the population was 3 players, reaching a peak of 13. The busiest point in the last 48 hours came at 12:00 UTC, averaging 6 players.
How does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?
The last seven days of player hours place [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] at #1,734, in the top 8% of all ranked servers and #171 in Asia.
Server details
How reliably does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] stay online?
Right now, you can reach [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. Going by the uptime figure it reports, it restarted about 6 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] perform under load?
Its average server fps over the last 48 hours was 55, and it never dropped below 2. At its highest, it carried 156,405 entities: buildings, deployables and the world's other contents. Memory use peaked at 3,617 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] hosted?
With its EA tag, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 222.224.192.138:28021.
What build of Rust does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] use?
On Windows, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
On average, the busiest point of its recent wipes drew 32 players. 23 hours after the latest wipe, the crowd peaked.
How often does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe, and on which days?
At the force wipe each month [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 27 days 4 hours. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] mean?
Tags published by [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp40 (Max players): The server has 40 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): East Asia is the region it's listed under in the browser; rustmaps (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. 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 C (Tokyo) |Japan PvE [ASIA] appear?
These Rust Server Trends lists include [JPN] IKKUNN Server C (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: 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 C (Tokyo) |Japan PvE [ASIA]?
Both [JPN] IKKUNN Server C (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 C (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28021 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.