Offline 79.223.239.140:28025 checked 4h ago
Operational Control Center
Connect
srv = rust.server("79.223.239.140: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 bestTop 41% 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 79.223.239.140:28025
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 11:57 UTC
- hostname
- –
- first seen
- 25 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 · 156 on average | 35/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 35/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Operational Control Center rank?
Rank #9,035 on seven-day player hours for Operational Control Center, within the top 41% of all ranked servers.
How full does Operational Control Center run?
Operational Control Center returns no live count at this refresh, having last been seen 4 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 18:00 UTC, averaging 1 players.
Server data
Which Rust version is Operational Control Center on?
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 4 hours ago. Uptime of 6% across the last 3 full days: 4 hours of 72. Its earliest recorded date in Rust Data is 25 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. You can reach it at 79.223.239.140:28025.
Settings and map
What rules and settings are recorded for Operational Control Center?
No gather rate appears in the name: Operational Control Center. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Wipe schedule
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. This world was created 5 days 12 hours ago.
Lists and tags
Where does Operational Control Center appear among Rust Data lists and filters?
The Rust Data lists that Operational Control Center fits are: 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.
How should you read the server tags on Operational Control Center?
The game's server browser reads these tags from Operational Control Center: gmvanilla (Game mode): The mode is vanilla survival; mp3 (Max players): Slot count: 3; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 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. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Operational Control Center?
The manual route: launch Rust, F1, then client.connect 79.223.239.140:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.