On the class lists: D (51), with population over 48 hours and no performance mark.
Players now22/ 3007% full
7-day average40peak 171
Rank#437top 2%
Last wipe6d agoweekly schedule
Next wipe20hFri 30 Oct, 08:31 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
13/ 100
F
A quiet classroom so far: 40 of 300 on average. Plenty of space to grow.
Standingrank on player hours
98/ 100
A+
Well up the rankings: #437 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
50/ 100
D
Slows down under load at times: 30 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
54/ 100
D
Moving up: up 36 places this week.
A term to build on.
Strongest in standing (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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 2% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
····W··
····W··
····W··
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 08:31 UTC, in 20h.
Every Friday at 08:31 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak142players, last three wipes
crowd held0%else halves by day 4
Coming wipes
20hFri 30 Oct, 08:31 UTC
7d 7hThu 5 Nov, 19:00 UTCFW
7d 20hFri 6 Nov, 08:31 UTC
14d 20hFri 13 Nov, 08:31 UTC
21d 20hFri 20 Nov, 08:31 UTC
28d 20hFri 27 Nov, 08:31 UTC
35d 7hThu 3 Dec, 19:00 UTCFW
35d 20hFri 4 Dec, 08:31 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 171, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 08:31 UTC6d ago
171
–
running
4
Fri 16 Oct, 08:31 UTC13d ago
129+39 queue
halved by day 5
7 days
3
Fri 9 Oct, 08:31 UTC20d ago
125
halved by day 4
7 days
0
Fri 2 Oct, 08:31 UTC27d ago
153+68 queue
halved by day 3
7 days
0
Fri 25 Sep, 08:31 UTC34d ago
133+3 queue
halved by day 4
7 days
0
Fri 18 Sep, 08:31 UTC41d ago
181
halved by day 6
7 days
4
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 Japan Tokyo - Limited Raid Hours |3x|PvP|JP based in?
No region tag appears for Japan Tokyo - Limited Raid Hours |3x|PvP|JP, but the name suggests Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 162.222.17.4:30040.
Is Japan Tokyo - Limited Raid Hours |3x|PvP|JP up, and how steady is its uptime?
Right now, Japan Tokyo - Limited Raid Hours |3x|PvP|JP is online. The uptime it reports puts the last restart at about 12 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does Japan Tokyo - Limited Raid Hours |3x|PvP|JP perform well?
The average over the last 48 hours was 30 server fps, and it never went below 30. Up to 185,989 entities were in the world, covering buildings, deployables and the rest. Up to 6,283 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is Japan Tokyo - Limited Raid Hours |3x|PvP|JP on?
Rust network protocol 2635 and build 168909 on Linux is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Japan Tokyo - Limited Raid Hours |3x|PvP|JP reset?
Wipes come every Friday at 08:31 UTC on Japan Tokyo - Limited Raid Hours |3x|PvP|JP. Expect the next wipe on Friday 30 October at 08:31 UTC. 6 days 3 hours have passed since this world was made. The tags carry a weekly wipe schedule.
What should you expect from wipe day on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
Across its recent wipes, the busiest moments averaged 142 players. Peak numbers came 4 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Player numbers
Where does Japan Tokyo - Limited Raid Hours |3x|PvP|JP place in the wider field of Rust servers?
In the top 2% of all ranked servers, Japan Tokyo - Limited Raid Hours |3x|PvP|JP sits at #437 for player hours over the last seven days.
What does the population on Japan Tokyo - Limited Raid Hours |3x|PvP|JP look like?
Japan Tokyo - Limited Raid Hours |3x|PvP|JP is showing 22 players right now, with 300 slots in total. It peaked at 171 and averaged 40 players over the last seven days. Over the last 48 hours, the peak hour was 14:00 UTC, averaging 78 players.
Lists and filters
How should you read the tags on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
The game's browser takes its cue from the tags Japan Tokyo - Limited Raid Hours |3x|PvP|JP has set: gmrust (Game mode): Rust survival, played by the standard rules; mp300 (Max players): The server holds 300 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 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; ^w (Weekly): Wipes come once a week; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Japan Tokyo - Limited Raid Hours |3x|PvP|JP appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Japan Tokyo - Limited Raid Hours |3x|PvP|JP among them: 3x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 3x; Players now: At least 10; Average players: 25+ on average.
Server rules
How is Japan Tokyo - Limited Raid Hours |3x|PvP|JP set up, and what rules does it keep?
Going by its name, Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs 3x gather. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Japan Tokyo - Limited Raid Hours |3x|PvP|JP uses?
The game generates the procedural map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP at size 3,800 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
Getting in
How do you get onto Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
To connect, start Rust, press F1, and type client.connect 162.222.17.4:30040. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/AH7FXJ2Xet.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2635,^z,^y,^w,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp300
Max playersThe server holds 300 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 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
^w
WeeklyWipes come once a week.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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 standing (A+); wipes are the one to work on (F).