RUST METRICSFlight deck · live data
Data live Servers11,869 Players103,347 Populated3,962 Fresh wipes 3 h552 Scan5 min
‹ All servers145.224.73.57:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 145.224.73.57:28015 checked 34d ago

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#13,593top 60%
Last wipe35d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k23 Sep25 Sep26 Sep28 Sep29 Sep1 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 24 SepThu 24 SepWed 23 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 24 Sep, 17:11 UTC35d ago 1 – running 0
Thu 24 Sep, 09:43 UTC35d ago 1 – 0.3 days 1
Wed 23 Sep, 14:28 UTC36d ago 1 – 0.8 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

Wipe timing

What happens on LinuxGSM when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does LinuxGSM follow?

No next wipe can be predicted for LinuxGSM, which wipes at irregular times. 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 35 days 2 hours ago.

Lists and filters

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

Tags published by LinuxGSM, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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?

These Rust Metrics lists carry LinuxGSM: Rust community servers: live readings. Check: filters. On the server list it appears under these: 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?

Ranking for LinuxGSM: #13,593 on seven-day player hours, top 60% of all ranked servers.

What is the population on LinuxGSM?

Status for LinuxGSM: offline. Last seen 34 days 22 hours ago.

Server

Where does LinuxGSM sit?

No region comes from LinuxGSM. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 145.224.73.57:28015.

What Rust version is LinuxGSM on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by LinuxGSM. Check: protocol. To join, your game must match; Steam handles the update.

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

LinuxGSM reports offline. The last reading came 34 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 23 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. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

Which map is live on LinuxGSM?

The game generates a procedural map for LinuxGSM.

Join

What do you do to join LinuxGSM?

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
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.