On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now1/ 402% full
7-day average3peak 13
Rank#1,710top 8% · #169 in EA
Last wipe26d agomonthly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
8/ 100
F
A quiet classroom so far: 3 of 40 on average. Plenty of space to grow.
Standingrank on player hours
92/ 100
A
Well up the rankings: #1,710 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
92/ 100
A
Mostly smooth: 55 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
46/ 100
D
Slipped a little: down 131 places this week. Nothing a good wipe can't fix.
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 8% of all ranked servers, top 30% 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 8h.
The force wipe · high confidence
wipe-day peak32players, last three wipes
Coming wipes
7d 8hThu 5 Nov, 19:00 UTCFW
35d 8hThu 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 32, 23 hours in.
Wipes
newest 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit?
In Asia, according to its own listing, sits [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], with the EA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 222.224.192.138:28021.
How reliable is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA], and is it up?
Right now, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is online. According to its reported uptime, the last restart was about 10 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.
Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] smooth to play on?
The average over the last 48 hours was 55 server fps, and it never went below 2. Up to 156,405 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 3,556 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit?
You will find [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipe, and how often?
Once a month, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] wipes with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 26 days 20 hours. The tags show a monthly wipe schedule.
What happens on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
The average peak on its recent wipes was 32 players. The crowd on the latest wipe was largest 23 hours after it began.
Player count
Where does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] sit among Rust servers?
In Asia, [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is #169, and overall it is #1,710 on player hours over the last seven days, in the top 8% of all ranked servers.
Is [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] a busy server?
[JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is showing 1 players right now, with 40 slots in total. It peaked at 13 and averaged 3 players over the last seven days. The busiest time in the last 48 hours was 12:00 UTC, with an average of 5 players.
Lists and filters
How should you read the tags on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
You'll see [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] tagged with gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Its slot count is 40; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EA (East Asia): You will find it under East Asia in the browser; rustmaps (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which person or group runs [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
A ikkunn53.com hostname is published by [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] and by 5 other tracked servers, which suggests one operator.
Where does [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]: 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
What settings and rules apply on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
You will find no gather rate in the name of [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
The map on [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA] is custom at size 4,000, and because the file is published you can download it from this page.
Getting in
What is the way to join [JPN] IKKUNN Server C (Tokyo) |Japan PvE [ASIA]?
To connect, start Rust, press F1, and type client.connect 222.224.192.138:28021. Or click Launch Rust here, which launches Rust through Steam and joins you. 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 limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EA
East AsiaYou will find it under East Asia in the browser.
Other
rustmaps
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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).