Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 15h.
The force wipe
Wipes
newest first
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
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. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 50.125.192.168:28015.
How dependable is SeattleProcedural. Solo/Duo, and is it online at the moment?
You cannot join now: SeattleProcedural. Solo/Duo is offline, last seen 44 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is SeattleProcedural. Solo/Duo running?
The server SeattleProcedural. Solo/Duo is on Rust network protocol 2633 and build 163794 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does SeattleProcedural. Solo/Duo reset?
the force wipe gives the basis for estimating SeattleProcedural. Solo/Duo's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 56 days 9 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player count
Where does SeattleProcedural. Solo/Duo sit among Rust servers?
Over the last seven days, SeattleProcedural. Solo/Duo has #15,392 for player hours, in the top – of all ranked servers and #1,582 in North America.
Is SeattleProcedural. Solo/Duo a busy server?
The last sighting of SeattleProcedural. Solo/Duo was 44 days 9 hours ago, and it is offline right now.
Tags
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): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); NA (North America): You will find it under North America in the browser. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does SeattleProcedural. Solo/Duo appear in the Rust Server Score lists and filters?
Rust Server Score lists that include SeattleProcedural. Solo/Duo: Best community servers, graded, North America Rust servers, graded and Vanilla Rust servers, graded. You can find it under these server-list 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.
Server rules
Which rules does SeattleProcedural. Solo/Duo enforce, and what are its settings?
Nothing in the name of SeattleProcedural. Solo/Duo states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. Plugins on it number Oxide. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Which map is in play on SeattleProcedural. Solo/Duo?
A procedural map, generated by the game, is what SeattleProcedural. Solo/Duo runs.
Getting in
What is the way to join SeattleProcedural. Solo/Duo?
Enter client.connect 50.125.192.168:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp65,ptrak,$r?,v2633,^m,^v,NA,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp65
Max playersThe server holds 65 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
NA
North AmericaYou will find it under North America in the browser.
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.
Not enough figures yet to write a report. Check back after a few days on the list.