Working its way up from the back of the class: #15,425 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
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 252 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 3 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
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
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 02:04 UTC26d ago
1
–
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
You won't find a region tag on WE RUST JP extra, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 31.214.143.121:10700 is the address to use.
How dependable is WE RUST JP extra, and is it online at the moment?
At this moment, WE RUST JP extra is offline; the last time it was seen was 8 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 3 October 2026, Rust Server Score saw it for the first time.
What Rust version is WE RUST JP extra on?
You will find WE RUST JP extra on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does WE RUST JP extra wipe, and how often?
WE RUST JP extra has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 26 days 1 hours.
What happens on WE RUST JP extra when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Population
Where does WE RUST JP extra place in the wider field of Rust servers?
Over the last seven days, WE RUST JP extra has #15,425 for player hours, in the top 69% of all ranked servers.
How many players does WE RUST JP extra usually have?
WE RUST JP extra is offline at the moment; the last time it was seen was 8 days 23 hours ago.
Tags and filters
What do WE RUST JP extra's tags stand for?
The game's browser takes its cue from the tags WE RUST JP extra has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Which lists and filters on Rust Server Score show WE RUST JP extra?
Rust Server Score lists that include WE RUST JP extra: Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is WE RUST JP extra set up, and what rules does it keep?
You will find no gather rate in the name of WE RUST JP extra. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map WE RUST JP extra uses?
The game generates the procedural map on WE RUST JP extra at size 4,000 with seed 1586544950. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join WE RUST JP extra?
Enter client.connect 31.214.143.121:10700 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?,v2634,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under 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); standing is the one to work on (F).