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.
AveragePeak
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 Friday 30 October, 07:31 UTC, in 2d 2h.
Weekly: 7 days after its last 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
Which region is [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 based in?
You'll see [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 119.71.209.86:28015.
How reliable is [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11, and is it up?
You cannot join now: [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 is offline, last seen 44 days 14 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 13 September 2026.
What Rust version is [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 on?
The server [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 is on Rust network protocol 2633 and build 163493 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 wipe its map?
The estimate for [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11's next wipe comes from weekly: 7 days after its last wipe. Expect the next wipe on Friday 30 October at 07:31 UTC. The world it runs now was created 46 days 21 hours. The tags carry a weekly wipe schedule.
Population
What does the population on [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 look like?
It has been 44 days 14 hours since [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11?
gmvanilla (Game mode): Survival, vanilla style; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): You will find it under East Asia in the browser are the tags [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 publishes, and the game's server browser reads them. 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 [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11: Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Players now: At least 10.
Map and rules
How is [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 set up, and what rules does it keep?
Nothing in the name of [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The plugin count runs to Oxide. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 uses?
A procedural map, generated by the game, is what [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11 runs.
How to join
How do you get onto [KR/JP]나히다서버/초보/자원밀도2배/WIPE 09.11?
Enter client.connect 119.71.209.86:28015 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 asmp150,ptrak,$r?,v2633,^w,^v,EA,gmvanilla,cs163493,ts8,^o
Game
gmvanilla
Game modeSurvival, vanilla style.
mp150
Max playersThe server holds 150 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
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
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
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.
Not enough figures yet to write a report. Check back after a few days on the list.