FINAL ORDER STAGING
Key statistics
the figures behind the quote- Players now
- 0/ 50 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,498 top 68%
- Rank · 7d ago
- #15,850 ▲352 places up
- Last wipe
- 47d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- 4500 Procedural Map · seed 1
- First seen
- 16 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rustoria.co - EU East LongEU · groups of 12+ · monthly · 398 on average | 303/375 | ▲+81+36.5% | |
| 2 | Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 337 on average | 261/300 | ▲+55+26.6% | |
| 3 | Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 329 on average | 364/375 | ▼−1−0.2% | |
| 4 | Rustoria.co - EU LongEU · groups of 14+ · monthly · 319 on average | 251/300 | ▲+63+33.3% | |
| 5 | Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average | 31/250 | ▼−3−9.9% | |
| 6 | Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 271 on average | 255/400 | ▲+89+53.8% |
Quick answers
from the figures on this pageMap and Rules
How is FINAL ORDER STAGING configured in terms of rules and settings?
The name of FINAL ORDER STAGING carries no gather rate. Up to 8 players per group, which is the game's default. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. The server browser lists it under Community, as a community server. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on FINAL ORDER STAGING?
A procedural map of size 4,500 with seed 1 runs on FINAL ORDER STAGING, created by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.
Population
Where does FINAL ORDER STAGING sit in the rankings?
In the top 68% of all ranked servers, FINAL ORDER STAGING is #15,498 on player hours over the last seven days.
What is the population on FINAL ORDER STAGING?
At present, FINAL ORDER STAGING is offline; the last sighting was 23 days 5 hours ago.
Wipe Schedule
When does FINAL ORDER STAGING schedule its wipes?
The record holds too few of FINAL ORDER STAGING's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 47 days 23 hours.
Server Overview
Where can FINAL ORDER STAGING be found?
No region is published by FINAL ORDER STAGING. Rust Analytics reports the location a server claims, not the machine's actual location. 66.51.99.158:3700 is its address.
What Rust version is FINAL ORDER STAGING running?
Rust network protocol 2633 and build 165021 on Linux is what FINAL ORDER STAGING runs. Joining requires the same protocol on your game, which Steam updates.
How reliable is FINAL ORDER STAGING and is it currently online?
FINAL ORDER STAGING is down. The last time we saw it was 23 days 5 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. 16 September 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on FINAL ORDER STAGING?
Published by FINAL ORDER STAGING for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165021 (Build): Build 165021; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does FINAL ORDER STAGING show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature FINAL ORDER STAGING: Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Joining the Server
What is the process to join FINAL ORDER STAGING?
The console route: start Rust, press F1, enter client.connect 66.51.99.158:3700. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2633,gmrust,cs165021,ts8
Game
gmrust
mp50
ts8
v2633
cs165021
ptrak
$r?
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.