RS-15466Modded server
Why So Sus
Offline 47.226.85.41:28015 checked 22d 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
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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Player activity
What is the typical player count on Why So Sus?
Why So Sus is offline at this moment; the last signal was 22 days 23 hours ago.
What is the ranking of Why So Sus?
Ranked #15,466 on seven-day player hours, Why So Sus is in the top 68% of all ranked servers.
Tags and filters
Where does Why So Sus appear among the Top Rust Servers lists and filters?
These Top Rust Servers lists count Why So Sus among their servers: Top modded Rust servers. These filters bring it up on the server list: 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): Standard survival, as in Rust; mp3 (Max players): There are 3 slots; ts8 (Group limit): At most 8 per team, as standard in the game; v2633 (Protocol): To join, your game must be on protocol 2633; cs164530 (Build): Running game build 164530; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): Region code not set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): It appears in Modded, as plugins or settings modify the game are the tags Why So Sus publishes, and the game's server browser reads them. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Rules, settings, and map
What is the map on Why So Sus?
Why So Sus uses a procedural map, which the game generates.
What does Why So Sus run for rules and settings?
No gather rate is given in the name Why So Sus. Groups use the default maximum of 8 players. survival is the game mode, gather, build and raid in the standard game. Player versus player combat and raiding are enabled. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are loaded. The server runs with VAC on.
Server info
What Rust version is Why So Sus on?
Rust network protocol 2633 and build 164530 is what Why So Sus runs, on Linux. The protocol must match for you to join; Steam will update your game.
Where can Why So Sus be found?
There is no region published by Why So Sus. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 47.226.85.41:28015 is its address.
Is Why So Sus currently online?
The server Why So Sus is down at the moment, with its last appearance 22 days 23 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. The first time Top Rust Servers saw it was on 20 September 2026.
Wipe details
When does Why So Sus wipe?
Too few wipes are recorded for Why So Sus to establish a rhythm. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. Its world was last replaced 23 days 10 hours ago.
Connection
What is the process to join Why So Sus?
To connect manually, open the console with F1 and type client.connect 47.226.85.41:28015. Or click Launch Rust on this page to open Rust through Steam and connect directly.