An entry in the registerNo. 1,701
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]
Online EA 222.224.192.138:28021 checked 9m ago
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is a Rust server in Asia, one of the ikkunn53.com servers. At the last count it had 0 players of a possible 40; over the past week it averaged 3, with a peak of 13. It stands at No. 1,701 of the ranked servers, the top 8%, and No. 167 in Asia. It last wiped 26d ago, on a monthly schedule, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as modded, oxide, pve.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 8% of all ranked servers, top 30% in EA. Ranked on player hours over the last seven days.
§ 4The wipe scheduleforce wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. The force wipe · high confidence
players, last three wipes
| Date, UTC | Hence |
|---|---|
| Thu 5 Nov, 19:00 FW | 7d 10h |
| Thu 3 Dec, 19:00 FW | 35d 10h |
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.
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 13:18 UTC26d 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.
§ 6In its own wordsas the server describes itself
Japan PvE Server Tokyo This server is currently in a 24-hour run.Please join the Discord server for more information discord discord.gg/6qtWzqrkGX Rules.No attacking or harassing players.Do not spam or overload the server.
§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本37/100 EA · groups of 8+ · monthly · 35 on average
- 2 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地17/88 EA · groups of 8+ · monthly · 20 on average
- 3 [熊猫PVE]修仙升级/召唤/据点/10月新档正式服13/100 EA · groups of 8+ · monthly · 12 on average
- 4 [JP]ちょっぴりHard-PvE RiSu Server14/100 EA · groups of 8+ · monthly · 11 on average
- 5 【青岩-PVE服】原倍/萌新/突袭据点13/200 EA · groups of 8+ · monthly · 11 on average
- 6 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简12/100 EA · groups of 16+ · monthly · 10 on average
§ 8Questions answeredfrom the figures in this entry
The record
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. The protocol must match on your game to join; the update comes through Steam.
Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] up, and how steady is its uptime?
The records show [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] online at the time of this check. Of note: the reported uptime places the last restart about 8 hours ago. Of note: 167 of 168 hours up in the last 7 full days, or 99% of the time. Its earliest entry at Rust Server Stats is dated 13 September 2026.
What is the performance of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] like?
The records show an average of 54 server fps over 48 hours, never below 1. Buildings, deployables and the rest brought the entity count to a high of 156,405. The memory peak was 3,556 MB. What players feel as lag: fps running low and entities climbing.
In which location does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit?
Under the EA tag, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. 222.224.192.138:28021 — that is the address.
Rules, settings, map
What map is in use on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] runs a custom map of size 4,000. Its map file is published, so it can be downloaded from this page.
What settings and rules does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] run?
The name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] states no rate for gathering. Eight players per group is the default and the limit here. pve is the game mode, player combat is excluded. The server browser lists it under Modded, where plugins or settings alter the game. The plugin set is Oxide. VAC, Valve's anti-cheat, is enabled.
The players
What population does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] carry?
At the latest count [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] has 0 players, with 40 slots in total. Averaged across seven days, 3 players; the peak reached 13. The busiest hour of the last 48 was 12:00 UTC, averaging 5 players.
Where does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit in the rankings?
For seven-day player hours [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is #1,701 overall and #167 in Asia, in the top 8% of ranked servers.
The tags and lists
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sits in which Rust Server Stats lists and filters?
On Rust Server Stats, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is placed in these lists: Modded Rust servers and Rust PvE servers. On the server list it comes up under these filters: 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 meanings attach to the tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
The game's server browser reads the tags [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] publishes: gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Slot count: 40; ts8 (Group limit): 8 to a team, which is the default; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): Region code absent; ^m (Monthly): Monthly wipes, in step with Facepunch's force wipe; ^p (PvE): The danger comes from the world, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded; EA (East Asia): The server browser files it under East Asia; rustmaps (Custom tag): A plugin or the owner set this tag; it is not standard Rust. The tags include current players, queue and the time the world was made; the top of this page shows them.
Which operator stands behind [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
Most likely one operator runs [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and 5 other servers we track: all publish a ikkunn53.com hostname.
Wipe record
What is the shape of wipe day on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
Across its recent wipes, the busiest point averaged 32 players. 23 hours into the latest wipe the crowd reached its peak.
On what schedule does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe?
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes with the force wipe alone, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers are wiped. Of note: the current world is 26 days 18 hours old. A monthly wipe schedule is published in its tags.
Connection
Which steps join [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
To connect, open the console with F1 in Rust and enter client.connect 222.224.192.138:28021. The Launch Rust and join button on this page does the same through Steam. The server's website is recorded as https://www.ikkunn53.com/rust.