Offline 85.172.88.36:28015 checked 18d ago
TroubleChute
Connect
srv = rust.server("85.172.88.36:28016")
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 72% 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
- 85.172.88.36:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 11:57 UTC
- hostname
- –
- first seen
- 9 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 | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 180/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 79/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 37/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TroubleChute rank?
Rank #15,841 on seven-day player hours for TroubleChute, within the top 72% of all ranked servers.
How many players does TroubleChute hold at once?
The current row shows TroubleChute offline; the last response was 18 days 20 hours ago.
Server facts
What is the Rust version on TroubleChute?
The build is Rust network protocol 2634 and build 167398 on Windows, run by TroubleChute. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TroubleChute, and is it up?
Offline now for TroubleChute, last seen 18 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 9 October 2026.
Which location does TroubleChute run from?
No region is published by TroubleChute. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 85.172.88.36:28015 is its address.
Settings and map
What rules and settings are recorded for TroubleChute?
No gather rate appears in the name: TroubleChute. 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. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TroubleChute loaded?
A procedural map runs on TroubleChute, generated by the game.
Wipe data
When does TroubleChute wipe, and how often?
A rhythm cannot be read from the wipes of TroubleChute on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 22 days 20 hours ago.
Lists and tags
Which Rust Data filters and lists contain TroubleChute?
The Rust Data lists that TroubleChute fits are: 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.
How should you read the server tags on TroubleChute?
These tags are published by TroubleChute and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is 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.
Join steps
What is the way to join TroubleChute?
The manual route: launch Rust, F1, then client.connect 85.172.88.36:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.