Why So Sus
Offline NA 47.226.85.41:28015 checked 2d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 01:29 UTC2d ago | 0 | – | running | 0 |
| Thu 8 Oct, 02:21 UTC20d ago | 2 | held half | 18 days | 2 |
| Wed 7 Oct, 06:20 UTC21d ago | 2 | – | 0.8 days | 0 |
| Tue 6 Oct, 05:40 UTC22d ago | 2 | – | 1 days | 0 |
| Wed 30 Sep, 22:41 UTC27d ago | 2 | halved by day 1 | 5.3 days | 0 |
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- 8/15
- 0/100
- 0/16
- 0/16
- 2/100
- 11/100
Quick answers
from the figures on this pageWipe timing
What happens on Why So Sus when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. By day 1 it fell below half when it didn't.
When does Why So Sus wipe?
No next wipe can be predicted for Why So Sus, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 2 days 4 hours ago.
Lists and filters
How should you read the tags on Why So Sus?
These are the tags Why So Sus publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): 3 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^d (Combat training): Loot is handed to you on this training server for aim and PvP work; ^i (Battlefield): Check: mode. Battlefield, with kits and high rates for quick fights; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server; NA (North America): Its browser listing: North America. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Why So Sus?
Rust Metrics lists featuring Why So Sus: Modded Rust servers, checked live, Aim training servers, live readings, Rust battlefield servers: check the readings and North America: server readout. Check: filters. On the server list it appears under these: Region: North America; Type: Vanilla and Modded; Server tag: Vanilla ^v, Combat training ^d, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Population
What position does Why So Sus hold among Rust servers?
Ranked by seven-day player hours, Why So Sus sits at #15,419 and #1,540 in North America, inside the top 69%.
What is the population on Why So Sus?
Why So Sus is not responding; status offline, last seen 2 days 4 hours ago. Check: player average. 0 over the last seven days.
Server details
Which location does Why So Sus run from?
Why So Sus gives North America as its location, with the NA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 47.226.85.41:28015.
What Rust version is Why So Sus on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Why So Sus. Matching protocol is required to join. Let Steam update your game.
How reliable is Why So Sus, and is it online now?
Check: connection. Why So Sus is offline at this moment. Last contact was 2 days 4 hours ago. Uptime for the last 7 full days: 2 of 168 hours, or 1%. Reading: first seen 25 September 2026, recorded by Rust Metrics.
Map and rules
How is Why So Sus configured, and what rules are in force?
Check: gather rate. The name Why So Sus does not state one. No limit is set beyond the default. Groups take up to 8 players. combat training, practice for aim and PvP, loot provided — that is the game mode. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. It describes itself as vanilla. The meaning given: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Why So Sus?
Procedural map on Why So Sus, made by the game's generator.
Connection
How do you connect to Why So Sus?
Check: join. Open Rust, press F1, then enter client.connect 47.226.85.41:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.