Offline 84.174.76.43:28025 checked 3d ago
Operational Control Center
Connect
srv = rust.server("84.174.76.43:28027")
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 best
Top 43% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 11:00 UTC4d ago | 1 | NaN | running | 0 |
# 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.174.76.43:28025
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 11:57 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 | ShockRust | Blue | NoLimit | no group limit · 164 on average | 99/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 105/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 30/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 91/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 29/1000 |
Quick answers
From the figures on this page.
Population data
How does Operational Control Center compare in the rankings?
Player hours over seven days put Operational Control Center at #9,446, in the top 43% of the ranked set.
How full does Operational Control Center run?
The current row shows Operational Control Center offline; the last response was 3 days 4 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What is the Rust version on Operational Control Center?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Operational Control Center. Steam updates your game for you, but the protocol must match to join.
How reliable is Operational Control Center, and is it up?
The latest sample has Operational Control Center offline, with a last sighting 3 days 4 hours ago. 6 of 72 hours up over the last 3 full days, or 8%. The first row Rust Data holds for it is dated 23 October 2026.
Which location does Operational Control Center run from?
There is no region published for Operational Control Center. Rust Data does not look up where the machine stands; it shows where a server says it is. 84.174.76.43:28025 is its address.
Map and rules
Which rules apply on Operational Control Center, and what settings?
You will not find a gather rate in the string Operational Control Center. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Wipes and dates
When does Operational Control Center wipe, and on what schedule?
Too few wipes are on record for Operational Control Center to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 4 days 10 hours ago, and that is the one in play.
What is wipe day on Operational Control Center like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
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. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Operational Control Center hold?
The game's server browser reads these tags from Operational Control Center: gmvanilla (Game mode): Survival in vanilla form; mp3 (Max players): 3 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Operational Control Center?
Enter client.connect 84.174.76.43:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.