Station NA-15353 · no signal
Why So Sus
Offline NA 47.226.85.41:28015 checked 3d ago
- Players now
- 0/ 3
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,353
- top 69% · #1518 in NA
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 3 slots
- Motion · 24 h
- M –not enough readings
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 69% of all ranked servers, top 81% 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.
- usual gap
- 3.2 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 50%else halves by day 1
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 01:29 UTC3d ago | M0.0■steady | 0 | – | running | 0 | |
| Thu 8 Oct, 02:21 UTC21d ago | M0.0■steady | 2 | held half | 18 days | 2 | |
| Wed 7 Oct, 06:20 UTC21d ago | M0.3▲rising | 2 | – | 0.8 days | 0 | |
| Tue 6 Oct, 05:40 UTC22d ago | M0.3▲rising | 2 | – | 1 days | 0 | |
| Wed 30 Sep, 22:41 UTC28d ago | M0.3▲rising | 2 | halved by day 1 | 5.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Why So Sus?
A procedural map runs on Why So Sus, generated by the game.
Which settings and rules apply on Why So Sus?
The name of Why So Sus gives no gather rate. The group limit is 8 players, the game's default. In combat training mode, loot is handed out for aim and PvP practice. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. By its own description it is vanilla: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Why So Sus right now?
No players are recorded on Why So Sus at this moment; it is offline, and the last sighting was 3 days ago. The seven-day average for this server is 0 players.
How does Why So Sus rank against other Rust servers?
For player hours across the last seven days, Why So Sus takes #15,353 overall and #1,518 in North America, inside the top 69% of all ranked servers.
Operator and location
How reliably does Why So Sus stay online?
No contact with Why So Sus right now, and the last recorded contact was 3 days ago. Of the 168 hours in the last 7 full days, it was up for 2, or 1% of the time. 25 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Why So Sus hosted?
In North America Why So Sus lists itself, with the tag NA. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 47.226.85.41:28015.
Which Rust version is Why So Sus running?
Rust network protocol 2635 and build 168909 on Windows is what Why So Sus runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Why So Sus?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
How often does Why So Sus wipe, and on which days?
No next wipe can be predicted for Why So Sus, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 3 days 1 hours.
Lists and tags
What do the server tags on Why So Sus mean?
The game's server browser reads the tags Why So Sus publishes: gmrust (Game mode): Survival in standard Rust; mp3 (Max players): 3 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^d (Combat training): You get loot handed to you to practise aim and PvP; ^i (Battlefield): Kits and high rates drive fast PvP; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; NA (North America): North America is the region it's listed under in the browser. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Why So Sus appear?
The Rust Server Trends lists that take in Why So Sus are: Modded Rust servers, tracked live, Rust aim training servers, live, Rust battlefield servers and North America Rust servers. These filters bring it up 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 week.
How to join
What steps get you onto Why So Sus?
You can connect by pressing F1 in Rust and typing client.connect 47.226.85.41:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.