On the class lists: F (32), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,318top 69%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,318 on player hours.
Uptimehours on the list, last 48
48/ 100
D
Attendance needs work: on the list only 23 of the last 48 hours.
Performanceserver fps, last 48 hours
17/ 100
F
Needs to work on its frame rate: 10 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
49/ 100
D
Slipped a little: down 193 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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 21 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region tag appears for WE RUST JP extra, 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 45.140.129.79:10600.
How reliable is WE RUST JP extra, and is it up?
You cannot join now: WE RUST JP extra is offline, last seen 25 hours ago. The uptime it reports puts the last restart at about 26 hours ago. It was up 156 of 168 hours over the last 7 full days, which is 93% of the time. It was first seen by Rust Server Score on 21 October 2026.
How well does WE RUST JP extra run?
It never fell below 9 server fps in the last 48 hours, averaging 10. Up to 94,138 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 2,214 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does WE RUST JP extra sit?
Rust network protocol 2635 and build 168909 on Windows is what WE RUST JP extra runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does WE RUST JP extra reset?
There are too few wipes on record for WE RUST JP extra to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 25 days 10 hours.
Player count
Where does WE RUST JP extra sit among Rust servers?
In the top 69% of all ranked servers, WE RUST JP extra sits at #15,318 for player hours over the last seven days.
What does the population on WE RUST JP extra look like?
WE RUST JP extra is offline at the moment; the last time it was seen was 25 hours ago. A seven-day average of 0 players applies here.
Lists and filters
What is meant by the tags on WE RUST JP extra?
You'll see WE RUST JP extra tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^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 in the browser, which picks them up from the server. 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 WE RUST JP extra appear in the Rust Server Score lists and filters?
These Rust Server Score lists count WE RUST JP extra among them: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does WE RUST JP extra enforce, and what are its settings?
The name of WE RUST JP extra gives no gather rate. The default of 8 players applies as the group cap. 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. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
WE RUST JP extra runs which map?
WE RUST JP extra runs a game-generated procedural map at size 4,000, seed 1586544950. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto WE RUST JP extra?
Enter client.connect 45.140.129.79:10600 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.
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 momentum (D); population is the one to work on (F).