Rust Server TrendsSeismic network · station log
Recording Stations11,652 Players32,618 Active2,799 Wipes · 3 h77 48 h

Station XX-15498 · no signal

FINAL ORDER STAGING

Offline 66.51.99.158:3700 checked 37d ago

Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,498
top 68%
Last wipe
62d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15498 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 549 on average
147/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
116/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
13/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 284 on average
18/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
13/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 249 on average
29/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on FINAL ORDER STAGING?

Generated by the game, the map on FINAL ORDER STAGING is procedural, size 4,500 with seed 1. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on FINAL ORDER STAGING?

No gather rate appears in the name of FINAL ORDER STAGING. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on FINAL ORDER STAGING right now?

A reading taken now finds FINAL ORDER STAGING offline; the most recent activity was 37 days 11 hours ago.

How does FINAL ORDER STAGING rank against other Rust servers?

The last seven days of player hours place FINAL ORDER STAGING at #15,498, in the top 68% of all ranked servers.

Server facts

How reliably does FINAL ORDER STAGING stay online?

FINAL ORDER STAGING is down at the moment; the last recorded contact was 37 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 16 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is FINAL ORDER STAGING hosted?

No region is published by FINAL ORDER STAGING. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 66.51.99.158:3700.

Which Rust version is FINAL ORDER STAGING running?

On Linux, FINAL ORDER STAGING runs Rust network protocol 2633 and build 165021. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

On what timetable does FINAL ORDER STAGING run its wipes?

The rhythm of FINAL ORDER STAGING cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 62 days 6 hours.

Server tags

What do the server tags on FINAL ORDER STAGING mean?

Tags published by FINAL ORDER STAGING and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165021 (Build): It runs game build 165021; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does FINAL ORDER STAGING appear?

You will find FINAL ORDER STAGING on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to FINAL ORDER STAGING?

Enter client.connect 66.51.99.158:3700 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165021
Build It runs game build 165021.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.