RUST METRICSFlight deck · live data
Data live Servers11,633 Players40,937 Populated2,826 Fresh wipes 3 h115 Scan5 min
‹ All servers50.125.192.168:28015
Offline Full Queue Fresh wipe Wipe due No query

SeattleProcedural. Solo/Duo

Offline NA 50.125.192.168:28015 checked 44d ago

monthly wipes vanillaoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 16 32 49 65 PAX 0 /65

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,392#1582 in NA
Last wipe56d agomonthly schedule
Next wipe6d 14hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 6d 14h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does SeattleProcedural. Solo/Duo follow?

An estimate from the force wipe gives SeattleProcedural. Solo/Duo's next wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 56 days 9 hours ago. Its tags carry a monthly wipe schedule.

Tag meanings

Which tags does SeattleProcedural. Solo/Duo carry, and what do they mean?

These are the tags SeattleProcedural. Solo/Duo publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp65 (Max players): Slots: 65; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; NA (North America): North America is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does SeattleProcedural. Solo/Duo appear in Rust Metrics lists and filters?

These Rust Metrics lists carry SeattleProcedural. Solo/Duo: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: 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.

Occupancy

Where does SeattleProcedural. Solo/Duo sit in the rankings?

Ranked by seven-day player hours, SeattleProcedural. Solo/Duo sits at #15,392 and #1,582 in North America, inside the top –.

What is the population on SeattleProcedural. Solo/Duo?

SeattleProcedural. Solo/Duo is not responding; status offline, last seen 44 days 9 hours ago.

Server

Which location does SeattleProcedural. Solo/Duo run from?

SeattleProcedural. Solo/Duo gives North America as its location, with the NA tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 50.125.192.168:28015.

What Rust version is SeattleProcedural. Solo/Duo on?

Rust network protocol 2633 and build 163794 on Windows is the build SeattleProcedural. Solo/Duo runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is SeattleProcedural. Solo/Duo, and is it online now?

SeattleProcedural. Solo/Duo reports offline. The last reading came 44 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is SeattleProcedural. Solo/Duo configured, and what rules are in force?

Check: gather rate. The name SeattleProcedural. Solo/Duo does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. VAC is on. That is Valve's anti-cheat.

What map is SeattleProcedural. Solo/Duo on?

Procedural map on SeattleProcedural. Solo/Duo, made by the game's generator.

Connection

How do you connect to SeattleProcedural. Solo/Duo?

Press F1 in Rust and enter client.connect 50.125.192.168:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp65,ptrak,$r?,v2633,^m,^v,NA,gmrust,cs163794,ts8,^o

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp65
Max players Slots: 65.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

Region

NA
North America North America is the browser category it sits in.

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.