Rust Server IndexCard catalogue of Rust servers

Holdings11,618 servers39,799 players88 fresh wipes

Call no.EA1699 On the shelf · online

[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]

Online EA 222.224.192.138:28021 checked 10m ago

Subjects 1. monthly wipes 2. modded3. oxide4. pve
Players now
1/ 40
2% full
7-day average
3
peak 13
Rank
#1,699
top 8% · #167 in EA
Last wipeWiped2 OCT2026 · 26d 18h ago
26d ago · monthly schedule
Next wipe
7d 11h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
02.557.51008:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

02040608008:0017:0002:0011:0021:0006:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 8% of all ranked servers, top 30% in EA. Ranked on player hours over the last seven days.

Record sheet D · loan terms

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence

wipe-day peak
32players, last three wipes

Coming wipes

  1. in 7d 11hThu 5 Nov, 19:00 UTCFW
  2. in 35d 11hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 32, 23 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
2 OCT 2026Fri 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EA
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average
37/ 100
EA
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average
18/ 88
EA
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average
12/ 100
EA
[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average
11/ 100
EA
【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average
13/ 200
EA
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average
11/ 100
Reference desk

Quick answers

From the figures on this page.

Rules and settings

On [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], which rules and settings apply?

You will find no gather rate in the name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. The group limit is 8 players, the game's default. Filed under pve, no PvP fighting. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.

What is the map on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Size 4,000, custom map. The file is published on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and can be downloaded from this page.

Lists and filters

On Rust Server Index, which lists and filters carry [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

The Rust Server Index lists that include [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] are Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. These filters on the server list bring it up: 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 operator stands behind [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] publishes a ikkunn53.com hostname, as do 5 other servers we track, which points to one operator for them all.

What is meant by the tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Filed under these tags, as published by [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): Player cap: 40; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): Build on file: 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^m (Monthly): The wipe schedule is monthly, alongside the Facepunch force wipe; ^p (PvE): Player against player combat is off; the world supplies the danger; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): This one is Modded, since plugins or settings change how it plays; EA (East Asia): Server browser region: East Asia; rustmaps (Custom tag): This one is not a standard Rust tag; an owner or plugin put it there. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipe schedule

How does a wipe day run on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

The average peak across its recent wipes is 32 players. The latest wipe peaked 23 hours in.

When does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe?

The only wipe on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is the monthly force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it runs now was made 26 days 18 hours. A monthly wipe schedule is published in its tags.

Player counts

How is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] ranked compared with the rest?

The seven-day player-hours ranking places [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] at #1,699 and #167 in Asia, among the top 8% of ranked servers.

What does the player count on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] look like?

The live count for [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] stands at 1 players, out of 40 slots. Filed under seven-day figures: an average of 3 players and a peak of 13. The busiest point in the last 48 hours was 12:00 UTC, averaging 5 players.

Server details

What version does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] use?

Rust network protocol 2635 and build 168909 on Windows is what you will find on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. The protocol must match before you can join, and Steam takes care of updating it.

Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] reachable, and does it stay up?

You will find [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] online as of now. About 8 hours ago, by its own uptime figure, is when it last restarted. Of the last 7 full days, 167 of 168 hours were up, 99% of the time. It was first recorded by Rust Server Index on 13 September 2026.

Is the performance on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] good?

Averaged over the last 48 hours, server fps was 54, with a low of 1. Buildings, deployables and everything else in the world came to as many as 156,721 entities. Memory use reached as much as 3,556 MB. What players feel as lag is low fps together with a rising entity count.

Which region is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] in?

[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] gives Asia as its location and the tag EA. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 222.224.192.138:28021.

Connecting

What is the way onto [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?

Two ways in. Type client.connect 222.224.192.138:28021 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. The website can be found at https://www.ikkunn53.com/rust.

Subject headings explained

Server tags

What each one means.

Published as mp40,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z,rustmaps

Game

gmrust
Game mode Survival on standard Rust rules.
mp40
Max players Player cap: 40.
ts8
Group limit The team limit is 8, as in the standard game.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build Build on file: 168909.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code The region code field is left empty.

Wipe schedule

^m
Monthly The wipe schedule is monthly, alongside the Facepunch force wipe.

Gameplay

^p
PvE Player against player combat is off; the world supplies the danger.

Mods and access

^o
Oxide Oxide, also known as uMod, provides the plugin framework.
^z
Modded This one is Modded, since plugins or settings change how it plays.

Region

EA
East Asia Server browser region: East Asia.

Other

rustmaps
Custom tag This one is not a standard Rust tag; an owner or plugin put it there.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.