Statistical profileOffline
Why So Sus
NA 47.226.85.41:28015 checked 2d ago
Connect to this server
1. Main points
Players now
0/ 3
0% full
7-day average
0
peak –
Rank
#15,425
top 69% · #1544 in NA
Last wipe
2d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 3 slots.
- It ranks #15,425 of all ranked servers, the top 69%, and #1544 in NA, on player hours over the last seven days.
- Its current map went up 2d ago.
2. Players
Figure 1: Players on Why So Sus
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Usual gap
3.2 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
1
players, last three wipes
Crowd held
50%
else halves by day 1
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| 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 UTC20d ago | 2 | – | 0.8 days | 0 |
| Tue 6 Oct, 05:40 UTC21d ago | 2 | – | 1 days | 0 |
| Wed 30 Sep, 22:41 UTC27d ago | 2 | halved by day 1 | 5.3 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Why So Sus
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Why So Sus
What the server publishes and what was recorded
| Address | 47.226.85.41:28015 |
|---|---|
| Region | NA |
| Max players | 3 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 26 Oct 2026, 01:29 UTC |
| Hostname | – |
| First seen | 25 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVP | NA · groups of 8+ · 5 on average | 5 / 10 |
| [US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 | NA · no group limit · 2 on average | 5 / 100 |
| NA | Apex Aim Arena | 1v1 Facecheck FFA Targets | NA · groups of 8+ · 4 on average | 0 / 16 |
| Deadshot's Arena | NA | BedWars | Aim Train | Scrim | Gun Game | NA · groups of 8+ · 4 on average | 0 / 16 |
| The Salt Mines (Official) Solo Only | 2x | | NA · groups of 8+ · 2x · monthly · 1 on average | 5 / 100 |
| [US] ICEFUSE BATTLEFIELD x1000000000|MYMINI|CLANS|KITS|PVP|FPS | NA · groups of 100+ · 1e+09x · weekly · 31 on average | 35 / 100 |
10. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on Why So Sus?
Wipes on Why So Sus fall at irregular times, leaving no next date to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 2 days 3 hours ago.
How is wipe day run on Why So Sus?
The average busiest point of its recent wipes drew 1 players. On the latest wipe, 0 hours passed before the crowd peaked. Half that peak was held until the next wipe in 50% of its recent wipes. If not, it dropped below half by day 1.
Server details
How reliable is Why So Sus, and is it online now?
The latest count records Why So Sus as offline, last seen 2 days 2 hours ago. A total of 2 of 168 hours were up over 7 full days, which is 1% of the time. First recorded by Rust Census on 25 September 2026.
What location has been recorded for Why So Sus?
In North America Why So Sus lists itself, with its NA tag. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 47.226.85.41:28015 it is addressed.
On which Rust version does Why So Sus operate?
The version in use on Why So Sus is Rust network protocol 2635 and build 168909 on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Player counts
How many players does Why So Sus carry?
At this release Why So Sus is offline, having last been seen 2 days 2 hours ago. The seven-day average for this server is 0 players.
In the rankings of Rust servers, where is Why So Sus placed?
For seven-day player hours Why So Sus is ranked #15,425 and #1,544 in North America, placing it in the top 69% of all ranked servers.
Lists and tags
Where does Why So Sus appear among the Rust Census lists and filters?
These Rust Census lists include Why So Sus: Modded Rust servers, counted, Aim training servers, counted, Rust battlefield servers and North America: servers listed. It appears under 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.
The tags on Why So Sus: what do they indicate?
These are the tags Why So Sus publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp3 (Max players): Slots: 3; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set; ^v (Vanilla): This is the unmodified game: rates, kits and rules as Facepunch ships them; ^d (Combat training): This is a training server: practise aim and PvP with loot handed to you; ^i (Battlefield): High rates and kits make this a fast PvP battlefield; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): This server is listed as modded, with plugins or settings that change the game; NA (North America): North America is the region under which the browser lists it. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map is in use on Why So Sus?
A procedural map runs on Why So Sus, generated by the game.
How is Why So Sus configured, and what rules does it keep?
No gather rate is recorded for Why So Sus in its name. The group cap stands at 8 players, the default for the game. It runs combat training, aim and PvP practice, loot handed out. The server browser lists it under Modded: plugins or settings alter the game. The plugin count is Oxide. Vanilla is its own description: this is the unmodified game: rates, kits and rules as Facepunch ships them. Anti-cheat is active: VAC, Valve's system, is on.
Join details
What is the way to join Why So Sus?
Enter client.connect 47.226.85.41:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp3,ptrak,$r?,v2635,^v,^d,^i,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp3 | Max players Slots: 3. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
Difficulty
^v | Vanilla This is the unmodified game: rates, kits and rules as Facepunch ships them. |
|---|
Gameplay
^d | Combat training This is a training server: practise aim and PvP with loot handed to you. |
|---|---|
^i | Battlefield High rates and kits make this a fast PvP battlefield. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
Region
NA | North America North America is the region under which the browser lists it. |
|---|
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.