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.
AveragePeak
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 7d 5h.
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
Where in the world is SeattleProcedural. Solo/Duo?
You'll see SeattleProcedural. Solo/Duo listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 50.125.197.83:28015 is the address to use.
How reliable is SeattleProcedural. Solo/Duo, and is it up?
You cannot join now: SeattleProcedural. Solo/Duo is offline, last seen 43 days 10 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 15 September 2026.
Which Rust version is SeattleProcedural. Solo/Duo running?
You will find SeattleProcedural. Solo/Duo on Rust network protocol 2633 and build 163794, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does SeattleProcedural. Solo/Duo wipe its map?
the force wipe gives the basis for estimating SeattleProcedural. Solo/Duo's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 55 days 18 hours. The tags show a monthly wipe schedule.
Player count
Where does SeattleProcedural. Solo/Duo sit among Rust servers?
Over the last seven days, SeattleProcedural. Solo/Duo has #12,570 for player hours, in the top – of all ranked servers and #1,444 in North America.
How many players does SeattleProcedural. Solo/Duo usually have?
The last sighting of SeattleProcedural. Solo/Duo was 43 days 10 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): This one runs plain Rust survival, with nothing altered; mp65 (Max players): 65 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Oxide (uMod) provides the plugin framework here; NA (North America): In the server browser it appears under North America. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature SeattleProcedural. Solo/Duo?
Rust Server Score lists that include SeattleProcedural. Solo/Duo: Best community servers, graded, North America Rust servers, graded and Vanilla Rust servers, graded. 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.
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. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Oxide plugins are running on it. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
SeattleProcedural. Solo/Duo runs which map?
The game generates a procedural map for SeattleProcedural. Solo/Duo.
Connecting
How do you get onto SeattleProcedural. Solo/Duo?
Enter client.connect 50.125.197.83: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 modeThis one runs plain Rust survival, with nothing altered.
mp65
Max players65 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
NA
North AmericaIn the server browser it appears 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.
Not enough figures yet to write a report. Check back after a few days on the list.