RUST METRICSFlight deck · live data
Data live Servers11,773 Players67,310 Populated3,523 Fresh wipes 3 h192 Scan5 min
‹ All servers145.224.75.219:28015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 145.224.75.219:28015 checked 26d ago

COM 1 · connect
Launch Rust and join

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,832top 61%
Last wipe27d 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 61% 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.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 OctThu 1 Oct
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 2 Oct, 09:16 UTC27d ago 1 – running 1
Fri 2 Oct, 01:04 UTC27d ago 1 – 0.3 days 0
Thu 1 Oct, 18:12 UTC FW27d ago 1 – 0.3 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

Wipe schedule

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?

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 in play was created 27 days 2 hours ago.

Tags

How should you read the tags on LinuxGSM?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Game build reading: 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from LinuxGSM. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show LinuxGSM?

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?

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

What player count does LinuxGSM carry?

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

Server

What location is LinuxGSM hosted in?

Reading: location. LinuxGSM gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 145.224.75.219:28015.

What Rust version is LinuxGSM on?

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

How reliable is LinuxGSM, and is it online now?

Reading: offline. LinuxGSM last answered 26 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on LinuxGSM?

Check: gather rate. The name LinuxGSM does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on LinuxGSM?

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

Join

How can you get onto LinuxGSM?

To join: start Rust, press F1 and type client.connect 145.224.75.219: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?,v2634,gmvanilla,cs166586,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Game build reading: 166586.
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.