RUST METRICSFlight deck · live data
Data live Servers11,662 Players43,563 Populated3,033 Fresh wipes 3 h101 Scan5 min
‹ All servers104.28.232.40:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 104.28.232.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 0 /10

Players now

0% 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#14,583top 66%
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
15k10k15k20k4 Oct7 Oct10 Oct22 Oct25 Oct28 Oct

Top 66% 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

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 12:34 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?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does TroubleChute wipe, and when?

To tell the rhythm of TroubleChute, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 23 days 13 hours ago the current world was made.

Tags

How should you read the tags on TroubleChute?

Check: tags. The game's server browser reads 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): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from TroubleChute. 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.

Occupancy

What position does TroubleChute hold among Rust servers?

Player hours over seven days put TroubleChute at #14,583, in the top 66% of all ranked servers.

What is the population on TroubleChute?

Reading for TroubleChute: offline at this moment; last seen 4 days 2 hours ago. Check: players over seven days. Average 0, peak 1.

Server

What location is TroubleChute hosted in?

No region tag on TroubleChute. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 104.28.232.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.

Is TroubleChute up, and how often does it stay up?

TroubleChute reports offline. The last reading came 4 days 2 hours ago. Uptime for the last 7 full days: 4 of 168 hours, or 2%. The first sighting on Rust Metrics was 4 October 2026.

Map and rules

What rules does TroubleChute enforce, and what are its settings?

Reading the name gives no gather rate for TroubleChute. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is off. That is Valve's anti-cheat.

Which map is live on TroubleChute?

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

Connection

How can you get onto TroubleChute?

To join: start Rust, press F1 and type client.connect 104.28.232.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 Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.