Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
No rank history yet.
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
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h.
The 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 JP kokuu Server PvE V2, but the name suggests Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 162.43.36.122:28015.
How dependable is JP kokuu Server PvE V2, and is it online at the moment?
The server is down: JP kokuu Server PvE V2 is offline now, with the last sighting 46 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is JP kokuu Server PvE V2 running?
You will find JP kokuu Server PvE V2 on Rust network protocol 2633 and build 163493, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does JP kokuu Server PvE V2 reset?
the force wipe gives the basis for estimating JP kokuu Server PvE V2's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 56 days 1 hours. The tags show a monthly wipe schedule.
Player numbers
Is JP kokuu Server PvE V2 a busy server?
JP kokuu Server PvE V2 is offline at the moment; the last time it was seen was 46 days 9 hours ago.
Lists and filters
How should you read the tags on JP kokuu Server PvE V2?
The game's browser takes its cue from the tags JP kokuu Server PvE V2 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts5 (Group limit): No team may go above 5; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163493 (Build): This runs on build 163493; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^p (PvE): The danger comes from the world, not from other players. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature JP kokuu Server PvE V2?
These Rust Server Score lists count JP kokuu Server PvE V2 among them: Best community servers, graded, Rust PvE servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v and PvE ^p; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does JP kokuu Server PvE V2 enforce, and what are its settings?
Nothing in the name of JP kokuu Server PvE V2 states a gather rate. The limit for a group is 5 players. pve is the mode here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map JP kokuu Server PvE V2 uses?
A procedural map, generated by the game, is what JP kokuu Server PvE V2 runs.
Getting in
How do you get onto JP kokuu Server PvE V2?
To connect, start Rust, press F1, and type client.connect 162.43.36.122:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^m,^v,^p,gmrust,cs163493,ts5
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts5
Group limitNo team may go above 5.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163493
BuildThis runs on build 163493.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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.
Not enough figures yet to write a report. Check back after a few days on the list.