A Shockbyte.test
Offline 198.244.225.80:23917 checked 7d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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.
Li4Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 08:19 UTC10d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on A Shockbyte.test?
At their busiest, its recent wipes averaged 1 players. 1 hours into the latest wipe, player numbers topped out.
What is the wipe schedule on A Shockbyte.test?
The record of A Shockbyte.test's wipes is not yet long enough to show a rhythm. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 10 days 17 hours ago.
Population
How busy is A Shockbyte.test?
Last seen 7 days 9 hours ago, A Shockbyte.test is offline at the moment.
How does A Shockbyte.test rank against other Rust servers?
The top 69% of ranked servers includes A Shockbyte.test, at #15,452 for player hours over the last seven days.
Settings and rules
Which map does A Shockbyte.test run?
A Shockbyte.test runs a procedural map of size 3,000 with seed 50000, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on A Shockbyte.test?
No gather rate appears in the name A Shockbyte.test. Groups can contain up to 8 players, the default in the game. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does A Shockbyte.test run?
The build on A Shockbyte.test is Rust network protocol 2634 and build 167781, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.
Is A Shockbyte.test online, and how reliable is it?
Offline at the moment: A Shockbyte.test was last seen 7 days 9 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. Rust Heatmap has had it on record since 18 October 2026.
Where is A Shockbyte.test located?
A region is not published for A Shockbyte.test. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. You can reach it at 198.244.225.80:23917.
Tags
Which Rust Heatmap lists and filters include A Shockbyte.test?
Modded Rust servers, by live population are the Rust Heatmap lists that A Shockbyte.test fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What do the server tags on A Shockbyte.test mean?
gmrust (Game mode): Rust survival, standard rules; mp40 (Max players): Slot count: 40; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs167781 (Build): This build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The game is changed by settings or plugins, so it sits under Modded are the tags A Shockbyte.test publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join A Shockbyte.test?
To join by console, open it with F1 in Rust and enter client.connect 198.244.225.80:23917. Or press Launch Rust on this page, which connects you through Steam.