DWG RG-S15396Server sheetchecked 2d ago
Why So Sus
Offline NA 47.226.85.41:28015 checked 2d 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 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Its 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
| 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
Quick answers
Recorded details
What uptime is recorded for Why So Sus, and is it up?
Last seen 2 days 7 hours ago; right now Why So Sus is offline. 2 of 168 hours up over the last 7 full days, which is 1% of the time. First seen by Rust Graphs on 25 September 2026.
What location is recorded for Why So Sus?
The NA tag is how Why So Sus lists itself in North America. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 47.226.85.41:28015.
What Rust version is recorded for Why So Sus?
Rust network protocol 2635 and build 168909 on Windows: that is what Why So Sus runs. Steam updates your game, which must be on the same protocol for you to join.
Counts
How many players are plotted on Why So Sus?
Why So Sus is not responding at the latest refresh; the last record of it online is 2 days 7 hours ago. Averaged across seven days, the player count is 0.
What rank has been recorded for Why So Sus?
Across seven days, player hours give Why So Sus #15,396 globally and #1,541 in North America, a top 69% position among ranked servers.
Schedules
What happens on Why So Sus on the day of a wipe?
At their busiest, its recent wipes drew 1 players on average. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. By day 1 the crowd had fallen below half on the wipes where it did not hold.
What wipe schedule has been recorded for Why So Sus?
There is no next wipe to predict at Why So Sus, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 2 days 7 hours ago.
Map and rules
What settings and rules apply on Why So Sus?
No gather rate is stated in the name of Why So Sus. The group limit is 8 players, the game's default. combat training, aim and PvP practice, loot handed out, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. Its own label is vanilla, meaning facepunch's game, unaltered: rates, kits and rules are as shipped. VAC is on: that is Valve's anti-cheat.
On which map is Why So Sus played?
A procedural map, generated by the game, is what Why So Sus runs.
Tags
Where does Why So Sus appear among the Rust Graphs lists and filters?
These Rust Graphs lists include Why So Sus: Modded Rust servers, Rust aim training servers, listed live, Rust battlefield servers and Rust server list: North America. It is returned by these filters on the server list: 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.
On Why So Sus, what is meant by each tag?
The game's server browser reads these tags from Why So Sus: gmrust (Game mode): Standard survival, as Rust plays; mp3 (Max players): The slot count is 3; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^d (Combat training): The loot is handed to you for aim and PvP practice; ^i (Battlefield): Kits and high rates drive fast PvP; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; NA (North America): The browser's listing places it under North America. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
How to join
How is Why So Sus joined?
Enter client.connect 47.226.85.41:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.
Server tags
Published as mp3,ptrak,$r?,v2635,^v,^d,^i,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp3
ts8
v2635
cs168909
ptrak
$r?
Difficulty
^v
Gameplay
^d
^i
Mods and access
^o
^z
Region
NA
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.