S
Offline 51.158.204.214:28015 checked 38d ago
Server instruments
no direct query in 48 hoursPlayers now
2% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 121/500
- 121/100
- 186/225
- 58/700
- 6/200
- 23/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does S follow?
The rhythm of S's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 38 days 23 hours ago.
Lists and filters
How should you read the tags on S?
These are the tags S publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does S appear in Rust Metrics lists and filters?
These Rust Metrics lists carry S: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does S sit in the rankings?
Player hours over seven days put S at #13,308, in the top – of all ranked servers.
How full does S get?
S is not responding; status offline, last seen 38 days 19 hours ago.
Operator and location
Where does S sit?
No region tag on S. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 51.158.204.214:28015.
What Rust version is S on?
Rust network protocol 2633 and build 164530 on Windows is the build S runs. To get in, your game needs the same protocol; Steam applies the update.
Is S up, and how often does it stay up?
Reading: offline. S last answered 38 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 20 September 2026.
Map and rules
How is S configured, and what rules are in force?
Reading the name gives no gather rate for S. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
How to join
How do you connect to S?
Check: join. Open Rust, press F1, then enter client.connect 51.158.204.214:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.