On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average1peak 6
Rank#3,083top 14% · #280 in EA
Last wipe23d agomonthly schedule
Next wipe7d 12hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
3/ 100
F
A quiet classroom so far: 1 of 40 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,083 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
98/ 100
A+
Runs smoothly: 59 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 556 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (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 14% of all ranked servers, top 50% 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
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h.
The force wipe · high confidence
usual gap7.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 1
Coming wipes
7d 12hThu 5 Nov, 19:00 UTCFW
35d 12hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Mon 5 OctSat 3 OctSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 7, 46 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 13:53 UTC23d ago
7
–
running
1
Sat 3 Oct, 12:17 UTC25d ago
1
✓ held half
2.1 days
0
Sun 20 Sep, 11:27 UTC38d ago
1
halved by day 1
13 days
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
Which region is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] based in?
In Asia, according to its own listing, sits [JPN] IKKUNN Server BP (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. Find it at 222.224.192.138:28027.
Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] up, and how steady is its uptime?
You can join now: [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is online. About 7 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
Does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] perform well?
It never fell below 53 server fps in the last 48 hours, averaging 59. At its peak, it held 124,425 entities, including buildings, deployables and all else in the world. At its highest, it used 3,273 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] sit?
The server [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipe, and how often?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 23 days 16 hours have passed since this world was made. Its tags record that it wipes monthly.
What happens on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
Recent wipes have peaked at 3 players on average. The crowd on the latest wipe was largest 46 hours after it began. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
What position does [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] hold in the rankings?
In Asia, [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is #280, and overall it is #3,083 on player hours over the last seven days, in the top 14% of all ranked servers.
Is [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] a busy server?
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] is showing 0 players right now, with 40 slots in total. Averaging 1 players over seven days, it peaked at 6. Over the last 48 hours, the peak hour was 06:00 UTC, averaging 2 players.
Tags
What do [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]'s tags stand for?
The game's browser takes its cue from the tags [JPN] IKKUNN Server BP (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): A team can hold 8 at most, which is the game default; 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): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): In the server browser it appears under East Asia. 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 BP (Tokyo) |Japan PvE [ASIA]?
A ikkunn53.com hostname is published by [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] and by 5 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Rust Server Score lists that include [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]: 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: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
What settings and rules apply on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
Nothing in the name of [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] states a gather rate. 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. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
[JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] runs which map?
The game generates the procedural map on [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA] at size 4,000 with seed 130303. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Getting in
How should you connect to [JPN] IKKUNN Server BP (Tokyo) |Japan PvE [ASIA]?
To connect, start Rust, press F1, and type client.connect 222.224.192.138:28027. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://www.ikkunn53.com/rust.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).