Offline 162.239.254.221:28015 checked 6d ago
CrowdControlServer
Connect
srv = rust.server("162.239.254.221: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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 21h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:25 UTC FW27d ago | 0 | 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 162.239.254.221:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:25 UTC
- hostname
- –
- first seen
- 17 Sep 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 · 157 on average | 109/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 · 116 on average | 133/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 101/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 31/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Population
How does CrowdControlServer compare in the rankings?
Player hours over seven days put CrowdControlServer at #15,348, in the top 69% of the ranked set.
How many players does CrowdControlServer hold at once?
CrowdControlServer returns no live count at this refresh, having last been seen 6 days ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does CrowdControlServer run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by CrowdControlServer. Steam updates your game for you, but the protocol must match to join.
Is CrowdControlServer up, and what does its uptime show?
Offline now for CrowdControlServer, last seen 6 days ago. Uptime of 1% across the last 7 full days: 2 hours of 168. Rust Data logged it first on 17 September 2026.
In which location is CrowdControlServer hosted?
For CrowdControlServer, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 162.239.254.221:28015 is its address.
Settings and map
What rules and settings are recorded for CrowdControlServer?
You will not find a gather rate in the string CrowdControlServer. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has CrowdControlServer selected?
The game generates its map: procedural, on CrowdControlServer.
Wipe schedule
On what schedule does CrowdControlServer wipe?
The only wipe CrowdControlServer takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 27 days 1 hours ago.
What is wipe day on CrowdControlServer like?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold CrowdControlServer, and which filters?
The Rust Data lists that CrowdControlServer fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on CrowdControlServer?
Read by the game's server browser, the tags CrowdControlServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $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.
Join steps
How can I connect to CrowdControlServer?
The manual route: launch Rust, F1, then client.connect 162.239.254.221:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.