Station XX-13656 · no signal
A Shockbyte Rust Server
Offline 157.85.85.150:27701 checked 2d ago
- Players now
- 1/ 40
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #13,656
- top 61%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 40 slots
- Motion · 24 h
- M –not enough readings
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 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
- usual gap
- 10 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 14:45 UTC2d ago | M0.0■steady | 1 | – | running | 1 | |
| Fri 16 Oct, 14:30 UTC12d ago | M0.0■steady | 1 | held half | 10 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on A Shockbyte Rust Server?
Generated by the game, the map on A Shockbyte Rust Server is procedural, size 3,750 with seed 50001. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.
Which settings and rules apply on A Shockbyte Rust Server?
You will find no gather rate in the name of A Shockbyte Rust Server. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on A Shockbyte Rust Server right now?
A reading taken now finds A Shockbyte Rust Server offline; the most recent activity was 2 days 20 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 1.
How does A Shockbyte Rust Server rank against other Rust servers?
The last seven days of player hours place A Shockbyte Rust Server at #13,656, in the top 61% of all ranked servers.
Server facts
How reliably does A Shockbyte Rust Server stay online?
As recorded now, A Shockbyte Rust Server is not reachable, the last contact having been 2 days 20 hours ago. 3 of 168 hours in the last 7 full days were up time, 2% of the total. On 15 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does A Shockbyte Rust Server run from?
A region is not published by A Shockbyte Rust Server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 157.85.85.150:27701 is the address it uses.
What build of Rust does A Shockbyte Rust Server use?
On Linux, A Shockbyte Rust Server runs Rust network protocol 2635 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on A Shockbyte Rust Server?
1 players, on average, was the busiest crowd at its recent wipes. 2 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.
On what timetable does A Shockbyte Rust Server run its wipes?
Too few wipes of A Shockbyte Rust Server are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 2 days 22 hours.
Tags
What do the server tags on A Shockbyte Rust Server mean?
The game's server browser reads the tags A Shockbyte Rust Server publishes: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does A Shockbyte Rust Server appear?
You will find A Shockbyte Rust Server on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it 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.
How to join
How do you connect to A Shockbyte Rust Server?
Enter client.connect 157.85.85.150:27701 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://maps.rustmaps.com/288/417b7458f246482e91539144a56c34cc/procedural__3750_drMQAYKm_EK40DaOXyvzNg.map.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.