On the class lists: D (49), with population over 48 hours and no performance mark.
Players now1/ 3000% full
7-day average4peak 22
Rank#1,553top 7% · #619 in EU
Last wipe6d agoweekly schedule
Next wipe17hFri 30 Oct, 14:59 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 4 of 300 on average. Plenty of space to grow.
Standingrank on player hours
93/ 100
A
Well up the rankings: #1,553 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 147 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
60/ 100
C
Moving up: up 301 places this week.
A fair term, with more to come.
Strongest in performance (A+); wipes are 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 7% of all ranked servers, top 21% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
····W··
····W··
····W··
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 14:59 UTC, in 17h.
Every Friday at 14:59 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak17players, last three wipes
crowd held0%else halves by day 3
Coming wipes
17hFri 30 Oct, 14:59 UTC
6d 21hThu 5 Nov, 19:00 UTCFW
7d 17hFri 6 Nov, 14:59 UTC
14d 17hFri 13 Nov, 14:59 UTC
21d 17hFri 20 Nov, 14:59 UTC
28d 17hFri 27 Nov, 14:59 UTC
34d 21hThu 3 Dec, 19:00 UTCFW
35d 17hFri 4 Dec, 14:59 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 22, 26 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 14:59 UTC6d ago
22
–
running
0
Fri 16 Oct, 14:59 UTC13d ago
20
halved by day 3
7 days
0
Fri 9 Oct, 14:59 UTC20d ago
10
halved by day 6
7 days
0
Fri 2 Oct, 14:59 UTC27d ago
18
halved by day 5
7 days
2
Fri 25 Sep, 14:59 UTC34d ago
17
halved by day 3
7 days
0
Fri 18 Sep, 14:59 UTC41d ago
15
halved by day 1
7 days
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
EU · groups of 300+ · 2x · weekly · 131 on average
9 / 100
Quick answers
from the figures on this page
Server details
Which region is CYBERSHOKE | #1 Vanilla (x2) based in?
In Europe, according to its own listing, sits CYBERSHOKE | #1 Vanilla (x2), with the EU tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 62.122.215.125:28015 is the address to use.
How reliable is CYBERSHOKE | #1 Vanilla (x2), and is it up?
You can join now: CYBERSHOKE | #1 Vanilla (x2) is online. According to its reported uptime, the last restart was about 16 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does CYBERSHOKE | #1 Vanilla (x2) perform well?
It never fell below 114 server fps in the last 48 hours, averaging 147. At its peak, it held 101,667 entities, including buildings, deployables and all else in the world. At its highest, it used 3,240 MB of memory. When fps is low and entities climb, that is lag to players.
What Rust version is CYBERSHOKE | #1 Vanilla (x2) on?
You will find CYBERSHOKE | #1 Vanilla (x2) on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does CYBERSHOKE | #1 Vanilla (x2) wipe, and how often?
Wipes come every Friday at 14:59 UTC on CYBERSHOKE | #1 Vanilla (x2). Friday 30 October at 14:59 UTC is the date set for its next wipe. It has been running its current world for 6 days 6 hours. The tags carry a weekly wipe schedule.
What happens on CYBERSHOKE | #1 Vanilla (x2) when wipe day arrives?
Recent wipes have peaked at 17 players on average. Peak numbers came 26 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 3.
Player count
Where does CYBERSHOKE | #1 Vanilla (x2) sit among Rust servers?
Over the last seven days, CYBERSHOKE | #1 Vanilla (x2) has #1,553 for player hours, in the top 7% of all ranked servers and #619 in Europe.
What does the population on CYBERSHOKE | #1 Vanilla (x2) look like?
Right now, 1 players are on CYBERSHOKE | #1 Vanilla (x2), which has 300 slots. Averaging 4 players over seven days, it peaked at 22. Over the last 48 hours, the peak hour was 16:00 UTC, averaging 3 players.
Lists and filters
What do CYBERSHOKE | #1 Vanilla (x2)'s tags stand for?
You'll see CYBERSHOKE | #1 Vanilla (x2) tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp300 (Max players): The server holds 300 slots; ts24 (Group limit): No team may go above 24; 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): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EU (Europe): In the server browser it appears under Europe in the browser, which picks them up from the server. 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 CYBERSHOKE | #1 Vanilla (x2) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count CYBERSHOKE | #1 Vanilla (x2) among them: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Server rules
Which rules does CYBERSHOKE | #1 Vanilla (x2) enforce, and what are its settings?
The name of CYBERSHOKE | #1 Vanilla (x2) points to a 2x gather rate. You can play in groups of up to 24 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. 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.
Can you tell me which map CYBERSHOKE | #1 Vanilla (x2) uses?
The game generates the procedural map on CYBERSHOKE | #1 Vanilla (x2) at size 4,000 with seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Connecting
How should you connect to CYBERSHOKE | #1 Vanilla (x2)?
To connect, start Rust, press F1, and type client.connect 62.122.215.125:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://cybershoke.net/rust.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2635,^w,^v,EU,gmrust,cs168909,ts24,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp300
Max playersThe server holds 300 slots.
ts24
Group limitNo team may go above 24.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EU
EuropeIn the server browser it appears under Europe.
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 fair term, with more to come. Strongest in performance (A+); wipes are the one to work on (F).