Offline 198.244.225.80:23917 checked 7d ago
A Shockbyte.test
Connect
srv = rust.server("198.244.225.80:23918")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 08:19 UTC10d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- address
- 198.244.225.80:23917
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 08:19 UTC
- hostname
- –
- first seen
- 18 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 36/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 56/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population data
What position does A Shockbyte.test take in the server rankings?
Player hours over seven days put A Shockbyte.test at #15,452, in the top 69% of the ranked set.
How many players does A Shockbyte.test hold at once?
A Shockbyte.test returns no live count at this refresh, having last been seen 7 days 12 hours ago.
About the server
What is the Rust version on A Shockbyte.test?
The build is Rust network protocol 2634 and build 167781 on Linux, run by A Shockbyte.test. Steam updates your game for you, but the protocol must match to join.
Is A Shockbyte.test up, and what does its uptime show?
A Shockbyte.test is offline at this refresh; the last response came 7 days 12 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 18 October 2026.
Which location does A Shockbyte.test run from?
There is no region published for A Shockbyte.test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 198.244.225.80:23917 is its address.
Map and rules
Which settings and rules does A Shockbyte.test run?
You will not find a gather rate in the string A Shockbyte.test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on A Shockbyte.test?
Size 3,000, seed 50000: the procedural map on A Shockbyte.test, 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
When does A Shockbyte.test wipe, and how often?
The record for A Shockbyte.test holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 10 days 20 hours ago.
On A Shockbyte.test, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Tags, lists
Where does A Shockbyte.test appear among Rust Data lists and filters?
The Rust Data lists that A Shockbyte.test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on A Shockbyte.test hold?
Read by the game's server browser, the tags A Shockbyte.test publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join A Shockbyte.test?
Enter client.connect 198.244.225.80:23917 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.