On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 4
Rank#5,261top 24%
Last wipe21h agoweekly schedule
Next wipe6d 2hTue 3 Nov, 21:47 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,261 on player hours.
Uptimehours on the list, last 48
92/ 100
A
Good attendance: on the list 44 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 107 server fps on average.
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.
A steady term.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 24% 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
from its schedule tag
Next wipe Tuesday 3 November, 21:47 UTC, in 6d 2h.
Its weekly schedule tag · low confidence
Coming wipes
6d 2hTue 3 Nov, 21:47 UTC
8d 0hThu 5 Nov, 19:00 UTCFW
13d 2hTue 10 Nov, 21:47 UTC
20d 2hTue 17 Nov, 21:47 UTC
27d 2hTue 24 Nov, 21:47 UTC
34d 2hTue 1 Dec, 21:47 UTC
36d 0hThu 3 Dec, 19:00 UTCFW
41d 2hTue 8 Dec, 21:47 UTC
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 21:47 UTC21h ago
–
–
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
In what location does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 sit?
The name of [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 points to Asia, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 1.34.205.31:28015.
How dependable is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27, and is it online at the moment?
Right now, [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 is online. According to its reported uptime, the last restart was about 46 minutes ago. It was up 24 of 24 hours over the last 1 full day, which is 100% of the time. The first sighting by Rust Server Score was on 26 October 2026.
Is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 smooth to play on?
It averaged 107 server fps over the last 48 hours, with a low of 58. Up to 123,236 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,919 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 running?
Rust network protocol 2635 and build 168909 on Windows is what [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 wipe its map?
Too few wipes on [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 are recorded to confirm the schedule, so its tag guides the prediction. Tuesday 3 November at 21:47 UTC is the date set for its next wipe. The world it runs now was created 21 hours. Wipes are scheduled weekly, according to its tags.
Player numbers
What position does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 hold in the rankings?
Over the last seven days, [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 has #5,261 for player hours, in the top 24% of all ranked servers.
How many players does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 usually have?
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 is showing 0 players right now, with 100 slots in total. Averaging 1 players over seven days, it peaked at 4. The busiest time in the last 48 hours was 06:00 UTC, with an average of 4 players.
Lists and filters
What do [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27's tags stand for?
You'll see [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^q (Premium): Joining requires premium status on Rust; ^o (Oxide): Plugin framework: Oxide (uMod) in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
These Rust Server Score lists count [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 among them: 2x Rust servers, graded, Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Weekly ^w, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 2x.
Map and rules
How is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 set up, and what rules does it keep?
The name of [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 points to a 2x gather rate. 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. Under Community in the server browser you will find this community server. Oxide plugins are running on it. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. Joining requires premium status on Rust. The server runs Valve's anti-cheat, VAC.
A procedural map of size 3,500 and seed 1955700823, generated by the game, is what [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
Enter client.connect 1.34.205.31:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. Joining requires premium status on Rust. The website for this server is https://discord.com/invite/6dHFqxsRYZ.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^v,^q,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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
^q
PremiumJoining requires premium status on Rust.
^o
OxidePlugin framework: Oxide (uMod).
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 steady term. Strongest in performance (A+); population is the one to work on (F).