SeattleProcedural. Solo/Duo
Offline NA 50.125.201.106:28015 checked 28d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers, top 83% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. 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- 88/200
- 79/200
- 56/400
- 56/225
- 15/200
- 27/150
Quick answers
from the figures on this pageReset cycle
How often does SeattleProcedural. Solo/Duo wipe, and when?
An estimate from the force wipe gives SeattleProcedural. Solo/Duo's next wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 56 days ago the current world was made. The tags state a wipe schedule of one wipe a month.
Tag meanings
How should you read the tags on SeattleProcedural. Solo/Duo?
Tags published by SeattleProcedural. Solo/Duo, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp65 (Max players): Slots: 65; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): It runs Oxide, also known as 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.
Which operator is behind SeattleProcedural. Solo/Duo?
Most likely the same operator runs them: SeattleProcedural. Solo/Duo publishes a rexisgodrust.ddnsfree.com hostname, and so do 3 other servers we track.
Which lists and filters on Rust Metrics show SeattleProcedural. Solo/Duo?
On Rust Metrics, SeattleProcedural. Solo/Duo sits in these lists: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. Reading: server list filters. It comes up under 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.
Population
What position does SeattleProcedural. Solo/Duo hold among Rust servers?
Player hours over the last seven days put SeattleProcedural. Solo/Duo at #16,599, #1,647 in North America, in the top 70% of all ranked servers.
What is the population on SeattleProcedural. Solo/Duo?
Reading for SeattleProcedural. Solo/Duo: offline at this moment; last seen 28 days 12 hours ago.
Server details
Where does SeattleProcedural. Solo/Duo sit?
SeattleProcedural. Solo/Duo gives North America as its location, with the NA tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 50.125.201.106:28015.
What Rust version is SeattleProcedural. Solo/Duo on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by SeattleProcedural. Solo/Duo. To get in, your game needs the same protocol; Steam applies the update.
Is SeattleProcedural. Solo/Duo up, and how often does it stay up?
Check: connection. SeattleProcedural. Solo/Duo is offline at this moment. Last contact was 28 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Map and rules
How is SeattleProcedural. Solo/Duo configured, and what rules are in force?
Reading the name gives no gather rate for SeattleProcedural. Solo/Duo. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Oxide plugins are running. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. VAC is on. That is Valve's anti-cheat.
What map is SeattleProcedural. Solo/Duo on?
Size 4,250 and seed 4683: the game generates the procedural map on SeattleProcedural. Solo/Duo from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
What do you do to join SeattleProcedural. Solo/Duo?
Press F1 in Rust and enter client.connect 50.125.201.106:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/ZpqaKhXjkn.