LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 25% of all ranked servers, and #347 of the quad servers (top 42%). Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The current map
Thursday 22 October 2026, 07:30 UTC
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.
Recent wipes on this server averaged a peak of 1 players at their busiest. The crowd on the latest wipe peaked 0 hours in.
Too few wipes are recorded for A Shockbyte Rust Server to establish a pattern. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world dates from 5 days 15 hours.
These are the Rust Live Stats lists A Shockbyte Rust Server fits: Live Rust community servers. Under the filters Type: Community (not modded, not official) and No plugins at all; Game mode: Softcore; Group limit: Quad; Last wipe: In the last week it appears on the server list.
These are the tags A Shockbyte Rust Server makes public: gmsoftcore (Game mode): Softcore ruleset: an easier game; mp2 (Max players): 2 slots are available; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 2 players on A Shockbyte Rust Server, out of 2 slots. The seven-day average is 0 players, with a peak of 2. Peak hour over 48 hours: 22:00 UTC, at 2 players on average.
Player hours over seven days put A Shockbyte Rust Server at #5,618, in the top 25% of all ranked servers. Within the quad group, its position is #347.
No gather rate appears in the name A Shockbyte Rust Server. The limit is 4 players to a group (quad). It runs softcore, The easier Facepunch mode, where you keep some loot. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is enabled: Valve's anti-cheat.
A procedural map of 4,000 with seed 50000, generated by the game, runs on A Shockbyte Rust Server. Same size, same seed, same map: RustMaps has it, reachable from this page.
There is no region from A Shockbyte Rust Server. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 157.85.90.208:28355 is its address.
Server fps averaged 110 over the last 48 hours, with a low of 36. Buildings, deployables and everything else in the world added up to a maximum of 95,095 entities. The highest memory usage was 3,467 MB. Players experience lag when fps is low and the entity count climbs.
A Shockbyte Rust Server operates on Linux with Rust network protocol 2635 and build 168909. To join, your game must use the same protocol; Steam handles the update for you.
Right now A Shockbyte Rust Server is online. The uptime it reports puts the last restart at about 41 minutes ago. 96 of 96 hours were online in the last 4 full days, giving 100% uptime. On 22 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 157.85.90.208:28355 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you. It is full at the moment, so a queue is likely.