DWG RG-S16599Server sheetchecked 28d ago
SeattleProcedural. Solo/Duo
Offline NA 50.125.201.106:28015 checked 28d 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 70% of all ranked servers, top 83% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. 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.
Similar servers
Quick answers
Server data
What uptime is recorded for SeattleProcedural. Solo/Duo, and is it up?
Last seen 28 days 7 hours ago; right now SeattleProcedural. Solo/Duo is offline. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 16 September 2026.
What location is recorded for SeattleProcedural. Solo/Duo?
In North America SeattleProcedural. Solo/Duo lists itself, tagged NA. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 50.125.201.106:28015 is its address.
On which Rust version is SeattleProcedural. Solo/Duo running?
Rust network protocol 2633 and build 165217 on Windows: that is what SeattleProcedural. Solo/Duo runs. Steam updates your game, which must be on the same protocol for you to join.
Population
What does the population history show for SeattleProcedural. Solo/Duo?
No response from SeattleProcedural. Solo/Duo; the server was last seen 28 days 7 hours ago.
In the rankings, which position does SeattleProcedural. Solo/Duo hold?
The same seven-day player-hour count places SeattleProcedural. Solo/Duo at #1,647 within North America, #16,599 across all ranked servers and in the top 70% of them.
Wipe times
What wipe schedule has been recorded for SeattleProcedural. Solo/Duo?
Estimated from the force wipe is when SeattleProcedural. Solo/Duo's next wipe falls. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 55 days 19 hours ago the current world was made. A wipe every month is the schedule its tags set out.
Rules and settings
Which settings does SeattleProcedural. Solo/Duo run, and what rules?
Gather rate for SeattleProcedural. Solo/Duo: not stated in the name. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Community. The plugin count is Oxide. It describes itself as vanilla, by which it means no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat: VAC, from Valve, is on.
What is the map for SeattleProcedural. Solo/Duo?
Size 4,250 with seed 4683: that is the procedural map SeattleProcedural. Solo/Duo runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
Where does SeattleProcedural. Solo/Duo appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry SeattleProcedural. Solo/Duo are: Rust community servers, plotted, Rust server list: North America and Vanilla Rust servers. On the server list, these filters 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.
On SeattleProcedural. Solo/Duo, what is meant by each tag?
gmrust (Game mode): Standard survival, as Rust plays; mp65 (Max players): 65 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): To join, your game must be on protocol 2633; cs165217 (Build): 165217 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework is Oxide (uMod); NA (North America): The server browser lists it under North America are the tags SeattleProcedural. Solo/Duo publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Who is the operator of SeattleProcedural. Solo/Duo?
The same operator most likely runs SeattleProcedural. Solo/Duo and 3 other servers we track, since all publish a rexisgodrust.ddnsfree.com hostname.
Connect
How is SeattleProcedural. Solo/Duo joined?
In Rust, press F1 and type client.connect 50.125.201.106:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://discord.com/invite/ZpqaKhXjkn.
Server tags
Published as mp65,ptrak,$r?,v2633,^m,^v,NA,gmrust,cs165217,ts8,^o
Game
gmrust
mp65
ts8
v2633
cs165217
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.