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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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
ServerHub Test leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 171.217.41.32:28015.
How reliable is ServerHub Test, and is it up?
At this moment, ServerHub Test is offline; the last time it was seen was 44 days 2 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 14 September 2026, Rust Server Score saw it for the first time.
On what Rust version does ServerHub Test sit?
You will find ServerHub Test on Rust network protocol 2633 and build 163207, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does ServerHub Test wipe its map?
There are too few wipes on record for ServerHub Test to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 52 days 12 hours.
Population
Where does ServerHub Test sit among Rust servers?
In the top – of all ranked servers, ServerHub Test sits at #15,025 for player hours over the last seven days.
Is ServerHub Test a busy server?
It has been 44 days 2 hours since ServerHub Test was last seen, and it is offline right now.
Lists and filters
What do ServerHub Test's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163207 (Build): The game build is 163207; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags ServerHub Test publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show ServerHub Test?
Rust Server Score lists that include ServerHub Test: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
How is ServerHub Test set up, and what rules does it keep?
You will find no gather rate in the name of ServerHub Test. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on ServerHub Test?
The game generates a procedural map for ServerHub Test.
How to join
How do you get onto ServerHub Test?
To connect, start Rust, press F1, and type client.connect 171.217.41.32:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,gmrust,cs163207,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163207
BuildThe game build is 163207.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is 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.
Not enough figures yet to write a report. Check back after a few days on the list.