RUST METRICSFlight deck · live data
Data live Servers11,591 Players34,139 Populated2,831 Fresh wipes 3 h62 Scan5 min
‹ All servers104.28.200.40:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 104.28.200.40:28015 checked 4d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak 1
Rank#13,790top 62%
Last wipe23d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep5 Oct9 Oct24 Oct28 Oct

Top 62% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 11:55 UTC23d ago 1 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on TroubleChute?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

What wipe timing does TroubleChute follow?

The rhythm of TroubleChute's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 15 hours ago.

Tags

How should you read the tags on TroubleChute?

Tags published by TroubleChute, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show TroubleChute?

These Rust Metrics lists carry TroubleChute: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does TroubleChute sit in the rankings?

Player hours over seven days put TroubleChute at #13,790, in the top 62% of all ranked servers.

What player count does TroubleChute carry?

Status for TroubleChute: offline. Last seen 4 days 5 hours ago. Check: players over seven days. Average 0, peak 1.

Server details

Where does TroubleChute sit?

No region comes from TroubleChute. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 104.28.200.40:28015.

What Rust version is TroubleChute on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by TroubleChute. Matching protocol is required to join. Let Steam update your game.

How reliable is TroubleChute, and is it online now?

Reading: offline. TroubleChute last answered 4 days 5 hours ago. Reading: 2% uptime over the last 7 full days. It was up 3 of 168 hours. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on TroubleChute?

Check: gather rate. The name TroubleChute does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is off. That is Valve's anti-cheat.

What map is TroubleChute on?

Check: map. Procedural, generated by the game, on TroubleChute.

How to join

How can you get onto TroubleChute?

To join: start Rust, press F1 and type client.connect 104.28.200.40:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.