Station EA-1268 · recording
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28015 checked 12m ago
- Players now
- 1/ 40
- 2% full
- Motion · 24 h
- M0.4▼falling
- −2 players on the day
- 7-day average
- 6
- peak 16
- Rank
- #1,268
- top 6% · #130 in EA
- Last wipe
- 26d ago
- monthly schedule
- Next wipe
- 7d 20h
- 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.4▼falling−2 players
- Sharpest hour
- +4into Wed 13:00 UTC
- Peak · 48 h
- 14most 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 6% of all ranked servers, top 23% 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 20h. The force wipe · high confidence
- wipe-day peak
- 35players, last three wipes
Coming wipes
- 7d 20hThu 5 Nov, 19:00 UTCFW
- 35d 20hThu 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 35, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 13:17 UTC26d ago | M1.5▲rising | 35 | – | 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 pageRules and settings
Which map is running on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
The custom map on [JPN] IKKUNN Server A (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 A (Tokyo) |Japan PvE [ASIA]?
You will find no gather rate in the name of [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]. Groups hold up to 8 players, which is the default for the game. pve is the game 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. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
At this moment, [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] records 1 players across 40 slots. The seven-day average is 6 players, with a peak of 16. The busiest point in the last 48 hours came at 15:00 UTC, averaging 12 players.
How does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] rank against other Rust servers?
The last seven days of player hours place [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] at #1,268, in the top 6% of all ranked servers and #130 in Asia.
Operator and location
How reliably does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] stay online?
Right now, you can reach [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]. The uptime it reports puts its last restart about 10 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] hold a steady tick rate?
Across the last 48 hours it averaged 57 server fps, with a floor of 49. The world held up to 154,114 entities at its peak, buildings and deployables included. It reached a ceiling of 3,642 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Which region does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] run from?
With its EA tag, [JPN] IKKUNN Server A (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:28015.
What build of Rust does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] use?
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
The recent wipes averaged a busiest count of 35 players. 23 hours after the latest wipe, the crowd peaked.
How often does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] wipe, and on which days?
At the force wipe each month [JPN] IKKUNN Server A (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. 26 days 8 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 A (Tokyo) |Japan PvE [ASIA] mean?
These are the tags [JPN] IKKUNN Server A (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): 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): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $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): You won't fight other players here; the world is what threatens you; ^o (Oxide): Oxide (uMod) is the plugin framework running 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; rustmaps (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. 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 A (Tokyo) |Japan PvE [ASIA] appear?
These Rust Server Trends lists include [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]: 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.
Who is behind [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
The same operator most likely runs [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] and the 5 other servers we track that also publish a ikkunn53.com hostname.
Connecting
How do you connect to [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.