Why So Sus
Offline 47.226.85.41:28015 checked 38d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Quick answers
Population
How does Why So Sus rank against other Rust servers?
The last seven days of player hours place Why So Sus at #15,466, within the top 68% of all ranked servers.
How busy is Why So Sus?
We have no live count for Why So Sus right now. It was last seen 38 days 11 hours ago.
Tags
What do the server tags on Why So Sus mean?
These are the tags Why So Sus publishes, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp3 (Max players): 3 slots are available; ts8 (Group limit): This is the game default: at most 8 per team; v2633 (Protocol): To join, your game must match protocol 2633; cs164530 (Build): This server runs game build 164530; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): Plugins or settings change the game; it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Why So Sus?
These Rust Population lists include Why So Sus: Modded Rust servers, counted. Look for it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Wipe schedule
What is the wipe schedule on Why So Sus?
Too few wipes are on record for Why So Sus to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 38 days 22 hours ago, that is how long the current world has stood.
Map and rules
Which map does Why So Sus run?
The map on Why So Sus is procedural, made by the game.
What are the rules and settings on Why So Sus?
Nothing in Why So Sus's name says how gather works. No limit is set beyond the standard 8 players per group. You get survival here, gather, build and raid, as in the standard game. Combat between players, raids included, is permitted. Modded is its browser category: plugins or settings change the game. You will find Oxide running as plugins. You play with Valve's anti-cheat on: VAC.
About the server
Which version of Rust does Why So Sus run?
On Linux, Why So Sus runs Rust network protocol 2633 and build 164530. Your game needs the same protocol to join; Steam takes care of updating it.
Is Why So Sus online, and how reliable is it?
We last saw Why So Sus 38 days 11 hours ago, and it is offline now. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. It was first seen by Rust Population on 20 September 2026.
Where is Why So Sus located?
Nothing published by Why So Sus states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 47.226.85.41:28015.
How to join
How do I join Why So Sus?
Open the console with F1 in Rust and enter client.connect 47.226.85.41:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.