SAO RUST #1 | SEMI CLASSIC X3 | MAX 4
Online 194.87.209.146:28015 checked 9m ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avg7-day peakServer 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 bestTop 32% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 8 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 14:55 UTC6d ago | 1 | – | running | 0 |
| Mon 19 Oct, 15:08 UTC10d ago | 0 | – | 4 days | 0 |
| Mon 12 Oct, 14:56 UTC17d ago | 0 | – | 7 days | 0 |
| Wed 7 Oct, 08:51 UTC22d ago | 1 | held half | 5.3 days | 0 |
| Mon 28 Sep, 15:08 UTC31d ago | 0 | – | 8.7 days | 0 |
| Fri 25 Sep, 15:03 UTC34d ago | 0 | – | 3 days | 0 |
| Mon 21 Sep, 15:19 UTC38d ago | 3 | halved by day 1 | 4 days | 0 |
| Fri 18 Sep, 14:58 UTC41d ago | 1 | halved by day 2 | 3 days | 0 |
| Mon 14 Sep, 15:05 UTC45d ago | 3 | halved by day 2 | 4 days | 1 |
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- 560/600
- 278/300
- 146/140
- 32/100
- 118/350
- 28/100
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on SAO RUST #1 | SEMI CLASSIC X3 | MAX 4?
At their busiest, its recent wipes drew 0 players on average. 8 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.
What wipe timing does SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 follow?
There is no next wipe to predict: SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 6 days 2 hours ago the current world was made.
Tags
Which tags does SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 carry, and what do they mean?
These are the tags SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^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 SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 appear in Rust Metrics lists and filters?
These Rust Metrics lists carry SAO RUST #1 | SEMI CLASSIC X3 | MAX 4: 3x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 3x.
Player count
What position does SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 hold among Rust servers?
Ranking for SAO RUST #1 | SEMI CLASSIC X3 | MAX 4: #7,180 on seven-day player hours, top 32% of all ranked servers.
What player count does SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 carry?
Current headcount on SAO RUST #1 | SEMI CLASSIC X3 | MAX 4: 0 players, 150 slots available. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.
Operator and location
Which location does SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 run from?
No region comes from SAO RUST #1 | SEMI CLASSIC X3 | MAX 4. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 194.87.209.146:28015.
What Rust version is SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by SAO RUST #1 | SEMI CLASSIC X3 | MAX 4. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is SAO RUST #1 | SEMI CLASSIC X3 | MAX 4, and is it online now?
Reading: online. SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 answers right now. Reading: 95% uptime over the last 7 full days. It was up 159 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What settings and rules apply on SAO RUST #1 | SEMI CLASSIC X3 | MAX 4?
The name carries the rate: 3x gather on SAO RUST #1 | SEMI CLASSIC X3 | MAX 4. 8 players per group, the default value. The mode is survival. Note the following: 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. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is SAO RUST #1 | SEMI CLASSIC X3 | MAX 4 on?
Procedural map on SAO RUST #1 | SEMI CLASSIC X3 | MAX 4, made by the game's generator.
Join
How can you get onto SAO RUST #1 | SEMI CLASSIC X3 | MAX 4?
Press F1 in Rust and enter client.connect 194.87.209.146:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.