Offline 85.190.158.224:10500 checked 7d ago
Chaos_Clan
Connect
srv = rust.server("85.190.158.224:10501")
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, measured since 1 Oct. 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 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 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 8h | 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, 18:33 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
3500 · seed 6738
- map
- Procedural Map
- size
- 3500
- seed
- 6738
Server
srv.info()- address
- 85.190.158.224:10500
- region
- –
- max players
- 80
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:33 UTC
- hostname
- –
- first seen
- 1 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 · 149 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 75/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 16/1000 |
Quick answers
From the figures on this page.
Population data
How does Chaos_Clan compare in the rankings?
Over the last seven days Chaos_Clan sits at #15,335 on player hours, in the top 69% of ranked servers.
What population does Chaos_Clan carry?
The current row shows Chaos_Clan offline; the last response was 7 days ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does Chaos_Clan run?
Rust network protocol 2634 and build 167781 on Windows is what Chaos_Clan runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Chaos_Clan, and is it up?
Chaos_Clan is offline at this refresh; the last response came 7 days ago. Over the last 7 full days the hours up number 10 of 168, 6%. Rust Data logged it first on 1 October 2026.
Where does Chaos_Clan sit?
For Chaos_Clan, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 85.190.158.224:10500.
Settings and map
Which settings and rules does Chaos_Clan run?
You will not find a gather rate in the string Chaos_Clan. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Chaos_Clan?
The game generates the map on Chaos_Clan: procedural, size 3,500, seed 6738. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does Chaos_Clan wipe?
A single wipe each month, the force wipe, is all Chaos_Clan does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 15 hours ago, and that is the one in play.
On Chaos_Clan, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain Chaos_Clan?
On Rust Data, Chaos_Clan appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Chaos_Clan hold?
These tags are published by Chaos_Clan and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp80 (Max players): Slot count: 80; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Chaos_Clan?
Enter client.connect 85.190.158.224:10500 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
