Offline 37.73.53.33:28015 checked 30d ago
TroubleChute
Connect
srv = rust.server("37.73.53.33: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 68% 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
- 37.73.53.33:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Sep 2026, 17:13 UTC
- hostname
- –
- first seen
- 28 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 | 61/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 61/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 51/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/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 #16,290 on player hours, in the top 68% of ranked servers.
How full does TroubleChute run?
Offline now for TroubleChute, with the last sample 30 days 2 hours ago.
Server facts
What Rust version does TroubleChute run?
Rust network protocol 2633 and build 163207 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 30 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 28 September 2026.
In which location is TroubleChute hosted?
For TroubleChute, 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. 37.73.53.33: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. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has TroubleChute selected?
TroubleChute runs a procedural map, which the game generates.
Wipe schedule
When does TroubleChute wipe, and how often?
The record for TroubleChute holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 51 days 5 hours ago.
Tags, lists
Which lists on Rust Data hold TroubleChute, and which filters?
On Rust Data, TroubleChute appears in these lists: 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 TroubleChute?
The game's server browser reads these tags from TroubleChute: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163207 (Build): Build number: 163207; 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): 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 TroubleChute?
Enter client.connect 37.73.53.33:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.