Working its way up from the back of the class: #15,967 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
43/ 100
F
Slipped a little: down 2,302 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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 2 Oct. 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, top 93% in EA. 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
The EA tag on [KR/JP] vanilla PVE puts it in Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 222.119.158.32:28015 is the address to use.
How dependable is [KR/JP] vanilla PVE, and is it online at the moment?
The server is down: [KR/JP] vanilla PVE is offline now, with the last sighting 25 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 2 October 2026.
What Rust version is [KR/JP] vanilla PVE on?
The server [KR/JP] vanilla PVE is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does [KR/JP] vanilla PVE wipe, and how often?
[KR/JP] vanilla PVE 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. 26 days 2 hours have passed since this world was made.
Population
What position does [KR/JP] vanilla PVE hold in the rankings?
Over the last seven days, [KR/JP] vanilla PVE has #15,967 for player hours, in the top 70% of all ranked servers and #484 in Asia.
Is [KR/JP] vanilla PVE a busy server?
The last sighting of [KR/JP] vanilla PVE was 25 days 12 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on [KR/JP] vanilla PVE?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^p (PvE): Players do not fight one another here; the world is the danger; EA (East Asia): You will find it under East Asia in the browser are the tags [KR/JP] vanilla PVE 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 [KR/JP] vanilla PVE appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [KR/JP] vanilla PVE: 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: Vanilla ^v and PvE ^p; Group limit: 5 or more.
Map and rules
What settings and rules apply on [KR/JP] vanilla PVE?
Nothing in the name of [KR/JP] vanilla PVE states a gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. VAC, Valve's anti-cheat, is enabled.
[KR/JP] vanilla PVE runs which map?
[KR/JP] vanilla PVE runs a game-generated procedural map at size 4,000, seed 774762328. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto [KR/JP] vanilla PVE?
To connect, start Rust, press F1, and type client.connect 222.119.158.32:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^v,EA,^p,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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 (F); standing is the one to work on (F).