On the class lists: D (51), with population over 48 hours and no performance mark.
Players now0/ 750% full
7-day average6peak 23
Rank#1,458top 7%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
8/ 100
F
A quiet classroom so far: 6 of 75 on average. Plenty of space to grow.
Standingrank on player hours
93/ 100
A
Well up the rankings: #1,458 on player hours.
Uptimehours on the list, last 48
21/ 100
F
Attendance needs work: on the list only 10 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 189 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
41/ 100
F
Slipped a little: down 254 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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
No five-minute samples in the last two hours.
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. Ranked on player hours over the last seven days.
Attendance: the wipe record
15 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W··W···
W··W···
W··FW··
W··W··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
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 gap3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak15players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Mon 26 OctSat 24 OctThu 22 Oct
Players each hour, from the hour of the wipe. The latest peaked at 7, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 16:40 UTC2d ago
7
–
running
0
Sat 24 Oct, 04:12 UTC4d ago
15
✓ held half
2.5 days
5
Thu 22 Oct, 14:08 UTC6d ago
23
–
1.6 days
1
Sun 18 Oct, 12:57 UTC10d ago
19
✓ held half
4 days
8
Wed 14 Oct, 22:00 UTC13d ago
18
✓ held half
3.6 days
6
Sun 11 Oct, 11:41 UTC17d ago
26
✓ held half
3.4 days
3
Thu 8 Oct, 15:00 UTC20d ago
18
✓ held half
2.9 days
2
Mon 5 Oct, 14:25 UTC23d ago
16
✓ held half
3 days
3
Fri 2 Oct, 14:18 UTC26d ago
15
✓ held half
3 days
1
Thu 1 Oct, 21:48 UTCFW26d ago
15
–
0.7 days
0
Mon 28 Sep, 14:54 UTC30d ago
16
halved by day 2
3.3 days
4
Thu 24 Sep, 14:24 UTC34d ago
18
halved by day 2
4 days
3
Mon 21 Sep, 14:35 UTC37d ago
13
✓ held half
3 days
2
Thu 17 Sep, 14:20 UTC41d ago
14
✓ held half
4 days
1
Mon 14 Sep, 14:34 UTC44d ago
10
✓ held half
3 days
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
You'll find no region listed by A Shockbyte Rust Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 157.85.89.136:28015.
How dependable is A Shockbyte Rust Server, and is it online at the moment?
At this moment, A Shockbyte Rust Server is offline; the last time it was seen was 37 hours ago. The uptime it reports puts the last restart at about 11 hours ago. For the last 7 full days, it was up 137 of 168 hours, or 82% of the time. 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 189 server fps, and it never went below 134. Up to 121,126 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,610 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does A Shockbyte Rust Server sit?
The server A Shockbyte Rust Server is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does A Shockbyte Rust Server wipe its map?
There is no next wipe to predict on A Shockbyte Rust Server, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 2 days 1 hours.
What should you expect from wipe day on A Shockbyte Rust Server?
The average peak on its recent wipes was 15 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Player numbers
Where does A Shockbyte Rust Server place in the wider field of Rust servers?
In the top 7% of all ranked servers, A Shockbyte Rust Server sits at #1,458 for player hours over the last seven days.
What does the population on A Shockbyte Rust Server look like?
A Shockbyte Rust Server is offline at the moment; the last time it was seen was 37 hours ago. Averaging 6 players over seven days, it peaked at 23. Over the last 48 hours, the peak hour was 20:00 UTC, averaging 1 players.
Tags and filters
How should you read the tags on A Shockbyte Rust Server?
You'll see A Shockbyte Rust Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp75 (Max players): 75 slots are available; 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): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here 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 A Shockbyte Rust Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count A Shockbyte Rust Server among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
How is A Shockbyte Rust Server set up, and what rules does it keep?
Nothing in the name of A Shockbyte Rust Server states a gather rate. 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. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
A Shockbyte Rust Server runs which map?
A procedural map of size 4,500 and seed 1057629265, generated by the game, is what A Shockbyte Rust Server runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to A Shockbyte Rust Server?
To connect, start Rust, press F1, and type client.connect 157.85.89.136:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp75
Max players75 slots are available.
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
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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+); population is the one to work on (F).