Offline NA 50.125.192.213:28015 checked 7d ago
SeattleProcedural. Solo/Duo
Connect
srv = rust.server("50.125.192.213:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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, measured since 1 Oct. 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 bestTop 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:18 UTC FW28d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
4250 · seed 1788459108
- map
- Procedural Map
- size
- 4250
- seed
- 1788459108
Server
srv.info()- address
- 50.125.192.213:28015
- region
- NA
- max players
- 65
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 18:18 UTC
- hostname
- rexisgodrust.ddnsfree.com
- first seen
- 1 Oct 2026
Operator · rexisgodrust.ddnsfree.com
rust.servers(operator="rexisgodrust.ddnsfree.com").sort_values("players")| server | players | |
|---|---|---|
| 0 | SeattleProcedural. Solo/Duo | 0/65 |
| 1 | SeattleProcedural. Solo/Duo | 0/65 |
| 2 | SeattleProcedural. Solo/Duo | 0/65 |
4 servers publish a rexisgodrust.ddnsfree.com hostname.
About this server · in its own words
print(srv.description)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 · 126 on average | 96/200 |
| 1 | Rusty Moose |US Monthly| | NA · groups of 12+ · monthly · 109 on average | 79/200 |
| 2 | [US East] Facepunch Premium 1 | NA · groups of 8+ · monthly · 75 on average | 50/400 |
| 3 | RustLands | Monthly Large | No BP Wipe | NOOB FRIENDLY | NA · groups of 50+ · monthly · 59 on average | 64/225 |
| 4 | PICKLE DUO MONTHLY | No BP Wipe | Low Upkeep | Duo Solo | NA · groups of 20+ · monthly · 35 on average | 16/200 |
| 5 | Rusticated.com - US Premium Long | NA · groups of 16+ · monthly · 33 on average | 29/150 |
Quick answers
From the figures on this page.
Player counts
What position does SeattleProcedural. Solo/Duo take in the server rankings?
Player hours over the last seven days: #15,344 for SeattleProcedural. Solo/Duo, #1,522 in North America, within the top 69% of the ranked set.
How full does SeattleProcedural. Solo/Duo run?
The current row shows SeattleProcedural. Solo/Duo offline; the last response was 7 days 21 hours ago.
About the server
What Rust version does SeattleProcedural. Solo/Duo run?
Rust network protocol 2634 and build 167781 on Windows is what SeattleProcedural. Solo/Duo runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is SeattleProcedural. Solo/Duo, and is it up?
SeattleProcedural. Solo/Duo is offline at this refresh; the last response came 7 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.
Which location does SeattleProcedural. Solo/Duo run from?
In North America, SeattleProcedural. Solo/Duo lists itself, using the NA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 50.125.192.213:28015 is its address.
Settings and map
Which rules apply on SeattleProcedural. Solo/Duo, and what settings?
The name SeattleProcedural. Solo/Duo carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. The plugin count is Oxide. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.
Which map has SeattleProcedural. Solo/Duo loaded?
SeattleProcedural. Solo/Duo runs a procedural map of size 4,250 with seed 1788459108, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does SeattleProcedural. Solo/Duo wipe, and how often?
A single wipe each month, the force wipe, is all SeattleProcedural. Solo/Duo does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 28 days 1 hours ago. Its tags carry a monthly wipe schedule.
On SeattleProcedural. Solo/Duo, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 2 hours after it began.
Tags and filters
Where does SeattleProcedural. Solo/Duo appear among Rust Data lists and filters?
These Rust Data lists include SeattleProcedural. Solo/Duo: Rust community servers, unfiltered, North America Rust servers and Vanilla Rust servers. Under these filters on the server list, it is listed: 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.
Who operates SeattleProcedural. Solo/Duo?
A rexisgodrust.ddnsfree.com hostname is published by SeattleProcedural. Solo/Duo and by 3 other servers we track, which suggests the same operator runs them.
How should you read the server tags on SeattleProcedural. Solo/Duo?
The game's server browser reads these tags from SeattleProcedural. Solo/Duo: gmrust (Game mode): Survival play, standard Rust; mp65 (Max players): 65 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not 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): Runs on Oxide (uMod) for plugins; NA (North America): In the server browser it sits under North America. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into SeattleProcedural. Solo/Duo?
The manual route: launch Rust, F1, then client.connect 50.125.192.213:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/ZpqaKhXjkn is the website recorded for it.