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,349 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 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
80/ 100
B+
Holds its players well after a wipe: 80% of wipes kept half their crowd.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 4,543 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
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W··W
···F··W
·······
W··W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 gap3.6 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held80%else halves by day 2
The first 48 hours of its last wipes
Thu 15 OctMon 12 OctSun 4 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 7 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 19:08 UTC13d ago
1
–
running
0
Mon 12 Oct, 03:33 UTC17d ago
1
halved by day 2
3.6 days
0
Sun 4 Oct, 06:28 UTC24d ago
1
✓ held half
7.9 days
0
Thu 1 Oct, 18:21 UTCFW27d ago
1
✓ held half
2.5 days
0
Sun 27 Sep, 05:14 UTC31d ago
1
✓ held half
4.5 days
0
Thu 24 Sep, 05:18 UTC34d ago
1
✓ held half
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.
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 reports the location a server gives; it does not check where the machine actually is. You can connect at 198.44.49.134:28015.
How reliable is LinuxGSM, and is it up?
The server is up: LinuxGSM is online now. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does LinuxGSM sit?
The server LinuxGSM is on Rust network protocol 2634 and build 167781 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does LinuxGSM wipe its map?
There is no next wipe to predict on LinuxGSM, as it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 13 days 9 hours.
What should you expect from wipe day on LinuxGSM?
Recent wipes have peaked at 1 players on average. Peak numbers came 7 hours into the latest wipe. Half the peak held until the next wipe in 80% of its recent wipes. Day 2 is when it sank below half in the wipes that did not hold.
Player numbers
Where does LinuxGSM sit among Rust servers?
Over the last seven days, LinuxGSM has #15,349 for player hours, in the top 69% of all ranked servers.
How many players does LinuxGSM usually have?
With 50 slots available, LinuxGSM currently has 0 players. Over the past seven days, the average player count was 0.
Tags and filters
What is meant by the tags on LinuxGSM?
gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; 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): Build number: 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. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show LinuxGSM?
Rust Server Score lists that include LinuxGSM: Best community servers, graded. 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; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on LinuxGSM?
The name of LinuxGSM gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map LinuxGSM uses?
The game generates a procedural map for LinuxGSM.
Connecting
How should you connect to LinuxGSM?
To connect, start Rust, press F1, and type client.connect 198.44.49.134:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max players50 slots are available.
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
BuildBuild number: 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).