TroubleChute
Offline 150.228.105.125:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 486/525
- 401/450
- 52/250
- 44/250
- 48/100
- 161/200
Quick answers
from the figures on this pageWipe schedule
When does TroubleChute wipe?
The rhythm of TroubleChute's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 days 2 hours ago the current world was made.
Lists and filters
Which tags does TroubleChute carry, and what do they mean?
These are the tags TroubleChute publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TroubleChute appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TroubleChute: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does TroubleChute hold among Rust servers?
Ranking for TroubleChute: #13,349 on seven-day player hours, top – of all ranked servers.
What player count does TroubleChute carry?
Status for TroubleChute: offline. Last seen 43 days ago.
Operator and location
Which location does TroubleChute run from?
Reading: location. TroubleChute gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 150.228.105.125:28015.
What Rust version is TroubleChute on?
Rust network protocol 2633 and build 163794 on Windows is the build TroubleChute runs. Matching protocol is required to join. Let Steam update your game.
Is TroubleChute up, and how often does it stay up?
TroubleChute reports offline. The last reading came 43 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Settings and map
What settings and rules apply on TroubleChute?
No gather rate appears in the name: TroubleChute. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is TroubleChute on?
Procedural map on TroubleChute, made by the game's generator.
How to join
How do you connect to TroubleChute?
Check: join. Open Rust, press F1, then enter client.connect 150.228.105.125:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.