SeattleProcedural. Solo/Duo
NA 50.125.192.213:28015 checked 11m ago
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 41% of all ranked servers, top 68% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 21d 5h. The force wipe · high confidence
- wipe-day peak
- 1 players, last three wipes
Coming wipes
- 21d 5hThu 5 Nov, 19:00 UTCFW
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:18 UTCFW 13d 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
Quick answers
Player Numbers
SeattleProcedural. Solo/Duo ranking: what position does it hold?
In North America, SeattleProcedural. Solo/Duo is #1,258; across all ranked servers, #9,130 on player hours over the last seven days, in the top 41%.
Is SeattleProcedural. Solo/Duo busy?
The current player count for SeattleProcedural. Solo/Duo is 0, out of 65 slots. The seven-day average player count stands at 0, and the highest point was 1. Over the last 48 hours, the peak hour was 05:00 UTC, averaging 1 players.
Tags & Lists
SeattleProcedural. Solo/Duo tags: what do they indicate?
The game's server browser reads these tags from SeattleProcedural. Solo/Duo: gmrust (Game mode): Standard survival gameplay; mp65 (Max players): Slot count is 65; ts8 (Group limit): Teams are limited to 8, the default; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167781 (Build): Build 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code not set; ^m (Monthly): Monthly wipes, synced to Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules—the game as shipped; ^o (Oxide): Oxide (uMod) provides the plugin framework here; NA (North America): In the server browser it appears under North America. Current players, queue and world creation time come from the tags and appear at the top of this page.
SeattleProcedural. Solo/Duo operator: who is it?
Most likely the same operator runs SeattleProcedural. Solo/Duo and 1 other server we track: all publish a rexisgodrust.ddnsfree.com hostname.
Which lists and filters on BestRustServers.xyz contain SeattleProcedural. Solo/Duo?
The BestRustServers.xyz lists that include SeattleProcedural. Solo/Duo are: Rust community servers, ranked, North American Rust servers and Vanilla-tagged Rust servers. It appears under these filters 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; Last wipe: In the last 2 weeks.
Server Details
What Rust version is SeattleProcedural. Solo/Duo on?
On Windows, SeattleProcedural. Solo/Duo runs Rust network protocol 2634 and build 167781. Joining requires the same protocol; Steam updates your game for you.
How smooth is the performance on SeattleProcedural. Solo/Duo?
Over 48 hours, it averaged 104 server fps; the lowest was 77. It held up to 101,112 entities: everything from buildings to deployables in the world. At its highest, memory usage was 4,129 MB. A climbing entity count and low fps are felt by players as lag.
What is the uptime and reliability of SeattleProcedural. Solo/Duo?
At the moment, SeattleProcedural. Solo/Duo is up. According to its reported uptime, the last restart was about 7 hours ago. It was up 98% of the time over the last 7 full days, 165 of 168 hours. The first time BestRustServers.xyz saw it was on 1 October 2026.
Where can SeattleProcedural. Solo/Duo be found?
With its NA tag, SeattleProcedural. Solo/Duo lists itself in North America. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 50.125.192.213:28015 is its address.
Settings & Map
SeattleProcedural. Solo/Duo map: which one is it?
Generated by the game, the map on SeattleProcedural. Solo/Duo is procedural, size 4,250, seed 1788459108. View it on RustMaps from this page: identical size and seed produce an identical map.
SeattleProcedural. Solo/Duo rules and settings: what are they?
No gather rate appears in the name of SeattleProcedural. Solo/Duo. With no stated limit, groups default to 8 players. It runs survival, gather, build, raid: the standard game. Fighting and raiding between players are allowed. Community is its browser category. Oxide plugins are used. Vanilla is the label it uses: no changed rates, kits or rules—the game as shipped. VAC: on.
Wipe Schedule
SeattleProcedural. Solo/Duo wipe schedule: what does it show?
SeattleProcedural. Solo/Duo wipes at the monthly force wipe only. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been running since 13 days 19 hours. The tags declare wipes once a month.
What happens on wipe day on SeattleProcedural. Solo/Duo?
The average busiest point of its recent wipes was 1 players. 2 hours after the latest wipe, the crowd hit its peak.
Join Server
SeattleProcedural. Solo/Duo joining: how is it done?
Use the F1 console: client.connect 50.125.192.213:28015. Launch Rust on this page does the same by opening Rust through Steam and connecting. https://discord.com/invite/ZpqaKhXjkn is its website.
Server tags
Published as mp65,ptrak,$r?,v2634,^m,^v,NA,gmrust,cs167781,ts8,^o
Game
gmrust- Game mode Standard survival gameplay.
mp65- Max players Slot count is 65.
ts8- Group limit Teams are limited to 8, the default.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167781- Build Build 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code not set.
Wipe schedule
^m- Monthly Monthly wipes, synced to Facepunch's force wipe.
Difficulty
^v- Vanilla No changed rates, kits or rules—the game as shipped.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
Region
NA- North America In the server browser it appears under North America.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.