Offline NA 50.125.192.168:28015 checked 44d ago
SeattleProcedural. Solo/Duo
Connect
srv = rust.server("50.125.192.168:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 8h. # The force wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 50.125.192.168:28015
- region
- NA
- max players
- 65
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 3 Sep 2026, 18:32 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustopia.gg - US Large | NA · groups of 16+ · monthly · 123 on average | 37/200 |
| 1 | Rusty Moose |US Monthly| | NA · groups of 12+ · monthly · 106 on average | 34/200 |
| 2 | [US East] Facepunch Premium 1 | NA · groups of 8+ · monthly · 73 on average | 21/400 |
| 3 | RustLands | Monthly Large | No BP Wipe | NOOB FRIENDLY | NA · groups of 50+ · monthly · 61 on average | 52/225 |
| 4 | PICKLE DUO MONTHLY | No BP Wipe | Low Upkeep | Duo Solo | NA · groups of 20+ · monthly · 32 on average | 13/200 |
| 5 | Rusticated.com - US Premium Long | NA · groups of 16+ · monthly · 32 on average | 18/150 |
Quick answers
From the figures on this page.
Population data
How does SeattleProcedural. Solo/Duo compare in the rankings?
Player hours over the last seven days: #15,392 for SeattleProcedural. Solo/Duo, #1,582 in North America, within the top – of the ranked set.
How many players does SeattleProcedural. Solo/Duo hold at once?
The current row shows SeattleProcedural. Solo/Duo offline; the last response was 44 days 15 hours ago.
About the server
What is the Rust version on SeattleProcedural. Solo/Duo?
Rust network protocol 2633 and build 163794 on Windows is what SeattleProcedural. Solo/Duo runs. Steam updates your game for you, but the protocol must match to join.
How reliable is SeattleProcedural. Solo/Duo, and is it online now?
The latest sample has SeattleProcedural. Solo/Duo offline, with a last sighting 44 days 15 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does SeattleProcedural. Solo/Duo run from?
With its NA tag, SeattleProcedural. Solo/Duo lists itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 50.125.192.168:28015.
Rules, settings, map
What rules and settings are recorded for SeattleProcedural. Solo/Duo?
No gather rate appears in the name: SeattleProcedural. Solo/Duo. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. Plugins installed: Oxide. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.
Which map has SeattleProcedural. Solo/Duo loaded?
SeattleProcedural. Solo/Duo runs a procedural map, which the game generates.
Wipe data
When does SeattleProcedural. Solo/Duo wipe, and how often?
An estimate from the force wipe gives SeattleProcedural. Solo/Duo's next wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 56 days 15 hours ago. A monthly wipe schedule is published in its tags.
Tags, lists
Where does SeattleProcedural. Solo/Duo appear among Rust Data lists and filters?
The Rust Data lists that SeattleProcedural. Solo/Duo fits are: Rust community servers, unfiltered, North America Rust servers and Vanilla Rust servers. These filters bring it up 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 server tags on SeattleProcedural. Solo/Duo?
These tags are published by SeattleProcedural. Solo/Duo and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp65 (Max players): Slot count: 65; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); NA (North America): In the server browser it sits under North America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into SeattleProcedural. Solo/Duo?
Enter client.connect 50.125.192.168:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.