Rust Server TrendsSeismic network · station log
Recording Stations11,798 Players68,197 Active3,637 Wipes · 3 h131 48 h

Station XX-12385 · no signal

A Shockbyte x Discord Production Rust Server

Offline 157.85.85.81:27900 checked 3d ago

Connect
Players now
0/ 40
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#12,385
top 56%
Last wipe
23d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-12385 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 40 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep2 Oct8 Oct13 Oct19 Oct28 Oct

Top 56% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

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 gap
4.5 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 3

The first 48 hours of its last wipes

Mon 5 OctSun 27 SepSat 26 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 45 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 5 Oct, 18:53 UTC23d ago M0.3rising 2 – running 0
Sun 27 Sep, 15:39 UTC31d ago M0.0rising 2 halved by day 3 8.1 days 1
Sat 26 Sep, 19:39 UTC32d ago M0.5rising 3 – 0.8 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 553 on average
513/ 575
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
315/ 400
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 297 on average
42/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 296 on average
35/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 272 on average
91/ 150
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 253 on average
111/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on A Shockbyte x Discord Production Rust Server?

The procedural map on A Shockbyte x Discord Production Rust Server is size 3,000 with seed 315848369, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which 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. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. The server has VAC off, Valve's anti-cheat.

Live population

How many players are recorded on A Shockbyte x Discord Production Rust Server right now?

No players are recorded on A Shockbyte x Discord Production Rust Server at this moment; it is offline, and the last sighting was 3 days 7 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.

How does A Shockbyte x Discord Production Rust Server rank against other Rust servers?

Over the last seven days, A Shockbyte x Discord Production Rust Server recorded enough player hours to reach #12,385 worldwide, placing it in the top 56% of all ranked servers.

Server details

How reliably does A Shockbyte x Discord Production Rust Server stay online?

A Shockbyte x Discord Production Rust Server is down at the moment; the last recorded contact was 3 days 7 hours ago. It was up 1% of the time across the last 7 full days: 2 of 168 hours. 26 September 2026 is when Rust Server Trends first recorded it.

Which region does A Shockbyte x Discord Production Rust Server run from?

No region is published by A Shockbyte x Discord Production Rust Server. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 157.85.85.81:27900 is the address it uses.

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. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on A Shockbyte x Discord Production Rust Server?

On average, the busiest point of its recent wipes drew 2 players. 45 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 3.

On what timetable does A Shockbyte x Discord Production Rust Server run its wipes?

No next wipe can be predicted for A Shockbyte x Discord Production Rust Server, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 23 days 2 hours is how long the current world has been running.

Tags

What do the server tags on A Shockbyte x Discord Production Rust Server mean?

Tags published by A Shockbyte x Discord Production Rust Server and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does A Shockbyte x Discord Production Rust Server appear?

You will find A Shockbyte x Discord Production Rust Server on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

What steps get you onto A Shockbyte x Discord Production Rust Server?

To join, enter client.connect 157.85.85.81:27900 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp40
Max players 40 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.