SeattleProcedural. Solo/Duo
Online 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
daily · 1 is bestTop 39% of all ranked servers, top 66% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 18d 9h. The force wipe · high confidence
Coming wipes
- 18d 9hThu 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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:18 UTC FW16d 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
- 126/ 200
- 106/ 200
- 67/ 400
- 58/ 200
- 58/ 100
- 44/ 200
Quick answers
Tags and filters
Where does SeattleProcedural. Solo/Duo appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry SeattleProcedural. Solo/Duo are: Rust community servers, going deep, North American Rust server list and Vanilla Rust servers. You can find it on the server list by these filters: 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 comes from SeattleProcedural. Solo/Duo, and from 1 other server we track, which points to the same operator running both.
What's the meaning of the tags on SeattleProcedural. Solo/Duo?
The server browser shows these tags for SeattleProcedural. Solo/Duo: gmrust (Game mode): This is the standard Rust survival experience; mp65 (Max players): The slot count is 65; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^m (Monthly): Monthly wipes, timed with the Facepunch force wipe; ^v (Vanilla): It's the vanilla game: rates, kits and rules are all standard; ^o (Oxide): Plugins run through Oxide (uMod); NA (North America): The server browser lists it under North America. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
How well does SeattleProcedural. Solo/Duo perform?
It averaged 91 server fps over the last 48 hours, with a low of 74. Buildings, deployables and all other world objects added up to as many as 101,265 entities. The top memory figure was 3,922 MB. Players experience lag when fps drops and entities climb.
What's the location of SeattleProcedural. Solo/Duo?
SeattleProcedural. Solo/Duo lists North America as its location, with the NA tag. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 50.125.192.213:28015.
Is SeattleProcedural. Solo/Duo up, and how often does it stay online?
Right now SeattleProcedural. Solo/Duo is online. Its reported uptime shows a restart about 3 days 3 hours ago. It was up 100% of the time over the last full 7 days, 168 of 168 hours. The first sighting by Rust Going Deep was on 1 October 2026.
What is the Rust version for SeattleProcedural. Solo/Duo?
On Windows, SeattleProcedural. Solo/Duo runs Rust network protocol 2634 and build 167781. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
When does SeattleProcedural. Solo/Duo wipe?
One wipe a month is all SeattleProcedural. Solo/Duo does, and that is the force wipe. All Rust servers wipe at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 16 days 15 hours is how long ago this world came into being. Its tags publish a wipe schedule that runs monthly.
What happens on wipe day at SeattleProcedural. Solo/Duo?
The average peak across recent wipes is 1 players. The peak crowd on the latest wipe came 2 hours in.
Settings and map
What settings and rules have been applied to SeattleProcedural. Solo/Duo?
The name of SeattleProcedural. Solo/Duo contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. Oxide plugins are running here. Vanilla is its own description: it's the vanilla game: rates, kits and rules are all standard. VAC, Valve's anti-cheat, is enabled.
What's the map on SeattleProcedural. Solo/Duo?
SeattleProcedural. Solo/Duo uses a procedural map of size 4,250 with seed 1788459108, made by the game. RustMaps can display it from this page because the same size and seed yield the same map.
Player count
How many players are on SeattleProcedural. Solo/Duo?
Out of 65 slots, 0 are filled on SeattleProcedural. Solo/Duo right now. For the past week, players averaged 0 with a high of 1. The busiest point in the last 48 hours was 18:00 UTC, averaging 1 players.
What's SeattleProcedural. Solo/Duo's rank among Rust servers?
Over the last seven days SeattleProcedural. Solo/Duo sits at #8,696 on player hours, which is #1,219 in North America and inside the top 39% of all ranked servers.
How to join
What's the way to join SeattleProcedural. Solo/Duo?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 50.125.192.213:28015. You can find its website at https://discord.com/invite/ZpqaKhXjkn.
