Live coverage · NA
Offline Why So Sus is not on the server list right now. The figures below are from when it was last seen, 3d 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 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Coming up · wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The current map
Monday 26 October 2026, 01:29 UTC
Wipe
Thursday 8 October 2026, 02:21 UTC
Wipe
Wednesday 7 October 2026, 06:20 UTC
Wipe
Tuesday 6 October 2026, 05:40 UTC
Wipe
Wednesday 30 September 2026, 22:41 UTC
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.
Recent wipes on this server averaged a peak of 1 players at their busiest. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. On those occasions it fell below half by day 1.
No next wipe can be predicted for Why So Sus, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. This world dates from 3 days 15 hours.
The Rust Live Stats lists that include Why So Sus are Modded Rust servers live now, Aim training servers, live now, Rust battlefield servers, live now and North America Rust servers, live. These filters on the server list bring it up: 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 week.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp3 (Max players): 3 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^d (Combat training): Practise aim and PvP here, and the loot is handed to you; ^i (Battlefield): High rates and kits make for fast PvP on this battlefield server; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded: plugins or changed settings alter the game; NA (North America): The server browser places this server under North America, which Why So Sus publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Why So Sus reads offline at the moment; the last sighting was 3 days 15 hours ago. Across the past week the average was 0 players.
North America places Why So Sus at #1,503; overall it is #15,341, inside the top 69% of ranked servers, by seven-day player hours.
The name Why So Sus carries no gather rate. No custom limit is set, so groups hold the default 8 players. combat training applies here, aim and PvP practice, loot handed out. The server browser files it under Modded: plugins or settings alter the game. Plugins run here: Oxide. By its own label it is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. VAC is enabled: Valve's anti-cheat.
Why So Sus uses a procedural map, which the game generates.
By its own NA tag, Why So Sus sits in North America. 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 Windows with Rust network protocol 2635 and build 168909. 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 3 days 15 hours ago. 2 of 168 hours were online in the last 7 full days, giving 1% uptime. On 25 September 2026, Rust Live Stats saw it for the first time.
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.