RUST METRICSFlight deck · live data
Data live Servers11,641 Players44,965 Populated3,093 Fresh wipes 3 h105 Scan5 min
‹ All servers161.13.116.81:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 161.13.116.81:28015 checked 36d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 12 16 PAX 0 /16

Players now

0% full 7-day avg
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 –
Rank#15,131top 66%
Last wipe36d 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
15k10k15k20k23 Sep24 Sep26 Sep27 Sep29 Sep30 Sep

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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 23 Sep, 05:12 UTC36d 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.

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 36 days 3 hours ago.

Lists and filters

How should you read the tags on TroubleChute?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp16 (Max players): 16 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2631 (Protocol): Your game must run protocol 2631 to get in; cs158021 (Build): The server runs game build 158021; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from TroubleChute. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show TroubleChute?

These Rust Metrics lists carry TroubleChute: Rust community servers: live readings. Check: filters. On the server list it appears under these: 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 #15,131, in the top 66% of all ranked servers.

What is the population on TroubleChute?

Status for TroubleChute: offline. Last seen 36 days 2 hours ago.

Server details

Which location does TroubleChute run from?

No region comes from TroubleChute. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 161.13.116.81:28015.

What Rust version is TroubleChute on?

Version check: Rust network protocol 2631 and build 158021 on Windows, run by TroubleChute. To get in, your game needs the same protocol; Steam applies the update.

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

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

Map and rules

How is TroubleChute configured, and what rules are in force?

Reading the name gives no gather rate for TroubleChute. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is TroubleChute on?

The game generates a procedural map for TroubleChute.

How to join

What do you do to join TroubleChute?

Press F1 in Rust and enter client.connect 161.13.116.81:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp16,ptrak,$r?,v2631,gmrust,cs158021,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp16
Max players 16 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2631
Protocol Your game must run protocol 2631 to get in.
cs158021
Build The server runs game build 158021.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.