Offline 84.174.76.43:28015 checked 5d ago
Operational Control Center
Connect
srv = rust.server("84.174.76.43:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 57% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.174.76.43:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 09:10 UTC
- hostname
- –
- first seen
- 23 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 246 on average | 188/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 236 on average | 301/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 101 on average | 74/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 60 on average | 55/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 52 on average | 47/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 52 on average | 92/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Operational Control Center rank?
Player hours over seven days put Operational Control Center at #12,640, in the top 57% of the ranked set.
What population does Operational Control Center carry?
Operational Control Center returns no live count at this refresh, having last been seen 5 days 6 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What is the Rust version on Operational Control Center?
Rust network protocol 2635 and build 168909 on Windows is what Operational Control Center runs. Joining needs the same protocol on your game; Steam handles the update.
Is Operational Control Center up, and what does its uptime show?
Operational Control Center is offline at this refresh; the last response came 5 days 6 hours ago. Over the last 4 full days the hours up number 0 of 96, 0%. Its earliest recorded date in Rust Data is 23 October 2026.
Where does Operational Control Center sit?
For Operational Control Center, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 84.174.76.43:28015.
Map and rules
What rules and settings are recorded for Operational Control Center?
The name Operational Control Center carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as pve, player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Anti-cheat status: VAC on.
Which map has Operational Control Center selected?
Operational Control Center runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Operational Control Center wipe?
Too few wipes are on record for Operational Control Center to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 5 days 7 hours ago.
Tags, lists
Where does Operational Control Center appear among Rust Data lists and filters?
On Rust Data, Operational Control Center appears in these lists: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Operational Control Center?
Read by the game's server browser, the tags Operational Control Center publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^p (PvE): PvE: the world is the threat, not other players; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Operational Control Center?
In Rust, F1 opens the console: type client.connect 84.174.76.43:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.