RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,212 Populated3,932 Fresh wipes 3 h403 Scan5 min
‹ All servers145.224.74.117:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 145.224.74.117:28015 checked 40d 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#15,456no region published
Last wipe40d 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 Sep22 Sep24 Sep25 Sep26 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

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 21:22 UTC40d 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 happens on LinuxGSM when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does LinuxGSM wipe, and when?

To tell the rhythm of LinuxGSM, too few of its wipes 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. The world it runs now was made 40 days 20 hours ago.

Tag meanings

How should you read the tags on LinuxGSM?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from LinuxGSM. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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.

Occupancy

Where does LinuxGSM sit in the rankings?

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

How full does LinuxGSM get?

Reading for LinuxGSM: offline at this moment; last seen 40 days 15 hours ago.

Server

Where does LinuxGSM sit?

Reading: location. LinuxGSM gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 145.224.74.117:28015.

What Rust version is LinuxGSM on?

Rust network protocol 2633 and build 164530 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?

Check: connection. LinuxGSM is offline at this moment. Last contact was 40 days 15 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 18 September 2026.

Settings and map

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

No gather rate appears in the name: LinuxGSM. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.

Which map is live on LinuxGSM?

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

Connection

How can you get onto LinuxGSM?

To join: start Rust, press F1 and type client.connect 145.224.74.117: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,cs164530,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Game build reading: 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.