RS-8165Modded server
A Shockbyte.test
Online 198.244.225.80:23917 checked 11m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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.
Wipes
| Wiped | Peak | Crowd | Lasted | Players 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.
Quick answers
From the figures on this page.
Population
How many players are usually on A Shockbyte.test?
A Shockbyte.test is showing 0 players on 40 slots right now. A seven-day average of 0 players was reached, peaking at 1. At 17:00 UTC it was busiest in the last 48 hours, averaging 1 players.
What is the ranking of A Shockbyte.test?
The last seven days of player hours place A Shockbyte.test at #8,165, in the top 38% of ranked servers.
Tags, lists, and filters
Where does A Shockbyte.test show up in Top Rust Servers lists and filters?
These Top Rust Servers lists include A Shockbyte.test: Top 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.
What is the meaning of the tags on A Shockbyte.test?
gmrust (Game mode): Standard survival, as in Rust; mp40 (Max players): Player slots: 40; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs167781 (Build): Running game build 167781; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, so it is listed as Modded are the tags A Shockbyte.test publishes, and the game's server browser reads them. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Rules, settings, and map
Which map is running on A Shockbyte.test?
The map on A Shockbyte.test is procedural, size 3,000, seed 50000, and generated by the game. You can look at the map on RustMaps from this page, because size and seed determine the map.
What does A Shockbyte.test run for rules and settings?
The name A Shockbyte.test does not state a gather rate. The group limit is the game's default of 8 players. You play survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.
Server info
What Rust version is A Shockbyte.test on?
A Shockbyte.test uses Rust network protocol 2634 and build 167781 with Linux as its system. The protocol must match for you to join; Steam will update your game.
How well does A Shockbyte.test perform?
Over the last two days, it ran at an average of 204 server fps, minimum 11. Its entity count reached 48,670, including buildings, deployables and all other objects. Memory usage peaked at 3,334 MB. A climbing entity count and low fps are the source of the lag players feel.
Where can A Shockbyte.test be found?
A region is not published by A Shockbyte.test. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. It answers at 198.244.225.80:23917.
What is the uptime of A Shockbyte.test?
Right now, A Shockbyte.test is up and running. Going by its reported uptime, it restarted about 9 hours ago. It spent 48 of the last 48 hours online across 2 days, giving 100% uptime. The first time Top Rust Servers saw it was on 18 October 2026.
Wipe cycle
What happens on wipe day on A Shockbyte.test?
Across recent wipes, the busiest times averaged 1 players. 1 hours after the latest wipe, the crowd hit its peak.
When does A Shockbyte.test wipe?
The record holds too few wipes to determine A Shockbyte.test's pattern. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The present world has been live since 2 days 21 hours ago.
How to join
How can I connect to A Shockbyte.test?
Use the console: open Rust, press F1, and type client.connect 198.244.225.80:23917. Or simply click Launch Rust here; it opens the game through Steam and connects you.