On the class lists: C (60), with population over 48 hours and no performance mark.
Players now3/ 408% full
7-day average2peak 9
Rank#2,270top 10% · #223 in EA
Last wipe26d agomonthly schedule
Next wipe7d 9hThu 5 Nov, 19:00 UTC FW
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,270 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
96/ 100
A+
Runs smoothly: 58 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
47/ 100
D
Slipped a little: down 116 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 10% of all ranked servers, top 40% 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 9h.
The force wipe · high confidence
wipe-day peak15players, last three wipes
Coming wipes
7d 9hThu 5 Nov, 19:00 UTCFW
35d 9hThu 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 15, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 13:18 UTC26d ago
15
–
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
Which region is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] based in?
The EA tag on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] puts it in Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 222.224.192.138:28024.
How reliable is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA], and is it up?
Right now, [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is online. The uptime it reports puts the last restart at about 10 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] perform well?
It never fell below 39 server fps in the last 48 hours, averaging 58. Buildings, deployables and everything else in the world added up to as many as 117,104 entities. Up to 3,494 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] running?
The server [JPN] IKKUNN Server D (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.
Resets
On what schedule does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] reset?
[JPN] IKKUNN Server D (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. 26 days 20 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What happens on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] when wipe day arrives?
Recent wipes have peaked at 15 players on average. The crowd on the latest wipe was largest 18 hours after it began.
Player count
What position does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] hold in the rankings?
In Asia, [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is #223, and overall it is #2,270 on player hours over the last seven days, in the top 10% of all ranked servers.
How many players does [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] usually have?
[JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is showing 3 players right now, with 40 slots in total. The seven-day average is 2 players, with a peak of 9. The highest average in the last 48 hours came at 13:00 UTC, with 7 players.
Tags
How should you read the tags on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
You'll see [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] tagged with 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): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^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): In the server browser it appears under East Asia; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who operates [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
A ikkunn53.com hostname is published by [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] and by 5 other tracked servers, which suggests one operator.
Which Rust Server Score filters and lists feature [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
Rust Server Score lists that include [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up 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 D (Tokyo) |Japan PvE [ASIA]?
Nothing in the name of [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] states a gather rate. With no change from the game default, groups take up to 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. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] uses?
The map on [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA] is custom at size 4,000, and because the file is published you can download it from this page.
Connecting
What is the way to join [JPN] IKKUNN Server D (Tokyo) |Japan PvE [ASIA]?
To connect, start Rust, press F1, and type client.connect 222.224.192.138:28024. 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,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
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
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
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EA
East AsiaIn the server browser it appears 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).