RUST METRICSFlight deck · live data
Data live Servers11,713 Players47,275 Populated3,205 Fresh wipes 3 h100 Scan5 min
‹ All servers66.51.99.158:3700
Offline Full Queue Fresh wipe Wipe due No query

FINAL ORDER STAGING

Offline 66.51.99.158:3700 checked 37d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,498top 68%
Last wipe62d agono schedule published
Next wipe–no wipe seen yet
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, measured since 17 Sep. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 68% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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

Wipe timing

What wipe timing does FINAL ORDER STAGING follow?

The rhythm of FINAL ORDER STAGING's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 62 days 2 hours ago the current world was made.

Tags

How should you read the tags on FINAL ORDER STAGING?

These are the tags FINAL ORDER STAGING publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165021 (Build): Build 165021; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does FINAL ORDER STAGING appear in Rust Metrics lists and filters?

These Rust Metrics lists carry FINAL ORDER STAGING: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does FINAL ORDER STAGING hold among Rust servers?

Player hours over seven days put FINAL ORDER STAGING at #15,498, in the top 68% of all ranked servers.

How full does FINAL ORDER STAGING get?

Status for FINAL ORDER STAGING: offline. Last seen 37 days 8 hours ago.

Server details

What location is FINAL ORDER STAGING hosted in?

No region comes from FINAL ORDER STAGING. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 66.51.99.158:3700.

What Rust version is FINAL ORDER STAGING on?

Reading: FINAL ORDER STAGING, Rust network protocol 2633 and build 165021, Linux. Matching protocol is required to join. Let Steam update your game.

What is the uptime on FINAL ORDER STAGING, and is it online?

FINAL ORDER STAGING reports offline. The last reading came 37 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 16 September 2026.

Rules and settings

How is FINAL ORDER STAGING configured, and what rules are in force?

No gather rate appears in the name: FINAL ORDER STAGING. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on FINAL ORDER STAGING?

From seed 1, the game generates the procedural map on FINAL ORDER STAGING. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto FINAL ORDER STAGING?

To join: start Rust, press F1 and type client.connect 66.51.99.158:3700. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165021,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165021
Build Build 165021.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.