Working its way up from the back of the class: #15,344 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
25/ 100
F
Lost ground: down 7,789 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
6d 23hThu 5 Nov, 19:00 UTCFW
34d 23hThu 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 UTCFW28d 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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is SeattleProcedural. Solo/Duo based in?
You'll see SeattleProcedural. Solo/Duo listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 50.125.192.213:28015.
How dependable is SeattleProcedural. Solo/Duo, and is it online at the moment?
The server is down: SeattleProcedural. Solo/Duo is offline now, with the last sighting 7 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 1 October 2026.
Which Rust version is SeattleProcedural. Solo/Duo running?
The server SeattleProcedural. Solo/Duo is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does SeattleProcedural. Solo/Duo wipe, and how often?
SeattleProcedural. Solo/Duo wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 28 days 1 hours. The tags show a monthly wipe schedule.
What should you expect from wipe day on SeattleProcedural. Solo/Duo?
Recent wipes have peaked at 1 players on average. Peak numbers came 2 hours into the latest wipe.
Population
Where does SeattleProcedural. Solo/Duo sit among Rust servers?
Over the last seven days, SeattleProcedural. Solo/Duo has #15,344 for player hours, in the top 69% of all ranked servers and #1,522 in North America.
Is SeattleProcedural. Solo/Duo a busy server?
SeattleProcedural. Solo/Duo is offline at the moment; the last time it was seen was 7 days 20 hours ago.
Tags and filters
What do SeattleProcedural. Solo/Duo's tags stand for?
The game's browser takes its cue from the tags SeattleProcedural. Solo/Duo has set: gmrust (Game mode): Rust survival, played by the standard rules; mp65 (Max players): The server holds 65 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): The plugin framework in use is Oxide (uMod); NA (North America): The server browser lists it under North America. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Who is behind SeattleProcedural. Solo/Duo?
A rexisgodrust.ddnsfree.com hostname is published by SeattleProcedural. Solo/Duo and by 3 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show SeattleProcedural. Solo/Duo?
These Rust Server Score lists count SeattleProcedural. Solo/Duo among them: Best community servers, graded, North America Rust servers, graded and Vanilla Rust servers, graded. It shows under the following filters 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.
Server rules
How is SeattleProcedural. Solo/Duo set up, and what rules does it keep?
You will find no gather rate in the name of SeattleProcedural. Solo/Duo. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
Can you tell me which map SeattleProcedural. Solo/Duo uses?
The game generates the procedural map on SeattleProcedural. Solo/Duo at size 4,250 with seed 1788459108. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join SeattleProcedural. Solo/Duo?
Enter client.connect 50.125.192.213:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/ZpqaKhXjkn.
Server tags
what each one means
Published asmp65,ptrak,$r?,v2634,^m,^v,NA,gmrust,cs167781,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp65
Max playersThe server holds 65 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
Region
NA
North AmericaThe server browser lists it under North America.
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.
A term to build on. Even marks across the subjects, from F to F.