Offline 47.226.85.41:28015 checked 37d ago
Why So Sus
Connect
srv = rust.server("47.226.85.41:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 47.226.85.41:28015
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Sep 2026, 13:51 UTC
- hostname
- –
- first seen
- 20 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 155 on average | 174/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 178/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 139/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 53/1000 |
Quick answers
From the figures on this page.
Population data
How does Why So Sus compare in the rankings?
Over the last seven days Why So Sus sits at #15,466 on player hours, in the top 68% of ranked servers.
What population does Why So Sus carry?
Offline now for Why So Sus, with the last sample 37 days 10 hours ago.
Server data
What Rust version does Why So Sus run?
The build is Rust network protocol 2633 and build 164530 on Linux, run by Why So Sus. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Why So Sus, and is it up?
Offline now for Why So Sus, last seen 37 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 20 September 2026.
In which location is Why So Sus hosted?
No region is published by Why So Sus. Rust Data does not look up where the machine stands; it shows where a server says it is. 47.226.85.41:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Why So Sus?
You will not find a gather rate in the string Why So Sus. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Why So Sus selected?
Why So Sus runs a procedural map, which the game generates.
Wipes and dates
When does Why So Sus wipe, and on what schedule?
A rhythm cannot be read from the wipes of Why So Sus on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 37 days 21 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain Why So Sus?
The Rust Data lists that Why So Sus fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Why So Sus?
The game's server browser reads these tags from Why So Sus: gmrust (Game mode): Rust survival in its standard form; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Build number: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join Why So Sus?
Enter client.connect 47.226.85.41:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.