RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h14 Scan5 min
‹ All servers109.149.83.136:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 109.149.83.136:28015 checked 44d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

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,021no region published
Last wipe44d 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 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+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
Mon 14 Sep, 12:41 UTC44d 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

Reset cycle

What should you expect from wipe day on LinuxGSM?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does LinuxGSM wipe, and when?

The rhythm of LinuxGSM's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 44 days 7 hours ago the current world was made.

Tags

Which tags does LinuxGSM carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): Build 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from LinuxGSM. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LinuxGSM appear in Rust Metrics lists and filters?

On Rust Metrics, LinuxGSM sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does LinuxGSM sit in the rankings?

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

What is the population on LinuxGSM?

LinuxGSM is not responding; status offline, last seen 44 days 5 hours ago.

Server details

Which location does LinuxGSM run from?

No region comes from LinuxGSM. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 109.149.83.136:28015.

What Rust version is LinuxGSM on?

Rust network protocol 2633 and build 162929 on Linux is the build LinuxGSM runs. To get in, your game needs the same protocol; Steam applies the update.

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

LinuxGSM reports offline. The last reading came 44 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

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

Check: gather rate. The name LinuxGSM does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.

What map is LinuxGSM on?

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

Join

How do you connect to LinuxGSM?

To join: start Rust, press F1 and type client.connect 109.149.83.136:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs162929,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build Build 162929.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.