RUST METRICSFlight deck · live data
Data live Servers11,649 Players43,286 Populated3,030 Fresh wipes 3 h94 Scan5 min
‹ All servers145.224.72.143:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 145.224.72.143:28015 checked 29d 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#14,450top 60%
Last wipe31d 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
15k10k15k20k25 Sep27 Sep29 Sep2 Oct4 Oct6 Oct

Top 60% 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 gap0.8 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 27 SepSat 26 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
Sun 27 Sep, 10:37 UTC31d ago 1 – running 1
Sat 26 Sep, 15:07 UTC32d 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 schedule

What should you expect from wipe day on LinuxGSM?

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?

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. The world it runs now was made 31 days 17 hours ago.

Tags

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): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from LinuxGSM. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show LinuxGSM?

On Rust Metrics, LinuxGSM sits in these lists: 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.

Population

What position does LinuxGSM hold among Rust servers?

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

What player count does LinuxGSM carry?

Reading for LinuxGSM: offline at this moment; last seen 29 days 9 hours ago.

Server details

Where does LinuxGSM sit?

No region tag on LinuxGSM. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 145.224.72.143:28015.

What Rust version is LinuxGSM on?

Reading: LinuxGSM, Rust network protocol 2633 and build 165217, Linux. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. LinuxGSM last answered 29 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Settings and map

What settings and rules apply on LinuxGSM?

Reading the name gives no gather rate for LinuxGSM. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

What map is LinuxGSM on?

The game generates a procedural map for LinuxGSM.

Join

How can you get onto LinuxGSM?

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.