Skip to the page
RUST ANALYTICS
LIVE45,373PLY11,592SRV
QUOTE 198.244.225.80:23917 Online checked 6m ago

A Shockbyte.test

moddedoxide
Players · last
0/ 40
+024h
0% full
Day range 0 1
7-day avg 0 peak 1
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 40
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak 1
Rank
#8,187
top 38%
Rank · 7d ago
–
not ranked a week ago
Last wipe
2d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
9
player hours, last seven days
Map
3000
Procedural Map · seed 50000
First seen
18 Oct 2026
no hostname published

Players

AveragePeak
00.250.50.75100:0009:0018:0003:0012:0021:00

Hourly average and peak, UTC. Busiest hour of the two days: 1 players.

Server performance

010020030040000:0009:0018:0003:0012:0021: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 18 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k18 Oct19 Oct20 Oct

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

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
1
players, last three wipes

The first 48 hours of its last wipes

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
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 08:19 UTC2d ago 1 – running 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1ShockRust | Blue | NoLimitno group limit · 130 on average33/400+3+10.7%
2МИНИ-КАРТА 2Х | STORM | FPS+ 17.10EU · groups of 8+ · weekly · 109 on average129/100+2+1.6%
3RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 20.10EU · groups of 16+ · weekly · 106 on average35/225+12+54.6%
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 17.10EU · groups of 16+ · monthly · 83 on average18/1000−1−7.0%
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 18.10EU · groups of 16+ · monthly · 73 on average45/700−27−37.4%
6404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 20.10EU · groups of 16+ · monthly · 72 on average110/700+110

Quick answers

from the figures on this page

Server Rules

How is A Shockbyte.test configured in terms of rules and settings?

No gather rate is given in the name of A Shockbyte.test. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. VAC is active.

What is the current map on A Shockbyte.test?

The map on A Shockbyte.test is procedural, size 3,000, with seed 50000, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.

Player Count

What position does A Shockbyte.test hold in the server rankings?

In the top 38% of all ranked servers, A Shockbyte.test is #8,187 on player hours over the last seven days.

What is the population on A Shockbyte.test?

0 of 40 slots on A Shockbyte.test are filled at the moment. The mean over the last seven days is 0 players, reaching 1 at its highest. At 17:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.

Wipe Schedule

How does A Shockbyte.test handle wipe day?

Recent wipes at this server drew an average peak of 1 players. On the latest wipe, 1 hours after the wipe, the crowd peaked.

On what cycle does A Shockbyte.test wipe?

The record holds too few of A Shockbyte.test's wipes to establish its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 2 days 14 hours.

Server Info

What is the location of A Shockbyte.test?

For A Shockbyte.test, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 198.244.225.80:23917.

Is A Shockbyte.test performing well?

The last 48 hours average 208 server fps, the low being 11. The entity count reached 48,670, covering buildings, deployables and all else in the world. The memory ceiling reached 3,334 MB. What players feel as lag is low fps together with a rising entity count.

A Shockbyte.test runs which version of Rust?

The build is Rust network protocol 2634 and build 167781 on Linux, running on A Shockbyte.test. Joining requires the same protocol on your game, which Steam updates.

What is the uptime and reliability of A Shockbyte.test?

Online at this moment: A Shockbyte.test. 2 hours ago is when it last restarted, judging by the uptime it reports. Availability of 100% over the last 1 full day: it was online for 24 of 24 hours. 18 October 2026 is when Rust Analytics first saw it.

Tags and Rankings

What is the meaning of the tags on A Shockbyte.test?

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167781 (Build): It runs build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded listing applies: plugins or settings change play, which A Shockbyte.test publishes. The top of this page and the tags both show its players now, its queue and when its world was made.

On Rust Analytics, which lists and filters feature A Shockbyte.test?

On Rust Analytics, A Shockbyte.test matches these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Joining the Server

What is the process to join A Shockbyte.test?

Type client.connect 198.244.225.80:23917 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp40
Max players Capacity: 40 slots.
ts8
Group limit Team size stays at the game default of 8.
v2634
Protocol Protocol 2634: matching game versions are required to join.
cs167781
Build It runs build 167781.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code The region code is absent.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The Modded listing applies: plugins or settings change play.

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.