Why So Sus
Key statistics
the figures behind the quote- Players now
- 0/ 3 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,466 top 68%
- Rank · 7d ago
- #10,562 ▼4904 places down
- Last wipe
- 23d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 20 Sep 2026 no hostname published
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 84/300 | ▼−41−32.7% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 80/225 | ▼−15−15.9% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 90/100 | ▼−1−0.7% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 26/1000 | ▼−28−52.1% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 7/1000 | ▼−15−67.6% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 22/700 | ▼−61−73.6% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Why So Sus?
No gather rate is given in the name of Why So Sus. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are running. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Why So Sus?
Why So Sus uses a procedural map, which the game generates.
Population
What position does Why So Sus hold in the server rankings?
In the top 68% of all ranked servers, Why So Sus is #15,466 on player hours over the last seven days.
What is the population on Why So Sus?
At present, Why So Sus is offline; the last sighting was 23 days 8 hours ago.
Wipe Schedule
On what cycle does Why So Sus wipe?
The record holds too few of Why So Sus's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 23 days 19 hours ago the current world was created.
Server Details
What is the server location for Why So Sus?
No region is published by Why So Sus. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 47.226.85.41:28015.
Why So Sus is on which Rust version?
Rust network protocol 2633 and build 164530 on Linux is what Why So Sus runs. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of Why So Sus?
Offline at this moment: Why So Sus. Last seen 23 days 8 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. First sighting by Rust Analytics: 20 September 2026.
Tags & Filters
How should you interpret the tags on Why So Sus?
These tags are published by Why So Sus and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp3 (Max players): It holds 3 slots; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs164530 (Build): It runs build 164530; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does Why So Sus show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature Why So Sus: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to Join
How can I connect to Why So Sus?
Type client.connect 47.226.85.41:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp3,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
mp3
ts8
v2633
cs164530
ptrak
$r?
Mods and access
^o
^z
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.