SeattleProcedural. Solo/Duo
Offline NA 50.125.197.83:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
3% 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
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. The 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- 115/200
- 81/200
- 64/400
- 93/225
- 22/200
- 19/150
Quick answers
from the figures on this pageReset cycle
What wipe timing does SeattleProcedural. Solo/Duo follow?
From the force wipe, the next wipe of SeattleProcedural. Solo/Duo is an estimate. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 56 days 4 hours ago. A monthly wipe schedule is published in its tags.
Tag meanings
How should you read the tags on SeattleProcedural. Solo/Duo?
These are the tags SeattleProcedural. Solo/Duo publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp65 (Max players): Slots: 65; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); NA (North America): The server browser files it under North America. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does SeattleProcedural. Solo/Duo appear in Rust Metrics lists and filters?
On Rust Metrics, SeattleProcedural. Solo/Duo sits in these lists: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. These filters bring it up on the server list: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Player count
What position does SeattleProcedural. Solo/Duo hold among Rust servers?
Player hours over the last seven days put SeattleProcedural. Solo/Duo at #12,570, #1,444 in North America, in the top – of all ranked servers.
What is the population on SeattleProcedural. Solo/Duo?
Reading for SeattleProcedural. Solo/Duo: offline at this moment; last seen 43 days 19 hours ago.
Server
Where does SeattleProcedural. Solo/Duo sit?
Reading: location. The NA tag puts SeattleProcedural. Solo/Duo in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 50.125.197.83:28015.
What Rust version is SeattleProcedural. Solo/Duo on?
Rust network protocol 2633 and build 163794 on Windows is the build SeattleProcedural. Solo/Duo runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on SeattleProcedural. Solo/Duo, and is it online?
SeattleProcedural. Solo/Duo reports offline. The last reading came 43 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 15 September 2026.
Map and rules
How is SeattleProcedural. Solo/Duo configured, and what rules are in force?
No gather rate appears in the name: SeattleProcedural. Solo/Duo. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Plugin count: Oxide. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. VAC is on. That is Valve's anti-cheat.
What map is SeattleProcedural. Solo/Duo on?
The game generates a procedural map for SeattleProcedural. Solo/Duo.
How to join
How do you connect to SeattleProcedural. Solo/Duo?
Check: join. Open Rust, press F1, then enter client.connect 50.125.197.83:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.