Local forecast · EA
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28021 checked 10m ago
Current conditions
observed 10m agoplayers now
0% full
- 7-day average
- 3
- peak 13
- Rank
- #1,669
- top 8% · #164 in EA
- Last wipe
- 26d ago
- monthly schedule
- Next wipe
- 7d 20h
- Thu 5 Nov, 19:00 UK · 19:00 UTC FW
Next wipe
force wipes onlyThursday 5 November, 19:00 UK · 19:00 UTC
in 7d 20h · FW the force wipe
The force wipe · high confidence
Coming wipes
- Thu 5 Nov 19:00 UK · 19:00 UTC 7d 20h FW
- Thu 3 Dec 19:00 UK · 19:00 UTC 35d 20h FW
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 29% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UK · 19:00 UTC, in 7d 20h. The force wipe · high confidence
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 14:18 UKFri 2 Oct, 13:18 UTC · 26d ago | 32 | – | running | 0 |
Peak: the most players in the first 48 hours. 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer details
How smoothly does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] run?
Across the last 48 hours the average was 54 server fps, with a floor of 1. Buildings, deployables and all else in the world took the entity count to a peak of 156,721. At most it drew 3,556 MB of memory. A falling fps and a rising entity count show up to players as lag.
Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] online at the moment, and how consistent is its uptime?
Right now [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is up and running. The uptime it reports puts the last restart about 10 hours ago. It was up for 168 of 168 hours across the last 7 full days, 100% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
What location is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] based in?
The EA tag places [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] in Asia, as it lists itself. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 222.224.192.138:28021 is its address.
What Rust version is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] on?
Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] runs. To join you need the same protocol, and Steam handles the update.
Lists and tags
Which operator is responsible for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
The same operator most likely runs [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, as all publish a ikkunn53.com hostname.
How should you read the tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
The server browser reads these tags from [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: gmrust (Game mode): Standard survival, the Rust way; mp40 (Max players): 40 player slots are available; ts8 (Group limit): Teams are at the game default of 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909 is installed here; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region has been set; ^m (Monthly): Wipes follow Facepunch's monthly force wipe; ^p (PvE): Player fighting is off; the world supplies the danger; ^o (Oxide): Oxide, known too as uMod, provides the plugin framework; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded; EA (East Asia): Its place in the server browser is East Asia; rustmaps (Custom tag): Neither standard Rust nor Facepunch defines this tag: the owner or a plugin supplied it. At the top of this page you can see the player count now, the queue and the world's creation time, all from the tags.
Where does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] appear among the Rust Wipe Stats lists and filters?
The Rust Wipe Stats lists that include [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] are: Modded Rust servers and Rust PvE servers, live. 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.
Rules and settings
Which map is in use on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] runs its own custom map, size 4,000. Download the published map file from this page.
What settings does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] use, and what rules does it enforce?
The name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] says nothing about gather rate. No group setting is published, so the game default of 8 players applies. It plays as pve, no combat between players. Plugins or settings change the game here, and the browser files it under Modded. Plugin frameworks in use: Oxide. Valve anti-cheat (VAC) runs on this server.
Wipe days
Which days and times does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] schedule its wipes for?
Once a month is all [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes, at the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server takes it. The current map and world began 26 days 8 hours. A monthly wipe schedule is set out in its tags.
What should you expect from wipe day on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
Its recent wipes drew an average peak of 32 players. 23 hours after the latest wipe, the crowd hit its peak.
Player counts
Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] busy or quiet?
Out of 40 slots, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] has 0 filled right now. Across the past week it peaked at 13 and averaged 3 players. The last 48 hours peak at 12:00 UTC, when the average was 5 players.
Where does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit in the rankings?
Player hours over the last seven days rank [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] at #1,669, top 8% overall and #164 in Asia.
How to join
How do you get into [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28021 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you. You can find its website at https://www.ikkunn53.com/rust.