Live coverage · NA
Offline SeattleProcedural. Solo/Duo is not on the server list right now. The figures below are from when it was last seen, 43d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. The force wipe
This server has not put up a new map since the desk started watching it.
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.
An estimate from the force wipe gives SeattleProcedural. Solo/Duo's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. This world dates from 56 days 3 hours. The tags carry a monthly wipe schedule.
These are the Rust Live Stats lists SeattleProcedural. Solo/Duo fits: Live Rust community servers, North America Rust servers, live and Vanilla Rust servers, live. These filters on the server list bring it up: 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.
These are the tags SeattleProcedural. Solo/Duo makes public: gmrust (Game mode): Survival here follows standard Rust; mp65 (Max players): 65 slots are available; ts8 (Group limit): Team cap: 8, which is the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^m (Monthly): A single monthly wipe, set by Facepunch's force wipe; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^o (Oxide): Plugin framework: Oxide (uMod); NA (North America): North America is the browser listing for this server. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
SeattleProcedural. Solo/Duo reads offline at the moment; the last sighting was 43 days 19 hours ago.
Seven-day player hours place SeattleProcedural. Solo/Duo at #12,570 overall, in the top – of ranked servers and #1,444 in North America.
The name SeattleProcedural. Solo/Duo carries no gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser lists it under Community. Plugins run here: Oxide. By its own label it is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. Anti-cheat: VAC from Valve is enabled.
SeattleProcedural. Solo/Duo uses a procedural map, which the game generates.
The NA tag on SeattleProcedural. Solo/Duo lists it in North America. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 50.125.197.83:28015.
Rust network protocol 2633 and build 163794 on Windows is what SeattleProcedural. Solo/Duo runs. Joining requires the same protocol on your game; Steam takes care of updating it.
As of now, SeattleProcedural. Solo/Duo is offline; the last sighting was 43 days 19 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. The first sighting by Rust Live Stats was on 15 September 2026.
Enter client.connect 50.125.197.83:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.