Rust Player Count
47,967 playing now

OfflineEA222.224.192.138:28030checked 14h ago

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

monthly wipes moddedoxidepve
Players now 0/ 40 0% full
7-day average 0 peak 2
Rank #7,370 top 33% · #403 in EA
Last wipe 9d ago monthly schedule
Next wipe 21d 19h Thu 5 Nov, 19:00 UTC FW

Players

AveragePeak
0123414:0018:0021:0001:0004:0008:00

Hourly average and peak, UTC.

Server performance

02040608014:0018:0021:0001:0004:0008: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 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k8 Oct9 Oct10 Oct12 Oct13 Oct14 Oct

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

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 21d 19h. The force wipe

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 71 on average 26/ 100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼EA · groups of 8+ · monthly · 41 on average 24/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average 18/ 88
[JP][PvE]ゆるラス☮YURU RUSTEA · groups of 12+ · monthly · 18 on average 8/ 75
[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 16 on average 10/ 100
【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 14 on average 0/ 200

Quick answers

from the figures on this page

Rules and settings

Which rules govern [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

No gather rate appears in the name of [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]. Up to 8 players per group, which is the game's default. pve is the game mode, other players cannot be fought. The server browser lists it as Modded, with plugins or settings that alter the game. Oxide plugins are running on it. Anti-cheat VAC from Valve is on.

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

[JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] runs a procedural map of size 4,000 with seed 130303, generated by the game. You can see it on RustMaps from this page, because the same size and seed give the same map. Its map is called: Custom Map.

Tags, lists and filters

Who is responsible for [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

The same operator most likely runs [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] and 5 other servers we track, which all publish a ikkunn53.com hostname.

Where can [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] be found in Rust Player Count lists and filters?

These Rust Player Count lists include [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]: Modded Rust servers and Rust PvE servers. You can find it on the server list using 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; Last wipe: In the last 2 weeks.

How should you interpret the tags on [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

For the game's server browser, [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] publishes: gmrust (Game mode): Survival as standard in Rust; mp40 (Max players): 40 slots are available; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): Joining requires the same protocol: 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): No region code is set; ^m (Monthly): Wipes occur monthly, at the same time as the force wipe; ^p (PvE): No player-versus-player combat: the environment provides the danger; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded category: plugins or configuration change gameplay; EA (East Asia): It appears under East Asia when browsing servers. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.

Population

What is the player count on [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

Currently offline, [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] was last seen 14 hours ago. The seven-day average is 0 players, with a peak of 2.

Where does [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] sit in the rankings?

In the last seven days, [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] is #7,370 for player hours, #403 in Asia, and within the top 33% of ranked servers.

About the server

How reliable is [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA], and is it online?

Currently offline, [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] was last seen 14 hours ago. The uptime it gives suggests it restarted about 11 hours ago. It was up 76% of the time over the last 5 full days, 91 of 120 hours. Its first appearance in Rust Player Count was on 8 October 2026.

What Rust version is used on [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

Rust network protocol 2634 and build 166652 on Windows is what [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] uses. Joining requires the same protocol on your game; Steam updates it for you.

What is the location of [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

Its EA tag shows [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] lists itself in Asia. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. You can reach it at 222.224.192.138:28030.

Is [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] lag-free?

In the last 48 hours, it averaged 57 server fps, with a low of 42. The highest entity count was 107,037, covering buildings, deployables and all other objects. At its highest, it used 2,769 MB of memory. Lag, as players experience it, is caused by low fps and increasing entities.

Wipe days

How often does [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] wipe?

Based on the force wipe, the next wipe for [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA] is estimated. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 9 days 9 hours ago. Its tags declare wipes on a monthly schedule.

Connect to the server

What steps are needed to join [JPN] IKKUNN Server TEST (Tokyo) |Japan PvE [ASIA]?

Joining is done by opening the console (F1) and running client.connect 222.224.192.138:28030. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in. https://www.ikkunn53.com/rust is its website.

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,^m,EA,^p,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival as standard in Rust.
mp40
Max players 40 slots are available.
ts8
Group limit This uses the default team cap: 8 players.
v2634
Protocol Joining requires the same protocol: 2634.
cs166652
Build Build number: 166652.
ptrak
Networking RakNet is the game's usual network protocol, and this server uses it.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Wipes occur monthly, at the same time as the force wipe.

Gameplay

^p
PvE No player-versus-player combat: the environment provides the danger.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded The Modded category: plugins or configuration change gameplay.

Region

EA
East Asia It appears under East Asia when browsing servers.

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.