On the class lists: C (64), with population over 48 hours and no performance mark.
Players now4/ 4010% full
7-day average6peak 16
Rank#1,279top 6% · #130 in EA
Last wipe26d agomonthly schedule
Next wipe7d 14hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
15/ 100
F
A quiet classroom so far: 6 of 40 on average. Plenty of space to grow.
Standingrank on player hours
94/ 100
A
Well up the rankings: #1,279 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
95/ 100
A+
Runs smoothly: 57 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 65 places this week.
A steady term.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 6% of all ranked servers, top 23% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h.
The force wipe · high confidence
wipe-day peak35players, last three wipes
Coming wipes
7d 14hThu 5 Nov, 19:00 UTCFW
35d 14hThu 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
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 13:17 UTC26d ago
35
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] sit?
In Asia, according to its own listing, sits [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA], with the EA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 222.224.192.138:28015.
How dependable is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA], and is it online at the moment?
The server is up: [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] is online now. According to its reported uptime, the last restart was about 5 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] run?
It averaged 57 server fps over the last 48 hours, with a low of 49. Buildings, deployables and everything else in the world added up to as many as 154,059 entities. At its highest, it used 3,642 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] on?
The server [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] wipe its map?
The force wipe each month is the only wipe [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] takes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 26 days 15 hours. The tags show a monthly wipe schedule.
What should you expect from wipe day on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
The average peak on its recent wipes was 35 players. Peak numbers came 23 hours into the latest wipe.
Player numbers
Where does [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] place in the wider field of Rust servers?
Over the last seven days, [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] has #1,279 for player hours, in the top 6% of all ranked servers and #130 in Asia.
Is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] a busy server?
[JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] is showing 4 players right now, with 40 slots in total. Averaging 6 players over seven days, it peaked at 16. The highest average in the last 48 hours came at 15:00 UTC, with 12 players.
Lists and filters
What is meant by the tags on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Its slot count is 40; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EA (East Asia): The server browser lists it under East Asia; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which person or group runs [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
5 other servers we track also use a ikkunn53.com hostname, so they and [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] most likely share an operator.
Which Rust Server Score filters and lists feature [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
These Rust Server Score lists count [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list 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.
Map and rules
How is [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] set up, and what rules does it keep?
The name of [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA] gives no gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
A custom map of size 4,000 is in use on [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA], and its published file can be downloaded from this page.
Getting in
What is the way to join [JPN] IKKUNN Server A (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://www.ikkunn53.com/rust.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z,rustmaps
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersIts slot count is 40.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EA
East AsiaThe server browser lists it under East Asia.
Other
rustmaps
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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.
A steady term. Strongest in uptime (A+); population is the one to work on (F).