RUST METRICSFlight deck · live data
Data live Servers11,657 Players32,896 Populated2,828 Fresh wipes 3 h79 Scan5 min
‹ All servers31.183.195.129:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 31.183.195.129:28015 checked 38d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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,053no region published
Last wipe38d 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
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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.

usual gap0.6 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 20 SepSat 19 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 09:41 UTC38d ago 1 – running 1
Sat 19 Sep, 18:57 UTC39d ago 1 – 0.6 days 1

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

Reset cycle

What happens on LinuxGSM when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

How often does LinuxGSM wipe, and when?

The rhythm of LinuxGSM'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. 38 days 18 hours ago the current world was made.

Tags

How should you read the tags on LinuxGSM?

These are the tags LinuxGSM publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): 50 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): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LinuxGSM appear in Rust Metrics lists and filters?

On Rust Metrics, LinuxGSM sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

What position does LinuxGSM hold among Rust servers?

Ranking for LinuxGSM: #14,053 on seven-day player hours, top – of all ranked servers.

What is the population on LinuxGSM?

Status for LinuxGSM: offline. Last seen 38 days 17 hours ago.

Server

Which location does LinuxGSM run from?

Reading: location. LinuxGSM gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 31.183.195.129:28015.

What Rust version is LinuxGSM on?

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

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

LinuxGSM reports offline. The last reading came 38 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.

Map and rules

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

Reading the name gives no gather rate for LinuxGSM. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is LinuxGSM on?

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

Join

What do you do to join LinuxGSM?

Check: join. Open Rust, press F1, then enter client.connect 31.183.195.129:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs163794,ts8,^z,^y

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp50
Max players 50 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 The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.