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 16 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
A Shockbyte x Discord Production Rust Server's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 12 days 9 hours have passed since this world was generated.
These are the Rust Live Stats lists A Shockbyte x Discord Production Rust Server fits: Live Rust community servers. Under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks it appears on the server list.
These are the tags A Shockbyte x Discord Production Rust Server makes public: gmrust (Game mode): Standard survival, in the Rust style; mp125 (Max players): 125 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of A Shockbyte x Discord Production Rust Server's 125 slots are filled right now. Across the past week the average was 0 players.
Player hours over seven days put A Shockbyte x Discord Production Rust Server at #15,339, in the top 69% of all ranked servers.
No gather rate appears in the name A Shockbyte x Discord Production Rust Server. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. 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 1,500 with seed 50000, generated by the game, runs on A Shockbyte x Discord Production Rust Server. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on A Shockbyte x Discord Production Rust Server states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 157.85.86.59:25684.
Server fps averaged 238 over the last 48 hours, with a low of 230. Entity count reached 8,326: buildings, deployables and the rest of the world. Up to 3,062 MB of memory was used. Players experience lag when fps is low and the entity count climbs.
A Shockbyte x Discord Production Rust Server operates on Linux with Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam takes care of updating it.
A Shockbyte x Discord Production Rust Server is up and running at this moment. Based on the uptime it reports, the last restart was about 2 days 18 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. On 16 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 157.85.86.59:25684 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.