SeattleProcedural. Solo/Duo
Online NA 50.125.205.168:28015 checked 10m ago
Server instruments
last reading Fri 06:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 57 · below 20 is lag, below 10 is badEntities
48 h range 99,606–102,058 · memory 4,136 MBUptime
7 days 10 hours since its last restart, at the last readingPlayers
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 51% of all ranked servers, top 72% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 10h. 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- 43/200
- 51/200
- 35/400
- 60/225
- 16/200
- 18/150
Quick answers
from the figures on this pageReset cycle
When does SeattleProcedural. Solo/Duo wipe?
The estimate for SeattleProcedural. Solo/Duo's next wipe comes from the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 28 days 13 hours ago. Its tags carry a monthly wipe schedule.
Lists and filters
Which tags does SeattleProcedural. Solo/Duo carry, and what do they mean?
Tags published by SeattleProcedural. Solo/Duo, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp65 (Max players): 65 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Plugin framework in use: Oxide (uMod); NA (North America): Its browser listing: 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?
Check: operator. SeattleProcedural. Solo/Duo publishes a rexisgodrust.ddnsfree.com hostname, and 3 other servers we track do too. Same operator, most likely.
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. 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.
Occupancy
Where does SeattleProcedural. Solo/Duo sit in the rankings?
Player hours over the last seven days put SeattleProcedural. Solo/Duo at #11,390, #1,332 in North America, in the top 51% of all ranked servers.
What player count does SeattleProcedural. Solo/Duo carry?
Current headcount on SeattleProcedural. Solo/Duo: 0 players, 65 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 02:00 UTC, averaging 1 players at that hour.
Server
Where does SeattleProcedural. Solo/Duo sit?
Its NA tag places SeattleProcedural. Solo/Duo in North America. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 50.125.205.168:28015.
What Rust version is SeattleProcedural. Solo/Duo on?
Rust network protocol 2635 and build 168909 on Windows is the build SeattleProcedural. Solo/Duo runs. To get in, your game needs the same protocol; Steam applies the update.
How does SeattleProcedural. Solo/Duo perform?
Reading: 81 server fps on average across the last 48 hours. It never dropped below 57. Reading: 102,058 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,739 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
Is SeattleProcedural. Solo/Duo up, and how often does it stay up?
Check: connection. SeattleProcedural. Solo/Duo is online at this moment. Reading: uptime. About 7 days 10 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 22 October 2026.
Rules and settings
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. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: plugins. It runs Oxide of them. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.
What map is SeattleProcedural. Solo/Duo on?
Size 4,250 and seed 1788459108: the game generates the procedural map on SeattleProcedural. Solo/Duo from them. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
What do you do to join SeattleProcedural. Solo/Duo?
Press F1 in Rust and enter client.connect 50.125.205.168: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.