Why So Sus
Offline 47.226.85.41:28015 checked 27d ago
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
daily · 1 is bestTop 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
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 1000/ 100
- 79/ 400
- 64/ 245
- 127/ 100
- 165/ 1000
- 19/ 700
Quick answers
Tags and search
Where does Why So Sus appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Why So Sus: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Why So Sus?
gmrust (Game mode): Survival, as standard Rust does it; mp3 (Max players): The slot count is 3; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs164530 (Build): It's on build 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Why So Sus puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server info
Where can you find Why So Sus?
Why So Sus does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 47.226.85.41:28015.
What's the uptime like for Why So Sus?
The server Why So Sus is not reachable at the moment; the last sighting was 27 days ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 20 September 2026.
What is the Rust version for Why So Sus?
On Linux, Why So Sus runs Rust network protocol 2633 and build 164530. The protocol must match to join; Steam will update your game.
Wipe info
How often does Why So Sus wipe?
The wipes recorded for Why So Sus are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 27 days 11 hours ago.
Settings and map
What settings and rules have been applied to Why So Sus?
Its name does not state a gather rate for Why So Sus. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. The server runs Valve's anti-cheat, VAC.
What's the map on Why So Sus?
Why So Sus uses a game-generated procedural map.
Population
How many players are on Why So Sus?
Right now Why So Sus is offline, with its last appearance 27 days ago.
What's Why So Sus's rank among Rust servers?
For player hours in the last seven days, Why So Sus ranks #15,466, within the top 68% of ranked servers.
Getting in
How do you get into Why So Sus?
To join, open Rust, hit F1, and enter client.connect 47.226.85.41:28015. Or click Launch Rust on this page to open the game through Steam and connect.