Fig. 1Players on A Shockbyte Rust ServerRG-S1362-01 · Sheet 1 of 10
Fig. 2
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S1362-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 6% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S1362-03 · Sheet 3 of 10
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak19players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sat 24 OctThu 22 OctSun 18 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 15, 20 hours in.
ScheduleExpected wipesRG-S1362-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 16:40 UTC1d ago
–
–
running
0
Sat 24 Oct, 04:12 UTC3d ago
15
held half
2.5 days
5
Thu 22 Oct, 14:08 UTC5d ago
23
–
1.6 days
1
Sun 18 Oct, 12:57 UTC9d ago
19
held half
4 days
8
Wed 14 Oct, 22:00 UTC13d ago
18
held half
3.6 days
6
Sun 11 Oct, 11:41 UTC16d ago
26
held half
3.4 days
3
Thu 8 Oct, 15:00 UTC19d ago
18
held half
2.9 days
2
Mon 5 Oct, 14:25 UTC22d ago
16
held half
3 days
3
Fri 2 Oct, 14:18 UTC25d ago
15
held half
3 days
1
Thu 1 Oct, 21:48 UTCFW26d ago
15
–
0.7 days
0
Mon 28 Sep, 14:54 UTC29d ago
16
halved by day 2
3.3 days
4
Thu 24 Sep, 14:24 UTC33d ago
18
halved by day 2
4 days
3
Mon 21 Sep, 14:35 UTC36d ago
13
held half
3 days
2
Thu 17 Sep, 14:20 UTC40d ago
14
held half
4 days
1
Mon 14 Sep, 14:34 UTC43d ago
10
held half
3 days
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.
Table 1Wipe logRG-S1362-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for A Shockbyte Rust Server, and is it up?
The current state of A Shockbyte Rust Server is offline, with the last sighting 17 hours ago. Counted from its reported uptime, the last restart was about 11 hours ago. For the last 7 full days the record is 156 of 168 hours up, 93% of the time. First seen by Rust Graphs on 13 September 2026.
2.
What does the recorded performance of A Shockbyte Rust Server show?
185 server fps on average over the last 48 hours, and never under 124. Counted at its highest: 121,126 entities, buildings, deployables and the rest of the world included. 5,891 MB is the memory peak. Players feel low fps and a climbing entity count as lag.
3.
In which location is A Shockbyte Rust Server hosted?
A region is not published by A Shockbyte Rust Server. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 157.85.89.136:28015 is its address.
4.
What Rust version is recorded for A Shockbyte Rust Server?
On Linux, A Shockbyte Rust Server runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.
Counts
5.
What player count is recorded on A Shockbyte Rust Server?
A Shockbyte Rust Server is not responding at the latest refresh; the last record of it online is 17 hours ago. Averaged across seven days, the player count is 6, with a peak of 23. The 48-hour peak falls at 15:00 UTC, averaging 5 players.
6.
What rank has been recorded for A Shockbyte Rust Server?
Player hours over seven days place A Shockbyte Rust Server at #1,362, within the top 6% of ranked servers.
Wipe times
7.
What happens on A Shockbyte Rust Server on the day of a wipe?
The recent wipes averaged a busiest count of 19 players. 20 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.
8.
What wipe schedule has been recorded for A Shockbyte Rust Server?
No next wipe can be predicted for A Shockbyte Rust Server: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 29 hours ago.
Settings
9.
Which rules and settings are recorded for A Shockbyte Rust Server?
The name of A Shockbyte Rust Server records no gather rate. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Community is its tab in the server browser. Anti-cheat: VAC, from Valve, is on.
10.
On which map is A Shockbyte Rust Server played?
Size 4,500 with seed 1057629265: that is the procedural map A Shockbyte Rust Server runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Filters
11.
On Rust Graphs, which lists and filters contain A Shockbyte Rust Server?
On Rust Graphs, A Shockbyte Rust Server is placed in these lists: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
12.
Which meaning is attached to each tag on A Shockbyte Rust Server?
gmrust (Game mode): Standard survival, as Rust plays; mp75 (Max players): The slot count is 75; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded are the tags A Shockbyte Rust Server publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
13.
By what method do you join A Shockbyte Rust Server?
Enter client.connect 157.85.89.136:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.
NotesAnswered from the figuresRG-S1362-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeStandard survival, as Rust plays.
mp75
Max playersThe slot count is 75.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolTo join, your game must be on protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
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.