RUST METRICSFlight deck · live data
Data live Servers11,635 Players30,176 Populated2,756 Fresh wipes 3 h70 Scan5 min
‹ All servers86.182.194.131:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 86.182.194.131:28015 checked 27d ago

COM 1 · connect

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#16,508top 70%
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 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

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 gap1.7 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 20 SepFri 18 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, 13:20 UTC38d ago 1 – running 0
Fri 18 Sep, 21:25 UTC40d ago 1 – 1.7 days 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.

What wipe timing does LinuxGSM follow?

Its rhythm cannot be told from the wipes of LinuxGSM 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. 38 days 16 hours ago the current world was made.

Lists and filters

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

These are the tags LinuxGSM publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): Slots: 50; 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): The region field is empty. 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?

These Rust Metrics lists carry LinuxGSM: 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.

Player count

Where does LinuxGSM sit in the rankings?

Player hours over seven days put LinuxGSM at #16,508, in the top 70% of all ranked servers.

How full does LinuxGSM get?

LinuxGSM is not responding; status offline, last seen 27 days 15 hours ago.

Server details

Where does LinuxGSM sit?

No region comes from LinuxGSM. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 86.182.194.131: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.

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

LinuxGSM reports offline. The last reading came 27 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: LinuxGSM. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

What map is LinuxGSM on?

The game generates a procedural map for LinuxGSM.

Connection

What do you do to join LinuxGSM?

Check: join. Open Rust, press F1, then enter client.connect 86.182.194.131: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,cs162929,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players Slots: 50.
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 The region field is empty.

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.