Operational Control Center
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 14d ago · 84.174.68.96:28025
Abstract
We describe the public Rust server Operational Control Center, reached at 84.174.68.96:28025. It is offline at the last check, against a seven-day mean of 01. It ranks #14,970 of all servers, the top 68%. It last wiped 14d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 68% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: 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.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 1 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Fri 6 Nov, 23:5614d ago | 1 | – | running | 1 |
| Thu 5 Nov, 19:00fw15d ago | – | – | – | – |
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 84.174.68.96:28025 |
|---|---|
| Region | – |
| Max players | 3 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 6 Nov 2026, 23:56 UTC |
| Hostname | – |
| First seen | 5 Nov 2026 |
| Map | Custom Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and Rust wipe forecast [3].
| Server | Players |
|---|---|
| МИНИ-КАРТА 2Х | STORM | FPS+ 21.11EU · groups of 8+ · weekly · 128 on average | 126/100 |
| ShockRust | Blue | NoLimitno group limit · 110 on average | 290/400 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11EU · groups of 16+ · weekly · 98 on average | 189/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11EU · groups of 16+ · monthly · 79 on average | 80/700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11EU · groups of 16+ · monthly · 68 on average | 127/1000 |
| ShockRust | Green | MAX 4no group limit · 65 on average | 135/250 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1In which location is Operational Control Center based?
There is no region published for Operational Control Center. Rust Statistics does not look up the machine's location; it shows where the server says it is. 84.174.68.96:28025 is its address.
A.2How reliable is Operational Control Center, and is it currently online?
At the present moment, Operational Control Center is offline; it was last seen 14 days 14 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 5 November 2026.
A.3What is the Rust version for Operational Control Center?
Operational Control Center is running Rust network protocol 2636 and build 170460 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.
Wipe schedule
A.4On what cycle does Operational Control Center wipe?
There are not yet enough recorded wipes for Operational Control Center to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 3 December at 19:00 UTC. The current world has been running for 14 days 15 hours.
A.5How would you describe wipe day on Operational Control Center?
The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 1 hours after it began.
Player count
A.6What is the rank of Operational Control Center among Rust servers?
The seven-day player-hours ranking puts Operational Control Center at #14,970, within the top 68% of ranked servers.
A.7How would you characterise the player activity on Operational Control Center?
Operational Control Center is not online now; 14 days 14 hours have passed since it was last seen.
Tags and filters
A.8How should the tags on Operational Control Center be interpreted?
Tags from Operational Control Center, read by the game's server browser, are gmvanilla (Game mode): Survival on vanilla rules; mp3 (Max players): The slot count is 3; ts8 (Group limit): The team cap is 8, which is the game default; v2636 (Protocol): Joining requires the same game version: protocol 2636; cs170460 (Build): Build 170460 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can Operational Control Center be found among the Rust Statistics lists and filters?
The Rust Statistics lists that Operational Control Center fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Settings and map
A.10What are the settings and rules that govern Operational Control Center?
The name of Operational Control Center states no gather rate. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
How to join
A.11What is the process for joining Operational Control Center?
Enter client.connect 84.174.68.96:28025 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.
Appendix BServer tags
What each of the server's tags means. Published as mp3,ptrak,$r?,v2636,gmvanilla,cs170460,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmvanilla | Game mode. Survival on vanilla rules. |
mp3 | Max players. The slot count is 3. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2636 | Protocol. Joining requires the same game version: protocol 2636. |
cs170460 | Build. Build 170460 is the one running. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. The region code is unset. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^z | Modded. The game is altered by plugins or settings, so it is listed as 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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.