Rust Data

rustdata.spaceservers157.85.87.206:21439.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.87.206:21438 checked 9m ago

A Shockbyte Rust Server

moddedoxide

Connect

srv = rust.server("157.85.87.206:21439")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 5
rank #7,491 # top 34%
last wipe 7d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123414:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020014:0023:0008:0017:0003:0012:00

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

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k13 Oct16 Oct19 Oct23 Oct26 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Wed 21 OctFri 16 OctTue 13 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 24 hours in, with 1 in the queue.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 21 Oct, 15:53 UTC7d ago 5+1 queue NaN running 0
1 Fri 16 Oct, 21:14 UTC12d ago 4 held half 4.8 days 0
2 Tue 13 Oct, 15:23 UTC15d ago 4 held half 3.2 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.

display(srv.map, srv.info())

Map

3500 · seed 833938114
Map of A Shockbyte Rust Server
map
Procedural Map
size
3500
seed
833938114
Open on RustMaps

Server

srv.info()
address
157.85.87.206:21438
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 15:53 UTC
hostname
–
first seen
13 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 149 on average183/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average128/100
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average83/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average23/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average28/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average267/700

Quick answers

From the figures on this page.

Population

How does A Shockbyte Rust Server compare in the rankings?

Player hours over seven days put A Shockbyte Rust Server at #7,491, in the top 34% of the ranked set.

How full does A Shockbyte Rust Server run?

A Shockbyte Rust Server reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 5.

About the server

How well does A Shockbyte Rust Server perform?

Server fps over the last 48 hours averages 111; the floor is 34. Buildings, deployables and all else in the world took the count as high as 72,318 entities. A high of 3,383 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on A Shockbyte Rust Server?

The build is Rust network protocol 2635 and build 167781 on Linux, run by A Shockbyte Rust Server. The protocol has to match before you can join, and Steam does the updating.

How reliable is A Shockbyte Rust Server, and is it up?

The current sample puts A Shockbyte Rust Server online. Count back 2 days 21 hours from its reported uptime to get the last restart. Uptime of 97% across the last 7 full days: 163 hours of 168. Its earliest recorded date in Rust Data is 13 October 2026.

In which location is A Shockbyte Rust Server hosted?

For A Shockbyte Rust Server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 157.85.87.206:21438.

Map and rules

Which rules apply on A Shockbyte Rust Server, and what settings?

No gather rate appears in the name: A Shockbyte Rust Server. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has A Shockbyte Rust Server loaded?

A Shockbyte Rust Server runs a procedural map of size 3,500 with seed 833938114, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

When does A Shockbyte Rust Server wipe, and how often?

Irregular wipe times on A Shockbyte Rust Server leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 7 days 21 hours ago.

On A Shockbyte Rust Server, what happens on wipe day?

Across recent wipes the busiest point averaged 4 players. A peak 24 hours into the latest wipe, plus 1 waiting in the queue. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Which lists on Rust Data hold A Shockbyte Rust Server, and which filters?

The Rust Data lists that A Shockbyte Rust Server fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on A Shockbyte Rust Server?

The game's server browser reads these tags from A Shockbyte Rust Server: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into A Shockbyte Rust Server?

The manual route: launch Rust, F1, then client.connect 157.85.87.206:21438. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 72,948 players 11,836 servers online