Rust Data

rustdata.spaceservers157.85.85.209:22476.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.85.209:22475 checked 9m ago

A Shockbyte Rust Server

moddedoxide

Connect

srv = rust.server("157.85.85.209:22476")
print(srv.connect_command)

Right now

srv.summary()
players now 0/1 # 0% full
7-day average 0 # peak –
rank #15,420 # top 69%
last wipe 19d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123404:0013:0022:0008:0017:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020004:0013:0022:0008:0017:0002: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 Oct9 Oct16 Oct22 Oct28 Oct

Top 69% 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 rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 2

The first 48 hours of its last wipes

Thu 8 OctFri 2 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 8 Oct, 15:43 UTC19d ago 1 NaN running 0
1 Fri 2 Oct, 13:50 UTC25d ago 1 halved by day 2 6.1 days 0
2 Mon 28 Sep, 14:31 UTC29d ago 1 held half 4 days 0
3 Sun 27 Sep, 18:32 UTC30d ago 1 NaN 0.8 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

3750 · seed 309970230
Map of A Shockbyte Rust Server
map
Procedural Map
size
3750
seed
309970230
Open on RustMaps

Server

srv.info()
address
157.85.85.209:22475
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
8 Oct 2026, 15:54 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 · 160 on average39/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average47/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average18/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average6/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average7/1000

Quick answers

From the figures on this page.

Population data

How does A Shockbyte Rust Server compare in the rankings?

Over the last seven days A Shockbyte Rust Server sits at #15,420 on player hours, in the top 69% of ranked servers.

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

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

Server data

What does performance look like on A Shockbyte Rust Server?

The 48-hour average is 104 server fps, with a low of 82. The entity count peaked at 83,580, covering buildings, deployables and the rest of the world. A high of 4,340 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. The protocol has to match before you can join, and Steam does the updating.

How reliable is A Shockbyte Rust Server, and is it online now?

Online is the state at the latest refresh for A Shockbyte Rust Server. A restart about 37 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 27 September 2026.

Where does A Shockbyte Rust Server sit?

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.85.209:22475 is its address.

Settings and map

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

The name A Shockbyte Rust Server carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. 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,750 with seed 309970230, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does A Shockbyte Rust Server wipe?

A Shockbyte Rust Server wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 19 days 11 hours ago.

What is wipe day on A Shockbyte Rust Server like?

Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. In the wipes where it did not hold, half was lost by day 2.

Tags, lists

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.

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; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into A Shockbyte Rust Server?

In Rust, F1 opens the console: type client.connect 157.85.85.209:22475. 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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp1
Max players Slot count: 1.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 37,139 players 11,636 servers online