Rust Server TrendsSeismic network · station log
Recording Stations11,628 Players32,585 Active2,817 Wipes · 3 h70 48 h

Station XX-9428 · no signal

Operational Control Center

Offline 84.174.76.43:28025 checked 4d ago

moddedoxide
Connect
Players now
1/ 3
33% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak 1
Rank
#9,428
top 42%
Last wipe
5d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-9428 · 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
1of 3 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
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 11:00 UTC5d ago M0.0rising 1 – running 0

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
ShockRust | Blue | NoLimit no group limit · 151 on average
48/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
126/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
67/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
16/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
6/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on Operational Control Center?

You will find no gather rate in the name of Operational Control Center. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on Operational Control Center?

A reading taken now finds Operational Control Center offline; the most recent activity was 4 days 11 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does Operational Control Center rank against other Rust servers?

Over the last seven days, Operational Control Center recorded enough player hours to reach #9,428 worldwide, placing it in the top 42% of all ranked servers.

Server details

How reliably does Operational Control Center stay online?

As recorded now, Operational Control Center is not reachable, the last contact having been 4 days 11 hours ago. Of the 120 hours in the last 5 full days, it was up for 6, or 5% of the time. Its earliest appearance in the records of Rust Server Trends dates to 23 October 2026.

Which region does Operational Control Center run from?

A region is not published by Operational Control Center. 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 84.174.76.43:28025.

What build of Rust does Operational Control Center use?

On Windows, Operational Control Center runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Operational Control Center?

On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.

How often does Operational Control Center wipe, and on which days?

On record so far are too few of Operational Control Center's wipes to tell its rhythm. 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 5 days 17 hours.

Server tags

What do the server tags on Operational Control Center mean?

These are the tags Operational Control Center publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp3 (Max players): Slots: 3; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 Operational Control Center appear?

The Rust Server Trends lists that take in Operational Control Center are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Connecting

What steps get you onto Operational Control Center?

You can connect by pressing F1 in Rust and typing client.connect 84.174.76.43:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla mode.
mp3
Max players Slots: 3.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.