On the class lists: F (44), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average0peak 3
Rank#5,889top 27% · #393 in EA
Last wipe11d agobiweekly schedule
Next wipe2d 14hFri 30 Oct, 09:00 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
73/ 100
B−
Holds a respectable place: #5,889 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 116 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
51/ 100
D
Moving up: up 88 places this week.
A term to build on.
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 27% of all ranked servers, top 72% 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····
·······
···F···
·······
····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 Friday 30 October, 09:00 UTC, in 2d 14h.
Its biweekly schedule tag · low confidence
usual gap14.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
Coming wipes
2d 14hFri 30 Oct, 09:00 UTC
9d 0hThu 5 Nov, 19:00 UTCFW
16d 14hFri 13 Nov, 09:00 UTC
30d 14hFri 27 Nov, 09:00 UTC
37d 0hThu 3 Dec, 19:00 UTCFW
44d 14hFri 11 Dec, 09:00 UTC
The first 48 hours of its last wipes
Fri 16 OctThu 1 OctWed 16 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 24 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 09:00 UTC11d ago
2
–
running
0
Thu 1 Oct, 18:55 UTCFW25d ago
4
halved by day 1
14.6 days
0
Wed 16 Sep, 13:05 UTC41d ago
0
–
15.2 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
In Asia, according to its own listing, sits [EA]Japan-Server |PvP|, with the EA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 133.117.73.110:28015 is the address to use.
How dependable is [EA]Japan-Server |PvP|, and is it online at the moment?
Right now, [EA]Japan-Server |PvP| is online. The uptime it reports puts the last restart at about 8 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Is [EA]Japan-Server |PvP| smooth to play on?
It never fell below 81 server fps in the last 48 hours, averaging 116. At its peak, it held 100,693 entities, including buildings, deployables and all else in the world. Up to 2,954 MB of memory was used. Players feel lag when fps drops and entities pile up.
What Rust version is [EA]Japan-Server |PvP| on?
You will find [EA]Japan-Server |PvP| on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does [EA]Japan-Server |PvP| reset?
Too few wipes on [EA]Japan-Server |PvP| are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Friday 30 October at 09:00 UTC. It has been running its current world for 11 days 9 hours. Its tags say it wipes every two weeks.
What happens on [EA]Japan-Server |PvP| when wipe day arrives?
The average peak on its recent wipes was 2 players. The crowd on the latest wipe was largest 24 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 1.
Player count
What position does [EA]Japan-Server |PvP| hold in the rankings?
Over the last seven days, [EA]Japan-Server |PvP| has #5,889 for player hours, in the top 27% of all ranked servers and #393 in Asia.
What does the population on [EA]Japan-Server |PvP| look like?
With 100 slots available, [EA]Japan-Server |PvP| currently has 1 players. Averaging 0 players over seven days, it peaked at 3. Over the last 48 hours, the peak hour was 07:00 UTC, averaging 3 players.
Tags
What is meant by the tags on [EA]Japan-Server |PvP|?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; 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): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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 are the tags [EA]Japan-Server |PvP| publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [EA]Japan-Server |PvP| appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [EA]Japan-Server |PvP| among them: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Server rules
How is [EA]Japan-Server |PvP| set up, and what rules does it keep?
The name of [EA]Japan-Server |PvP| gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [EA]Japan-Server |PvP| uses?
A procedural map of size 4,096 and seed 1337, generated by the game, is what [EA]Japan-Server |PvP| runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
Connecting
What is the way to join [EA]Japan-Server |PvP|?
Enter client.connect 133.117.73.110:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/473S8yCnC7.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,EA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
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
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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.
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 performance (A+); population is the one to work on (F).