Working its way up from the back of the class: #16,728 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
23/ 100
F
Lost ground: down 9,024 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
Thu 24 Sep, 15:54 UTC34d ago
1
–
running
1
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 PVE Rust Server 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. You can connect at 162.43.50.87:28015.
How dependable is PVE Rust Server JP, and is it online at the moment?
The server is down: PVE Rust Server JP is offline now, with the last sighting 27 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 24 September 2026, Rust Server Score saw it for the first time.
What Rust version is PVE Rust Server JP on?
The server PVE Rust Server JP is on Rust network protocol 2633 and build 165217 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does PVE Rust Server JP wipe its map?
The record holds too few of PVE Rust Server JP's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 34 days 3 hours.
What should you expect from wipe day on PVE Rust Server JP?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe.
Player count
Where does PVE Rust Server JP place in the wider field of Rust servers?
Over the last seven days, PVE Rust Server JP has #16,728 for player hours, in the top 70% of all ranked servers.
What does the population on PVE Rust Server JP look like?
PVE Rust Server JP is offline at the moment; the last time it was seen was 27 days 23 hours ago.
Lists and filters
What do PVE Rust Server JP's tags stand for?
You'll see PVE Rust Server JP tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): 4 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does PVE Rust Server JP appear in the Rust Server Score lists and filters?
Rust Server Score lists that include PVE Rust Server JP: Best community servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does PVE Rust Server JP enforce, and what are its settings?
Nothing in the name of PVE Rust Server JP states a 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. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map PVE Rust Server JP uses?
The game generates the procedural map on PVE Rust Server JP at size 3,500 with seed 50000. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to PVE Rust Server JP?
To connect, start Rust, press F1, and type client.connect 162.43.50.87:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max players4 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from F to F.