SeattleProcedural. Solo/Duo
Offline NA 50.125.192.213:28015 checked 8d 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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 15h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 15hFW
- WPT 2Thu 3 Dec, 19:00 UTC34d 15hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:18 UTC FW28d ago | 1 | – | running | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 131/200
- 98/200
- 79/400
- 157/225
- 27/200
- 16/150
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on SeattleProcedural. Solo/Duo?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 2 hours.
What wipe timing does SeattleProcedural. Solo/Duo follow?
Once a month SeattleProcedural. Solo/Duo wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 28 days 9 hours ago. The tags state a wipe schedule of one wipe a month.
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): The server holds 65 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^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): It runs Oxide, also known as uMod; NA (North America): The server browser files it under North America. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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?
These Rust Metrics lists carry SeattleProcedural. Solo/Duo: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: 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
Where does SeattleProcedural. Solo/Duo sit in the rankings?
Player hours over the last seven days put SeattleProcedural. Solo/Duo at #15,344, #1,522 in North America, in the top 69% of all ranked servers.
How full does SeattleProcedural. Solo/Duo get?
Status for SeattleProcedural. Solo/Duo: offline. Last seen 8 days 4 hours ago.
Operator and location
Where does SeattleProcedural. Solo/Duo sit?
Its NA tag places SeattleProcedural. Solo/Duo in North America. 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.192.213:28015.
What Rust version is SeattleProcedural. Solo/Duo on?
Rust network protocol 2634 and build 167781 on Windows is the build SeattleProcedural. Solo/Duo runs. 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 8 days 4 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 1 October 2026.
Rules and settings
What rules does SeattleProcedural. Solo/Duo enforce, and what are its settings?
No gather rate appears in the name: SeattleProcedural. Solo/Duo. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Plugin count: Oxide. The server calls itself vanilla, with this meaning: 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?
From seed 1788459108, the game generates the procedural map on SeattleProcedural. Solo/Duo. Its size is 4,250. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join SeattleProcedural. Solo/Duo?
Press F1 in Rust and enter client.connect 50.125.192.213:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://discord.com/invite/ZpqaKhXjkn is where its website sits.