Rust Server IndexCard catalogue of Rust servers

Holdings11,748 servers75,412 players138 fresh wipes

Call no.NA15432 Off the shelf · offline

Why So Sus

Offline NA 47.226.85.41:28015 checked 2d ago

Subjects 1. vanilla2. modded3. oxide
Players now
0/ 3
0% full
7-day average
0
peak –
Rank
#15,432
top 69% · #1539 in NA
Last wipeWiped26 OCT2026 · 2d 12h ago
2d ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

No hourly history yet.

Hourly average and peak, UTC.

Record sheet B · appended

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep30 Sep5 Oct9 Oct14 Oct28 Oct

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

Record sheet D · loan terms

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.

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

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.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
26 OCT 2026Mon 26 Oct, 01:29 UTC2d ago
0 – running 0
8 OCT 2026Thu 8 Oct, 02:21 UTC20d ago
2 held half 18 days 2
7 OCT 2026Wed 7 Oct, 06:20 UTC21d ago
2 – 0.8 days 0
6 OCT 2026Tue 6 Oct, 05:40 UTC22d ago
2 – 1 days 0
30 SEP 2026Wed 30 Sep, 22:41 UTC27d 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

NA 7/ 15
NA 3/ 100
NA
NA | Apex Aim Arena | 1v1 Facecheck FFA TargetsNA · groups of 8+ · 4 on average
0/ 16
NA 0/ 16
NA2X
The Salt Mines (Official) Solo Only | 2x |NA · groups of 8+ · 2x · monthly · 1 on average
2/ 100
NAMAX
[US] ICEFUSE BATTLEFIELD x1000000000|MYMINI|CLANS|KITS|PVP|FPSNA · groups of 100+ · 1e+09x · weekly · 31 on average
16/ 100
Reference desk

Quick answers

From the figures on this page.

Rules and settings

On Why So Sus, which rules and settings apply?

The name of Why So Sus does not state a gather rate. The default group limit of 8 players applies. Filed under combat training, practice for aim and PvP, with loot given out. Plugins or settings change the game; it is listed under Modded in the server browser. Plugins in use: Oxide. Its own label is vanilla: filed under vanilla: Facepunch's game, unaltered. VAC is on: Valve's anti-cheat is enabled.

What is the map on Why So Sus?

A procedural map, generated by the game, is what Why So Sus runs.

Tags

Where does Why So Sus appear among the Rust Server Index lists and filters?

The Rust Server Index lists that include Why So Sus are Modded Rust servers, filed by play style, Aim training servers, filed, Rust battlefield servers, indexed and North American Rust servers. These filters on the server list bring it up: 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.

How should you read the tags listed for Why So Sus?

The server's own tags are listed here, and the game's server browser reads them: Why So Sus gives gmrust (Game mode): Rust survival, as standard; mp3 (Max players): The queue ceiling sits at 3; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^v (Vanilla): Filed under vanilla: Facepunch's game, unaltered; ^d (Combat training): Training: aim and PvP drills with loot supplied; ^i (Battlefield): High rates and kits drive the fast PvP here; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded: the game is changed by plugins or settings; NA (North America): Server browser region: North America. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipes and resets

What happens on wipe day at Why So Sus?

Its recent wipes averaged 1 players at peak. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 50% of its recent wipes. By day 1 the crowd had fallen below half when it didn't hold.

Which wipe timetable does Why So Sus follow?

Why So Sus wipes at times that follow no pattern, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Its present world dates from 2 days 12 hours.

Player counts

What position does Why So Sus hold among Rust servers?

Filed under rankings: #15,432 for Why So Sus on seven-day player hours, #1,539 in North America, top 69% overall.

What does the player count on Why So Sus look like?

The last check found Why So Sus offline, last seen 2 days 11 hours ago. Averaged over the last seven days, the count is 0 players.

Server facts

Which Rust build is Why So Sus running?

Rust network protocol 2635 and build 168909 on Windows is what you will find on Why So Sus. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of Why So Sus?

Last seen 2 days 11 hours ago, Why So Sus is offline right now. It was up 2 of 168 hours across the last 7 full days, or 1% of the time. On 25 September 2026 it was first seen by Rust Server Index.

Where in the world is Why So Sus hosted?

The NA tag places Why So Sus, by its own listing, in North America. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 47.226.85.41:28015.

Joining the server

How can you connect to Why So Sus?

If you would rather use the console, press F1 in Rust and enter client.connect 47.226.85.41:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.

Subject headings explained

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 Rust survival, as standard.
mp3
Max players The queue ceiling sits at 3.
ts8
Group limit Game default applies: teams of up to 8.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build It runs build 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region code field is left empty.

Difficulty

^v
Vanilla Filed under vanilla: Facepunch's game, unaltered.

Gameplay

^d
Combat training Training: aim and PvP drills with loot supplied.
^i
Battlefield High rates and kits drive the fast PvP here.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Modded: the game is changed by plugins or settings.

Region

NA
North America Server browser region: 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.