RUST METRICSFlight deck · live data
Data live Servers11,694 Players35,972 Populated2,914 Fresh wipes 3 h94 Scan5 min
‹ All servers150.228.104.245:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 150.228.104.245:28015 checked 43d ago

moddedoxide
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 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#13,304no region published
Last wipe44d 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 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 timing

What wipe timing does TroubleChute follow?

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. The world in play was created 44 days 12 hours ago.

Tags

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; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game from TroubleChute. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TroubleChute?

Rust Metrics lists featuring TroubleChute: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does TroubleChute sit in the rankings?

Ranking for TroubleChute: #13,304 on seven-day player hours, top – of all ranked servers.

How full does TroubleChute get?

TroubleChute is not responding; status offline, last seen 43 days 14 hours ago.

Server details

Which location does TroubleChute run from?

No region comes from TroubleChute. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 150.228.104.245:28015.

What Rust version is TroubleChute on?

Rust network protocol 2633 and build 163794 on Windows is the build TroubleChute runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on TroubleChute, and is it online?

Check: connection. TroubleChute is offline at this moment. Last contact was 43 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 15 September 2026.

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. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is TroubleChute on?

Procedural map on TroubleChute, made by the game's generator.

How to join

How can you get onto TroubleChute?

To join: start Rust, press F1 and type client.connect 150.228.104.245: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 Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build The server runs game 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 It runs Oxide, also known as uMod.
^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.