Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
27/ 100
F
Lost ground: down 6,368 places this week. A strong wipe could turn it round.
A term to build on.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.6 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sun 20 SepSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 20 Sep, 09:41 UTC38d ago
1
–
running
1
Sat 19 Sep, 18:57 UTC39d ago
1
–
0.6 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by LinuxGSM. Rust Server Score takes the server's word for its location and does not trace the hardware. 31.183.195.129:28015 is the address to use.
Is LinuxGSM up, and how steady is its uptime?
You cannot join now: LinuxGSM is offline, last seen 38 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 17 September 2026.
What Rust version is LinuxGSM on?
You will find LinuxGSM on Rust network protocol 2633 and build 163794, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does LinuxGSM wipe its map?
LinuxGSM has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 38 days 16 hours have passed since this world was made.
What should you expect from wipe day on LinuxGSM?
Recent wipes have peaked at 1 players on average. 1 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does LinuxGSM hold in the rankings?
In the top – of all ranked servers, LinuxGSM sits at #14,053 for player hours over the last seven days.
How many players does LinuxGSM usually have?
LinuxGSM is offline at the moment; the last time it was seen was 38 days 16 hours ago.
Tags and filters
What do LinuxGSM's tags stand for?
The game's browser takes its cue from the tags LinuxGSM has set: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does LinuxGSM appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LinuxGSM: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What settings and rules apply on LinuxGSM?
The name of LinuxGSM gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on LinuxGSM?
LinuxGSM runs a procedural map, which the game generates.
Getting in
What is the way to join LinuxGSM?
Enter client.connect 31.183.195.129:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmvanilla,cs163794,ts8,^z,^y
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on.