Working its way up from the back of the class: #16,736 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
47/ 100
D
Slipped a little: down 1,150 places this week. Nothing a good wipe can't fix.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
GHC-Test Rust leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 57.130.78.114:30552.
Is GHC-Test Rust up, and how steady is its uptime?
At this moment, GHC-Test Rust is offline; the last time it was seen was 29 days ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 30 September 2026.
On what Rust version does GHC-Test Rust sit?
Rust network protocol 2633 and build 165217 on Linux is what GHC-Test Rust runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does GHC-Test Rust reset?
There are too few wipes on record for GHC-Test Rust to show a rhythm. 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 29 days 1 hours.
Player numbers
Where does GHC-Test Rust sit among Rust servers?
In the top 70% of all ranked servers, GHC-Test Rust sits at #16,736 for player hours over the last seven days.
What does the population on GHC-Test Rust look like?
The last sighting of GHC-Test Rust was 29 days ago, and it is offline right now.
Tags and filters
What do GHC-Test Rust's tags stand for?
The game's browser takes its cue from the tags GHC-Test Rust has set: gmrust (Game mode): Survival in the standard Rust style; mp24 (Max players): 24 slots are available; 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; cs165217 (Build): Build number: 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does GHC-Test Rust appear in the Rust Server Score lists and filters?
These Rust Server Score lists count GHC-Test Rust 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.
Server rules
How is GHC-Test Rust set up, and what rules does it keep?
Nothing in the name of GHC-Test Rust states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on GHC-Test Rust?
The game generates the procedural map on GHC-Test Rust at size 3,000 with seed 777001. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join GHC-Test Rust?
To connect, start Rust, press F1, and type client.connect 57.130.78.114:30552. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp24,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp24
Max players24 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
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).