Offline 103.174.225.210:28015 checked 2d ago
TroubleChute
Connect
srv = rust.server("103.174.225.210: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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 21 Sep, 21:45 UTC37d ago | 1 | 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
- 103.174.225.210:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Sep 2026, 22:19 UTC
- hostname
- –
- first seen
- 21 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 · 156 on average | 4/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 38/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/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 #15,349 on player hours, in the top 69% of ranked servers.
How many players does TroubleChute hold at once?
TroubleChute returns no live count at this refresh, having last been seen 2 days 3 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does TroubleChute run?
Rust network protocol 2633 and build 162616 on Windows is what TroubleChute runs. The protocol has to match before you can join, and Steam does the updating.
Is TroubleChute up, and what does its uptime show?
The latest sample has TroubleChute offline, with a last sighting 2 days 3 hours ago. Over the last 7 full days the hours up number 1 of 168, 1%. The first row Rust Data holds for it is dated 21 September 2026.
Which location does TroubleChute run from?
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. You can reach it at 103.174.225.210:28015.
Map and rules
What rules and settings are recorded for TroubleChute?
The name TroubleChute carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has TroubleChute loaded?
The game generates its map: procedural, on TroubleChute.
Wipes and dates
On what schedule does TroubleChute wipe?
A rhythm cannot be read from the wipes of TroubleChute on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 37 days 2 hours ago.
On TroubleChute, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 2 hours in.
Lists and tags
Which Rust Data filters and lists contain TroubleChute?
The Rust Data lists that TroubleChute fits are: 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.
Which meanings do the tags on TroubleChute hold?
These tags are published by TroubleChute and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs162616 (Build): The server runs build 162616; 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. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join TroubleChute?
The manual route: launch Rust, F1, then client.connect 103.174.225.210:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.