RUST METRICSFlight deck · live data
Data live Servers11,736 Players50,841 Populated3,279 Fresh wipes 3 h115 Scan5 min
‹ All servers64.40.8.143:22015
Offline Full Queue Fresh wipe Wipe due No query

LinuxGSM

Offline 64.40.8.143:22015 checked 13d 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#12,906top 60%
Last wipe13d 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 Sep22 Sep15 Oct17 Oct19 Oct21 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 gap28.1 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 15 OctWed 16 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 15 Oct, 00:27 UTC13d ago 1 – running 0
Wed 16 Sep, 22:09 UTC42d ago 0 – 28.1 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 should you expect from wipe day on LinuxGSM?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

When does LinuxGSM wipe?

The rhythm of LinuxGSM's wipes cannot be told yet: too few 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 in play was created 13 days 23 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): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from LinuxGSM. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show LinuxGSM?

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; Last wipe: In the last 2 weeks.

Occupancy

Where does LinuxGSM sit in the rankings?

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

What is the population on LinuxGSM?

Status for LinuxGSM: offline. Last seen 13 days 23 hours ago.

Operator and location

Which location does LinuxGSM run from?

No region comes from LinuxGSM. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 64.40.8.143:22015.

What Rust version is LinuxGSM on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by LinuxGSM. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. LinuxGSM last answered 13 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for LinuxGSM. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on LinuxGSM?

Procedural map on LinuxGSM, made by the game's generator.

How to join

What do you do to join LinuxGSM?

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
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.