Working its way up from the back of the class: #15,863 on player hours.
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
50/ 100
D
Holding steady: up 95 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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.
No daily history yet.
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Which region is LinuxGSM rebuilt parity test based in?
You'll find no region listed by LinuxGSM rebuilt parity test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 14.1.89.24:28125.
How reliable is LinuxGSM rebuilt parity test, and is it up?
You cannot join now: LinuxGSM rebuilt parity test is offline, last seen 18 days 4 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 9 October 2026.
On what Rust version does LinuxGSM rebuilt parity test sit?
Rust network protocol 2634 and build 167231 on Linux is what LinuxGSM rebuilt parity test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does LinuxGSM rebuilt parity test reset?
LinuxGSM rebuilt parity test has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 18 days 9 hours.
Population
What position does LinuxGSM rebuilt parity test hold in the rankings?
Over the last seven days, LinuxGSM rebuilt parity test has #15,863 for player hours, in the top 72% of all ranked servers.
Is LinuxGSM rebuilt parity test a busy server?
The last sighting of LinuxGSM rebuilt parity test was 18 days 4 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on LinuxGSM rebuilt parity test?
You'll see LinuxGSM rebuilt parity test tagged with gmvanilla (Game mode): You play vanilla survival here; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): This runs on build 167231; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. 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.
Where does LinuxGSM rebuilt parity test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LinuxGSM rebuilt parity test: 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.
Rules and settings
Which rules does LinuxGSM rebuilt parity test enforce, and what are its settings?
You will find no gather rate in the name of LinuxGSM rebuilt parity test. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map LinuxGSM rebuilt parity test uses?
A procedural map, generated by the game, is what LinuxGSM rebuilt parity test runs.
Getting in
How should you connect to LinuxGSM rebuilt parity test?
Enter client.connect 14.1.89.24:28125 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 asmp1,ptrak,$r?,v2634,gmvanilla,cs167231,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildThis runs on build 167231.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 momentum (D); standing is the one to work on (F).