Station XX-14970 · no signal
Operational Control Center
Offline 84.174.68.96:28025 checked 14d ago
- Players now
- 0/ 3
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,970
- top 68%
- Last wipe
- 14d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 3 slots
- Motion · 24 h
- M –not enough readings
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. 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
too few wipes seen yetNot 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
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 6 Nov, 23:56 UTC14d ago | M0.0■steady | 1 | – | – | running | 1 |
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | – | – |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which settings and rules apply on Operational Control Center?
The name of Operational Control Center gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. 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 14 days 12 hours ago.
How does Operational Control Center rank against other Rust servers?
Over the last seven days, Operational Control Center recorded enough player hours to reach #14,970 worldwide, placing it in the top 68% of all ranked servers.
Server details
How reliably does Operational Control Center stay online?
Operational Control Center is down at the moment; the last recorded contact was 14 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 5 November 2026 is when Rust Server Trends first recorded it.
Where in the world is Operational Control Center hosted?
No region is published by Operational Control Center. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 84.174.68.96:28025.
Which Rust version is Operational Control Center running?
Rust network protocol 2636 and build 170460 on Windows is what Operational Control Center runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Operational Control Center?
1 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak.
On what timetable does Operational Control Center run its wipes?
Too few wipes of Operational Control Center are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 3 December at 19:00 UTC. 14 days 13 hours is how long the current world has been running.
Tags
What do the server tags on Operational Control Center mean?
The game's server browser reads the tags Operational Control Center publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp3 (Max players): The server has 3 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): Game protocol 2636: to join, your game must match this version; cs170460 (Build): Game build: 170460; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown 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. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to Operational Control Center?
Enter client.connect 84.174.68.96:28025 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.