Working its way up from the back of the class: #13,255 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 59 places this week.
A term to build on.
Even marks across the subjects, from F to D.
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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 58% 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
Which region is A Shockbyte x Discord Production Rust Server based in?
A Shockbyte x Discord Production Rust Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 157.85.87.141:29497.
Is A Shockbyte x Discord Production Rust Server up, and how steady is its uptime?
The server is down: A Shockbyte x Discord Production Rust Server is offline now, with the last sighting 36 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 22 September 2026.
What Rust version is A Shockbyte x Discord Production Rust Server on?
You will find A Shockbyte x Discord Production Rust Server on Rust network protocol 2633 and build 165217, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does A Shockbyte x Discord Production Rust Server reset?
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. 36 days 7 hours have passed since this world was made.
Population
Where does A Shockbyte x Discord Production Rust Server sit among Rust servers?
In the top 58% of all ranked servers, A Shockbyte x Discord Production Rust Server sits at #13,255 for player hours over the last seven days.
How many players does A Shockbyte x Discord Production Rust Server usually have?
It has been 36 days 7 hours since A Shockbyte x Discord Production Rust Server was last seen, and it is offline right now.
Lists and filters
What do A Shockbyte x Discord Production Rust Server's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags A Shockbyte x Discord Production Rust Server publishes, and the game's server browser reads them. 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.
Which Rust Server Score filters and lists feature A Shockbyte x Discord Production Rust Server?
These Rust Server Score lists count A Shockbyte x Discord Production Rust Server among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on A Shockbyte x Discord Production Rust Server?
You will find no gather rate in the name of A Shockbyte x Discord Production Rust Server. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
A Shockbyte x Discord Production Rust Server runs which map?
The game generates a procedural map for A Shockbyte x Discord Production Rust Server.
How to join
How should you connect to A Shockbyte x Discord Production Rust Server?
To connect, start Rust, press F1, and type client.connect 157.85.87.141:29497. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 term to build on. Even marks across the subjects, from F to D.