Rust Wipe StatsWipe forecast
Now 97,865 players 11,882 servers 398 fresh wipes in 3 h

Local forecast · NA

Why So Sus

Offline NA 47.226.85.41:28015 checked 3d ago

vanillamoddedoxide

Current conditions

observed 3d ago
0 / 3
players now
Offline H – · avg 0 7-day high and average

0% full

7-day average
0
peak –
Rank
#15,341
top 69% · #1503 in NA
Last wipe
3d ago
no schedule published
Next wipe
–
no rhythm it keeps

Next wipe

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

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k25 Sep30 Sep5 Oct10 Oct15 Oct29 Oct

Top 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.

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.

3.2 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
50%
crowd held
else halves by day 1

The first 48 hours of its last wipes

Mon 26 OctThu 8 OctWed 7 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Past weather: its wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 01:29 UKMon 26 Oct, 01:29 UTC · 3d ago 0 – running 0
Thu 8 Oct, 03:21 UKThu 8 Oct, 02:21 UTC · 21d ago 2 held half 18 days 2
Wed 7 Oct, 07:20 UKWed 7 Oct, 06:20 UTC · 22d ago 2 – 0.8 days 0
Tue 6 Oct, 06:40 UKTue 6 Oct, 05:40 UTC · 23d ago 2 – 1 days 0
Wed 30 Sep, 23:41 UKWed 30 Sep, 22:41 UTC · 28d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.

Similar servers

the same kind of game, then region, group limit, rate and wipes
PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVP NA · groups of 8+ · 5 on average
10/ 25
[US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 NA · no group limit · 2 on average
2/ 100
NA | Apex Aim Arena | 1v1 Facecheck FFA Targets NA · groups of 8+ · 3 on average
0/ 16
0/ 16
The Salt Mines (Official) Solo Only | 2x | NA · groups of 8+ · 2x · monthly · 1 on average
1/ 100
[US] ICEFUSE BATTLEFIELD x1000000000|MYMINI|CLANS|KITS|PVP|FPS NA · groups of 100+ · 1e+09x · weekly · 32 on average
24/ 100

Quick answers

from the figures on this page

Server details

Is Why So Sus online at the moment, and how consistent is its uptime?

Right now Why So Sus is down; the last sighting was 3 days 14 hours ago. In the last 7 full days it stayed up 2 of 168 hours, 1% of the time. The first sighting by Rust Wipe Stats was on 25 September 2026.

Where does Why So Sus run from?

With its NA tag, Why So Sus lists itself in North America. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 47.226.85.41:28015 is its address.

What version of Rust is running on Why So Sus?

Rust network protocol 2635 and build 168909 on Windows is what Why So Sus runs. Steam updates your game for you; the protocol must match to join.

Server tags

Which meaning sits behind each tag on Why So Sus?

For the game's server browser, Why So Sus publishes these tags: gmrust (Game mode): The mode is plain Rust survival; mp3 (Max players): Capacity: 3; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region field is left blank; ^v (Vanilla): No changed rates, kits or rules: this is the stock Facepunch game; ^d (Combat training): Training for aim and PvP: loot is supplied; ^i (Battlefield): Kits and high rates keep the PvP quick; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded; NA (North America): The server browser puts it under North America. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.

Where does Why So Sus appear among the Rust Wipe Stats lists and filters?

These Rust Wipe Stats lists include Why So Sus: Modded Rust servers, Aim, UKN and combat training servers, Rust battlefield servers and US 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.

Rules and settings

Which map is in use on Why So Sus?

The map is procedural, generated by the game on Why So Sus.

What settings does Why So Sus use, and what rules does it enforce?

Gather rate is not given in the name for Why So Sus. No group setting is published, so the game default of 8 players applies. It plays as combat training, practice for aim and PvP, loot given freely. The server browser lists it as Modded, where plugins or settings alter the game. It runs these plugin frameworks: Oxide. Its own description reads vanilla: no changed rates, kits or rules: this is the stock Facepunch game. VAC, Valve's anti-cheat, is enabled.

Wipe days

Which days and times does Why So Sus schedule its wipes for?

Why So Sus keeps no regular rhythm, and its wipes fall at irregular times, so no next wipe can be named. All Rust servers wipe at the force wipe each month, next due Thursday 5 November at 19:00 UTC. 3 days 15 hours is how long the current world has been running.

What happens on Why So Sus when wipe day arrives?

At their busiest, its recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd hit its peak. 50% of recent wipes kept more than half the peak until the next wipe. The fall below half came by day 1 when the crowd did not hold.

Population

What sort of population does Why So Sus carry?

Why So Sus is offline at the moment; the last sighting was 3 days 14 hours ago. The average for the past week is 0 players.

How does Why So Sus compare with other Rust servers in the rankings?

Seven-day player hours place Why So Sus at #15,341, inside the top 69% of ranked servers and at #1,503 in North America.

Getting in

What steps let you join Why So Sus?

Enter client.connect 47.226.85.41:28015 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,^v,^d,^i,NA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The mode is plain Rust survival.
mp3
Max players Capacity: 3.
ts8
Group limit The default cap of 8 per team applies here.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build: 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region field is left blank.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the stock Facepunch game.

Gameplay

^d
Combat training Training for aim and PvP: loot is supplied.
^i
Battlefield Kits and high rates keep the PvP quick.

Mods and access

^o
Oxide The plugins run through Oxide (uMod).
^z
Modded Plugins or settings alter the game here, so it is listed under Modded.

Region

NA
North America The server browser puts it under North America.

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.