On the class lists: D (45), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average2peak 8
Rank#2,217top 10% · #210 in EA
Last wipe14d agobiweekly schedule
Next wipedueThu 29 Oct, 14:47 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
5/ 100
F
A quiet classroom so far: 2 of 40 on average. Plenty of space to grow.
Standingrank on player hours
90/ 100
A
Well up the rankings: #2,217 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
93/ 100
A
Mostly smooth: 56 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
40/ 100
F
Slipped a little: down 431 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); wipes are 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 10% of all ranked servers, top 39% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
····W··
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 14:47 UTCdue.
Its biweekly schedule tag · low confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak14players, last three wipes
crowd held0%else halves by day 9
Coming wipes
dueThu 29 Oct, 14:47 UTC
7d 3hThu 5 Nov, 19:00 UTCFW
13d 23hThu 12 Nov, 14:47 UTC
27d 23hThu 26 Nov, 14:47 UTC
35d 3hThu 3 Dec, 19:00 UTCFW
41d 23hThu 10 Dec, 14:47 UTC
The first 48 hours of its last wipes
Thu 15 OctFri 2 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 17, 46 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 14:47 UTC14d ago
17
–
running
4
Fri 2 Oct, 13:17 UTC27d ago
12
halved by day 7
13.1 days
0
Thu 17 Sep, 14:50 UTC42d ago
14
halved by day 11
14.9 days
2
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
Which region is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] based in?
You'll see [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] listed in Asia, tagged EA. 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:28018.
How dependable is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA], and is it online at the moment?
Right now, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is online. According to its reported uptime, the last restart was about 3 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.
Does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] perform well?
It never fell below 31 server fps in the last 48 hours, averaging 56. Buildings, deployables and everything else in the world added up to as many as 131,792 entities. Memory use reached up to 3,568 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] running?
Rust network protocol 2635 and build 168909 on Windows is what [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] wipe its map?
Its tag sets the prediction, as the record holds too few of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]'s wipes to confirm its schedule. It is due to wipe next on Thursday 29 October at 14:47 UTC. It has been running its current world for 14 days. A fortnightly wipe schedule appears in its tags.
What happens on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
The average peak on its recent wipes was 14 players. The crowd on the latest wipe was largest 46 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 9.
Population
Where does [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] sit among Rust servers?
In Asia, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] is #210, and overall it is #2,217 on player hours over the last seven days, in the top 10% of all ranked servers.
Is [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] a busy server?
With 40 slots available, [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] currently has 0 players. Averaging 2 players over seven days, it peaked at 8. The highest average in the last 48 hours came at 13:00 UTC, with 4 players.
Tags and filters
How should you read the tags on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The game's browser takes its cue from the tags [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): The server holds 40 slots; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser lists it under East Asia; rustmaps (Custom tag): The owner or a plugin created this tag, so it is not standard Rust. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Who is behind [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
5 other servers we track also use a ikkunn53.com hostname, so they and [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] most likely share an operator.
Which Rust Server Score filters and lists feature [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
These Rust Server Score lists count [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Map and rules
What settings and rules apply on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
The name of [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] gives no gather rate. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Download the published file for the custom 4,000 map on [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] from this page.
Getting in
What is the way to join [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA]?
Enter client.connect 222.224.192.138:28018 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://www.ikkunn53.com/rust.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^b,EA,^p,gmrust,cs168909,ts8,^o^z,rustmaps
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersThe server holds 40 slots.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaThe server browser lists it under East Asia.
Other
rustmaps
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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 term to build on. Strongest in uptime (A); wipes are the one to work on (F).