RUST METRICSFlight deck · live data
Data live Servers11,826 Players82,123 Populated3,756 Fresh wipes 3 h273 Scan5 min
‹ All servers150.228.104.179:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 150.228.104.179:28015 checked 43d ago

moddedoxide
COM 1 · connect

Server instruments

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

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,498no region published
Last wipe43d agono schedule published
Next wipe–no wipe 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 Sep21 Sep22 Sep23 Sep
PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

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 schedule

When does TroubleChute wipe?

Its rhythm cannot be told from the wipes of TroubleChute on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 43 days 5 hours ago.

Lists and filters

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): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. 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: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does TroubleChute hold among Rust servers?

Player hours over seven days put TroubleChute at #15,498, in the top – of all ranked servers.

What is the population on TroubleChute?

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

Server details

Where does TroubleChute sit?

No region tag on TroubleChute. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 150.228.104.179:28015.

What Rust version is TroubleChute on?

Rust network protocol 2633 and build 163794 on Windows is the build TroubleChute runs. Check: protocol. To join, your game must match; Steam handles the update.

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

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

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: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TroubleChute?

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

Join

How do you connect to TroubleChute?

To join: start Rust, press F1 and type client.connect 150.228.104.179: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?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.