STT15344
SeattleProcedural. Solo/Duo
Offline NA 50.125.192.213:28015 checked 7d 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
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 7d 2h.
The force wipe · high confidence
Coming wipes
- 7d 2hThu 5 Nov, 19:00 UTCFW
- 35d 2hThu 3 Dec, 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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:18 UTC FW27d 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.
-
01COMPlayers 65/200
-
02COMPlayers 59/200
-
03COMPlayers 44/400
-
04COMPlayers 30/225
-
05COMPlayers 17/200
-
06COMPlayers 19/150
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show SeattleProcedural. Solo/Duo?
These Rust Tracker lists carry SeattleProcedural. Solo/Duo: Community servers, no tags, North America: live server tracking and Vanilla Rust servers, tracked live. These filters surface it 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.
How should you read the tags on SeattleProcedural. Solo/Duo?
These tags are published by SeattleProcedural. Solo/Duo for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp65 (Max players): 65 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Follows Facepunch's force wipe: one wipe per month; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); NA (North America): The server browser lists it under North America. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Who is behind SeattleProcedural. Solo/Duo?
Same operator, most likely: SeattleProcedural. Solo/Duo publishes a rexisgodrust.ddnsfree.com hostname, and 3 other servers we track publish it as well.
Wipe Times
What happens on SeattleProcedural. Solo/Duo on wipe day?
Recent wipes averaged a peak of 1 players. 2 hours after the latest wipe, the crowd peaked.
On what schedule does SeattleProcedural. Solo/Duo wipe?
Once a month is the wipe rate at SeattleProcedural. Solo/Duo, on the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its world went live 27 days 21 hours. Tags list a monthly wipe schedule.
Location and Status
How reliable is SeattleProcedural. Solo/Duo, and is it online now?
Offline: SeattleProcedural. Solo/Duo confirmed offline, last seen 7 days 17 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. Rust Tracker logged it first on 1 October 2026.
What Rust version is SeattleProcedural. Solo/Duo on?
Confirmed for SeattleProcedural. Solo/Duo: Rust network protocol 2634 and build 167781, Windows. Steam updates it for you; your game must share the protocol to join.
Which location is SeattleProcedural. Solo/Duo in?
In North America, under its NA tag, is where SeattleProcedural. Solo/Duo lists itself. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 50.125.192.213:28015.
Player Count
What is the player count on SeattleProcedural. Solo/Duo?
Offline now for SeattleProcedural. Solo/Duo, last seen 7 days 17 hours ago.
How does SeattleProcedural. Solo/Duo compare in the rankings?
Top 69% of all ranked servers and #1,522 in North America: SeattleProcedural. Solo/Duo ranks #15,344 on player hours over the last seven days.
Map and Rules
Which settings and rules are confirmed on SeattleProcedural. Solo/Duo?
No gather rate appears in SeattleProcedural. Solo/Duo's name. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Community, as a community server. Oxide plugins run on it. Vanilla is its own label: facepunch's game unaltered: rates, kits and rules unchanged. On: VAC, Valve's anti-cheat.
Which map is loaded on SeattleProcedural. Solo/Duo?
A procedural map of size 4,250 runs on SeattleProcedural. Solo/Duo, generated by the game from seed 1788459108. Same size, same seed, same map. RustMaps shows it, linked from this page.
How to Join
What is the way to join SeattleProcedural. Solo/Duo?
To connect: start Rust, press F1, enter client.connect 50.125.192.213:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://discord.com/invite/ZpqaKhXjkn.
Server tags
What each one means.
Published as mp65,ptrak,$r?,v2634,^m,^v,NA,gmrust,cs167781,ts8,^o
Game
gmrust
mp65
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^m
Difficulty
^v
Mods and access
^o
Region
NA
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.