SeattleProcedural. Solo/Duo
Online NA 50.125.205.168:28015 checked 11m ago
Measurements
Players
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
Top 68% of all ranked servers, top 80% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 0h. The force wipe
Wipes
| 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.
Quick answers
Population
How does SeattleProcedural. Solo/Duo rank against other Rust servers?
Seven-day player hours put SeattleProcedural. Solo/Duo at #15,158, or #1,480 in North America, inside the top 68% of all ranked servers.
How busy is SeattleProcedural. Solo/Duo?
Of its 65 slots, SeattleProcedural. Solo/Duo is using 0 right now. Seven days of counting give an average of 0 players and a peak of 1.
Tags
What do the server tags on SeattleProcedural. Solo/Duo mean?
What the game's server browser reads from SeattleProcedural. Solo/Duo is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp65 (Max players): 65 slots are available; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code; ^m (Monthly): Monthly wipes take place, following Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; NA (North America): Its place in the server browser is under North America. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Who runs SeattleProcedural. Solo/Duo?
A rexisgodrust.ddnsfree.com hostname comes from SeattleProcedural. Solo/Duo and from 3 other servers we track, which suggests one operator runs them all.
Which Rust Population lists and filters include SeattleProcedural. Solo/Duo?
These Rust Population lists include SeattleProcedural. Solo/Duo: Community servers, field-listed, North American Rust servers and Vanilla Rust servers, counted. These are the filters it appears under when you browse the 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.
Wipe notes
What is the wipe schedule on SeattleProcedural. Solo/Duo?
Estimated from the force wipe, that is SeattleProcedural. Solo/Duo's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it runs now dates from 28 days ago. Its tags give a wipe schedule of one wipe a month.
Settings
Which map does SeattleProcedural. Solo/Duo run?
SeattleProcedural. Solo/Duo uses a map the game generates, procedural, at size 4,250 with seed 1788459108. You can look at it on RustMaps from this page: size and seed determine the map.
What are the rules and settings on SeattleProcedural. Solo/Duo?
Nothing in SeattleProcedural. Solo/Duo's name says how gather works. No limit is set beyond the standard 8 players per group. This server runs survival, the usual game, where you gather, build and raid. Combat between players, raids included, is permitted. You will find it under Community: it is a community server. The plugins it runs are Oxide. Vanilla is the label it uses: no changed rates, kits or rules: this is the game as Facepunch ships it. You play with Valve's anti-cheat on: VAC.
About the server
Which version of Rust does SeattleProcedural. Solo/Duo run?
The setup is Rust network protocol 2635 and build 168909 on Windows for SeattleProcedural. Solo/Duo. The protocol must match for you to join, and Steam updates it for you.
Does SeattleProcedural. Solo/Duo run smoothly?
It ran at 81 server fps on average over the last 48 hours, and never went below 58. The entity count reached 102,058: buildings, deployables and all other objects. Memory use peaked at 4,644 MB. What players experience as lag comes from low fps and a rising entity count.
Is SeattleProcedural. Solo/Duo online, and how reliable is it?
SeattleProcedural. Solo/Duo is up and running at the moment. The uptime it reports suggests a restart roughly 6 days 21 hours ago. It was up 99% of the time over the last 6 full days, 143 out of 144 hours. On 22 October 2026, Rust Population saw it for the first time.
Where is SeattleProcedural. Solo/Duo located?
With its NA tag, SeattleProcedural. Solo/Duo places itself in North America. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 50.125.205.168:28015.
How to join
How do I join SeattleProcedural. Solo/Duo?
To connect directly, open Rust's console with F1 and type client.connect 50.125.205.168:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://discord.com/invite/ZpqaKhXjkn.