Live coverage · Rust server
Offline Why So Sus is not on the server list right now. The figures below are from when it was last seen, 37d ago.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 68% 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.
Too few wipes are recorded for Why So Sus to establish a pattern. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 38 days 4 hours have passed since this world was generated.
On Rust Live Stats, Why So Sus is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.
These are the tags Why So Sus makes public: gmrust (Game mode): The game mode is standard Rust survival; mp3 (Max players): Slots: 3; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2633 (Protocol): The server runs protocol 2633, so match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Why So Sus is not online at the moment, having last been seen 37 days 17 hours ago.
On player hours for the past seven days, Why So Sus sits at #15,466, inside the top 68% of ranked servers.
The name Why So Sus carries no gather rate. The default applies: 8 players to a group. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
A procedural map, generated by the game, runs on Why So Sus.
There is no region from Why So Sus. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 47.226.85.41:28015 is its address.
Why So Sus operates on Linux with Rust network protocol 2633 and build 164530. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, Why So Sus is down, last seen 37 days 17 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. Rust Live Stats has tracked it since 20 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 47.226.85.41:28015.