RUST METRICSFlight deck · live data
Data live Servers11,762 Players65,727 Populated3,483 Fresh wipes 3 h193 Scan5 min
‹ All servers150.228.105.124:28015
Offline Full Queue Fresh wipe Wipe due No query

TroubleChute

Offline 150.228.105.124: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#14,128no 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

How often does TroubleChute wipe, and when?

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

Lists and filters

How should you read the tags on TroubleChute?

These are the tags TroubleChute publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. 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?

On Rust Metrics, TroubleChute sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does TroubleChute hold among Rust servers?

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

What player count does TroubleChute carry?

Reading for TroubleChute: offline at this moment; last seen 43 days 22 hours ago.

Operator and location

Which location does TroubleChute run from?

Reading: location. TroubleChute gives no region. 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.105.124:28015.

What Rust version is TroubleChute on?

Rust network protocol 2633 and build 163794 on Windows is the build TroubleChute runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. TroubleChute last answered 43 days 22 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

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

No gather rate appears in the name: TroubleChute. 8 players per group, the default value. 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. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TroubleChute?

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

Connection

How do you connect to TroubleChute?

Check: join. Open Rust, press F1, then enter client.connect 150.228.105.124:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.