On the class lists: C+ (65), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average0peak 1
Rank#5,434top 24%
Last wipe13d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
20/ 100
F
A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,434 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 232 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
43/ 100
F
Slipped a little: down 797 places this week. Nothing a good wipe can't fix.
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.
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 24% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
16 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WW·WW
WW·F··W
WW·WW·W
···W·W·
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Thu 22 OctSat 17 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in, with 1 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 02:51 UTC7d ago
1+1 queue
–
running
0
Sat 17 Oct, 17:34 UTC11d ago
1
✓ held half
4.4 days
1
Thu 15 Oct, 18:10 UTC13d ago
1
–
2 days
1
Sun 11 Oct, 17:18 UTC17d ago
1
✓ held half
4 days
0
Sun 11 Oct, 09:22 UTC17d ago
1
–
0.3 days
0
Fri 9 Oct, 08:42 UTC19d ago
1
✓ held half
2 days
1
Thu 8 Oct, 06:25 UTC20d ago
1
–
1.1 days
0
Tue 6 Oct, 22:24 UTC22d ago
1
–
1.3 days
0
Tue 6 Oct, 05:55 UTC22d ago
1
–
0.7 days
1
Mon 5 Oct, 05:02 UTC23d ago
1
–
1 days
0
Sun 4 Oct, 04:07 UTC24d ago
1
–
1 days
0
Thu 1 Oct, 18:39 UTCFW27d ago
1
✓ held half
2.4 days
0
Tue 29 Sep, 22:04 UTC29d ago
1
–
1.9 days
1
Mon 28 Sep, 21:43 UTC30d ago
1
–
1 days
0
Sun 27 Sep, 17:23 UTC31d ago
1
–
1.2 days
0
Sat 26 Sep, 02:27 UTC33d ago
1
–
1.6 days
1
Thu 24 Sep, 17:57 UTC34d ago
1
–
1.4 days
0
Thu 24 Sep, 01:38 UTC35d ago
1
–
0.7 days
0
Wed 23 Sep, 18:19 UTC35d ago
1
–
0.3 days
0
Wed 23 Sep, 07:20 UTC35d ago
1
–
0.5 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
You'll find no region listed by A Shockbyte Rust Server. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 51.81.176.81:28015.
How dependable is A Shockbyte Rust Server, and is it online at the moment?
You can join now: A Shockbyte Rust Server is online. The uptime it reports puts the last restart at about 4 days 22 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does A Shockbyte Rust Server run?
The average over the last 48 hours was 232 server fps, and it never went below 194. At its peak, it held 65,222 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,359 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is A Shockbyte Rust Server on?
Rust network protocol 2635 and build 168909 on Linux is what A Shockbyte Rust Server runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does A Shockbyte Rust Server wipe its map?
No next wipe can be predicted for A Shockbyte Rust Server, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 13 days 9 hours.
What should you expect from wipe day on A Shockbyte Rust Server?
Recent wipes have peaked at 1 players on average. 0 hours after the latest wipe began the crowd peaked, and 1 more were in the queue. Half the peak held until the next wipe in 100% of its recent wipes.
Player count
Where does A Shockbyte Rust Server place in the wider field of Rust servers?
In the top 24% of all ranked servers, A Shockbyte Rust Server sits at #5,434 for player hours over the last seven days.
How many players does A Shockbyte Rust Server usually have?
Right now, 0 players are on A Shockbyte Rust Server, which has 1 slots. It peaked at 1 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 17:00 UTC, with 1 players.
Tags and filters
What do A Shockbyte Rust Server's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags A Shockbyte Rust Server publishes, and the game's server browser reads them. 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 A Shockbyte Rust Server?
Rust Server Score lists that include A Shockbyte Rust Server: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is A Shockbyte Rust Server set up, and what rules does it keep?
You will find no gather rate in the name of A Shockbyte Rust Server. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map A Shockbyte Rust Server uses?
A procedural map of size 3,500 and seed 471471404, generated by the game, is what A Shockbyte Rust Server runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to A Shockbyte Rust Server?
To connect, start Rust, press F1, and type client.connect 51.81.176.81:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).