Rust Server TrendsSeismic network · station log
Recording Stations11,644 Players39,744 Active2,959 Wipes · 3 h78 48 h

Station XX-16810 · no signal

ORAX STAGING TEST

Offline 188.72.46.209:28025 checked 27d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,810
top 70%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16810 · 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 10 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. 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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

Top 70% 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 · 530 on average
257/ 300
Rustoria.co - EU Main EU · groups of 16+ · weekly · 329 on average
15/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 327 on average
30/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
121/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 279 on average
44/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 264 on average
48/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on ORAX STAGING TEST?

The map on ORAX STAGING TEST is procedural, produced by the game.

Which settings and rules apply on ORAX STAGING TEST?

The name of ORAX STAGING TEST gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on ORAX STAGING TEST?

ORAX STAGING TEST is not responding at this moment and is offline, last seen 27 days 13 hours ago.

How does ORAX STAGING TEST rank against other Rust servers?

The last seven days of player hours place ORAX STAGING TEST at #16,810, in the top 70% of all ranked servers.

Operator and location

How reliably does ORAX STAGING TEST stay online?

No contact with ORAX STAGING TEST right now, and the last recorded contact was 27 days 13 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 30 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does ORAX STAGING TEST run from?

No region is published by ORAX STAGING TEST. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 188.72.46.209:28025.

What build of Rust does ORAX STAGING TEST use?

On Windows, ORAX STAGING TEST runs Rust network protocol 2634 and build 166318. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

How often does ORAX STAGING TEST wipe, and on which days?

The rhythm of ORAX STAGING TEST cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 13 hours.

Server tags

What do the server tags on ORAX STAGING TEST mean?

These are the tags ORAX STAGING TEST publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166318 (Build): The game build is 166318; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does ORAX STAGING TEST appear?

These Rust Server Trends lists include ORAX STAGING TEST: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to ORAX STAGING TEST?

To join, enter client.connect 188.72.46.209:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166318,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players 10 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166318
Build The game build is 166318.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.