Rust Data

rustdata.spaceservers157.85.85.155:28016.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.85.155:28015 checked 9m ago

A Shockbyte Rust Server

Connect

srv = rust.server("157.85.85.155:28016")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040022:0007:0016:0000:0009:0019: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 3 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
15k10k15k20k3 Oct7 Oct12 Oct16 Oct24 Oct28 Oct

Top 45% 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 gap10.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5

The first 48 hours of its last wipes

Sat 24 OctMon 5 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 24 Oct, 12:46 UTC4d ago 2 NaN running 0
1 Mon 5 Oct, 15:32 UTC23d ago 1 halved by day 4 18.9 days 0
2 Sat 3 Oct, 13:37 UTC25d ago 1 halved by day 1 2.1 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

2500 · seed 754335138
Map of A Shockbyte Rust Server
map
Procedural Map
size
2500
seed
754335138
Open on RustMaps

Server

srv.info()
address
157.85.85.155:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 13:20 UTC
hostname
–
first seen
3 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 553 on average548/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average357/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 297 on average44/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average37/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average118/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average128/300

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does A Shockbyte Rust Server rank?

Over the last seven days A Shockbyte Rust Server sits at #10,055 on player hours, in the top 45% of ranked servers.

How full does A Shockbyte Rust Server run?

The sample now reads 0 players for A Shockbyte Rust Server, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 2.

About the server

What does performance look like on A Shockbyte Rust Server?

The 48-hour average is 196 server fps, with a low of 143. Buildings, deployables and all else in the world took the count as high as 32,280 entities. A high of 4,094 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on A Shockbyte Rust Server?

Rust network protocol 2635 and build 168909 on Linux is what A Shockbyte Rust Server runs. 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 9 hours ago is what its reported uptime implies. 84 of 168 hours up over the last 7 full days, or 50%. Its earliest recorded date in Rust Data is 3 October 2026.

In which location is A Shockbyte Rust Server hosted?

There is no region published for A Shockbyte Rust Server. 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.85.155:28015.

Rules, settings, map

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

The name A Shockbyte Rust Server carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has A Shockbyte Rust Server selected?

Size 2,500, seed 754335138: the procedural map on A Shockbyte Rust Server, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

On what schedule does A Shockbyte Rust Server wipe?

A Shockbyte Rust Server wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 4 days 7 hours ago.

What is wipe day on A Shockbyte Rust Server like?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 5 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.5.

Lists and tags

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

On Rust Data, A Shockbyte Rust Server appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

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): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join A Shockbyte Rust Server?

Enter client.connect 157.85.85.155:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

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 The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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.

Rust Data 73,970 players 11,800 servers online