A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,348 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
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
49/ 100
D
Slipped a little: down 175 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
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
Every five minutes, from the Steam server list.
AveragePeak
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 21hThu 5 Nov, 19:00 UTCFW
35d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 26 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 20:22 UTCFW27d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for LinuxGSM. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 64.118.241.64:28015.
How dependable is LinuxGSM, and is it online at the moment?
You can join now: LinuxGSM is online. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is LinuxGSM on?
Rust network protocol 2634 and build 167781 on Linux is what LinuxGSM runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does LinuxGSM wipe, and how often?
The force wipe each month is the only wipe LinuxGSM takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 27 days 1 hours have passed since this world was made.
What happens on LinuxGSM when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 26 hours into the latest wipe.
Player numbers
Where does LinuxGSM place in the wider field of Rust servers?
In the top 69% of all ranked servers, LinuxGSM sits at #15,348 for player hours over the last seven days.
How many players does LinuxGSM usually have?
Right now, 0 players are on LinuxGSM, which has 50 slots. A seven-day average of 0 players applies here.
Tags and filters
What do LinuxGSM's tags stand for?
gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags LinuxGSM publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show LinuxGSM?
These Rust Server Score lists count LinuxGSM among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is LinuxGSM set up, and what rules does it keep?
Nothing in the name of LinuxGSM states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map LinuxGSM uses?
The game generates a procedural map for LinuxGSM.
How to join
How should you connect to LinuxGSM?
Enter client.connect 64.118.241.64: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?,v2634,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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. Strongest in uptime (A+); population is the one to work on (F).