On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 1250% full
7-day average0peak –
Rank#15,335top 69%
Last wipe6d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 125 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,335 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: 253 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 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
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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
In what location does A Shockbyte x Discord Production Rust Server sit?
A Shockbyte x Discord Production Rust Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 203.16.163.188:26048.
How dependable is A Shockbyte x Discord Production Rust Server, and is it online at the moment?
Right now, A Shockbyte x Discord Production Rust Server is online. The uptime it reports puts the last restart at about 5 days 22 hours ago. It was up 99% of the time over the last 5 full days, 119 of 120 hours. On 23 October 2026, Rust Server Score saw it for the first time.
Does A Shockbyte x Discord Production Rust Server perform well?
It averaged 253 server fps over the last 48 hours, with a low of 235. At its peak, it held 8,245 entities, including buildings, deployables and all else in the world. Up to 2,683 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is A Shockbyte x Discord Production Rust Server running?
Rust network protocol 2635 and build 168909 on Linux is what A Shockbyte x Discord Production Rust Server runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does A Shockbyte x Discord Production Rust Server wipe, and how often?
There are too few wipes on record for A Shockbyte x Discord Production Rust Server to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 6 days.
Player numbers
Where does A Shockbyte x Discord Production Rust Server place in the wider field of Rust servers?
Over the last seven days, A Shockbyte x Discord Production Rust Server has #15,335 for player hours, in the top 69% of all ranked servers.
Is A Shockbyte x Discord Production Rust Server a busy server?
With 125 slots available, A Shockbyte x Discord Production Rust Server currently has 0 players. Over the past seven days, the average player count was 0.
Tags and filters
What is meant by the tags on A Shockbyte x Discord Production Rust Server?
You'll see A Shockbyte x Discord Production Rust Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp125 (Max players): The server holds 125 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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): RakNet handles it, the game's default network layer; $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 x Discord Production Rust Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include A Shockbyte x Discord Production 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 week.
Rules and settings
How is A Shockbyte x Discord Production Rust Server set up, and what rules does it keep?
Nothing in the name of A Shockbyte x Discord Production Rust Server 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. 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 x Discord Production Rust Server uses?
The game generates the procedural map on A Shockbyte x Discord Production Rust Server at size 1,500 with seed 50000. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to A Shockbyte x Discord Production Rust Server?
Enter client.connect 203.16.163.188:26048 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 asmp125,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp125
Max playersThe server holds 125 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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).