Rust Data

rustdata.spaceservers157.85.91.86:28853.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.91.86:28852 checked 8m ago

A Shockbyte Rust Server

moddedoxide

Connect

srv = rust.server("157.85.91.86:28853")
print(srv.connect_command)

Right now

srv.summary()
players now 0/75 # 0% full
7-day average 0 # peak 1
rank #12,209 # top 55%
last wipe 26d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75106:0015:0000:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020006:0015:0000:0010:0019:0004: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 27 Sep. 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
15k10k15k20k27 Sep3 Oct8 Oct14 Oct19 Oct28 Oct

Top 55% 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 gap2.1 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctTue 29 SepSun 27 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 00:28 UTC26d ago 2 NaN running 0
1 Tue 29 Sep, 18:00 UTC28d ago 1 halved by day 1 2.3 days 1
2 Sun 27 Sep, 17:41 UTC30d ago 1 halved by day 1 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

6000 · seed 559464932
Map of A Shockbyte Rust Server
map
Procedural Map
size
6000
seed
559464932
Open on RustMaps

Server

srv.info()
address
157.85.91.86:28852
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 00:28 UTC
hostname
–
first seen
27 Sep 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 · 158 on average60/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average57/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average29/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average9/1000

Quick answers

From the figures on this page.

Population

How does A Shockbyte Rust Server compare in the rankings?

Rank #12,209 on seven-day player hours for A Shockbyte Rust Server, within the top 55% of all ranked servers.

How many players does A Shockbyte Rust Server hold at once?

Current row: 0 players on A Shockbyte Rust Server, against 75 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 01:00 UTC is the busiest, at 0 players.

About the server

How smoothly does A Shockbyte Rust Server run?

The 48-hour average is 82 server fps, with a low of 1. Buildings, deployables and all else in the world took the count as high as 199,411 entities. A high of 5,597 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does A Shockbyte Rust Server run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by A Shockbyte Rust Server. Joining needs the same protocol on your game; Steam handles the update.

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

The current sample puts A Shockbyte Rust Server online. Count back 4 hours from its reported uptime to get the last restart. 70 of 168 hours up over the last 7 full days, or 42%. The first row Rust Data holds for it is dated 27 September 2026.

In which location is A Shockbyte Rust Server hosted?

For A Shockbyte Rust Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.91.86:28852 is its address.

Rules, settings, map

Which settings and rules does A Shockbyte Rust Server run?

You will not find a gather rate in the string A Shockbyte Rust Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has A Shockbyte Rust Server selected?

Size 6,000, seed 559464932: the procedural map on A Shockbyte Rust Server, 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?

A Shockbyte Rust Server wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 26 days 5 hours ago, and that is the one in play.

What is wipe day on A Shockbyte Rust Server like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 45 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Lists and tags

Where does A Shockbyte Rust Server appear among Rust Data lists and filters?

The Rust Data lists that A Shockbyte Rust Server fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

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

These tags are published by A Shockbyte Rust Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp75 (Max players): Slot count: 75; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into A Shockbyte Rust Server?

In Rust, F1 opens the console: type client.connect 157.85.91.86:28852. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp75
Max players Slot count: 75.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 33,161 players 11,582 servers online