Offline 88.154.34.77:28015 checked 12d ago
TroubleChute
Connect
srv = rust.server("88.154.34.77: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 best
Top 65% 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
- 88.154.34.77:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 18:00 UTC
- hostname
- –
- first seen
- 15 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 | 134/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 155/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 73/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 36/1000 |
Quick answers
From the figures on this page.
Population
How does TroubleChute compare in the rankings?
Over the last seven days TroubleChute sits at #14,053 on player hours, in the top 65% of ranked servers.
How full does TroubleChute run?
Offline now for TroubleChute, with the last sample 12 days 12 hours ago.
Server data
Which Rust version is TroubleChute on?
Rust network protocol 2634 and build 167398 on Windows is what TroubleChute runs. Joining needs the same protocol on your game; Steam handles the update.
Is TroubleChute up, and what does its uptime show?
The latest sample has TroubleChute offline, with a last sighting 12 days 12 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 15 October 2026.
Where does TroubleChute sit?
For TroubleChute, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 88.154.34.77:28015 is its address.
Settings and map
What rules and settings are recorded for TroubleChute?
You will not find a gather rate in the string TroubleChute. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on TroubleChute?
TroubleChute runs a procedural map, which the game generates.
Wipe schedule
When does TroubleChute wipe, and how often?
A rhythm cannot be read from the wipes of TroubleChute on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 16 days 14 hours ago.
Tags and filters
Which lists on Rust Data hold TroubleChute, and which filters?
On Rust Data, TroubleChute 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.
How should you read the server tags on TroubleChute?
Read by the game's server browser, the tags TroubleChute publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
What is the way into TroubleChute?
In Rust, F1 opens the console: type client.connect 88.154.34.77:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.