Working its way up from the back of the class: #12,895 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
36/ 100
F
Slipped a little: down 3,634 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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 60% of all ranked servers, top 82% in EU. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h.
The 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
In Europe, according to its own listing, sits HzB_TestServer, with the EU tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 87.169.186.237:28015.
Is HzB_TestServer up, and how steady is its uptime?
At this moment, HzB_TestServer is offline; the last time it was seen was 13 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
On what Rust version does HzB_TestServer sit?
The server HzB_TestServer is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does HzB_TestServer wipe, and how often?
The next wipe on HzB_TestServer is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 14 days 9 hours. Its tags list a monthly wipe schedule.
Population
Where does HzB_TestServer sit among Rust servers?
In Europe, HzB_TestServer is #2,423, and overall it is #12,895 on player hours over the last seven days, in the top 60% of all ranked servers.
How many players does HzB_TestServer usually have?
The last sighting of HzB_TestServer was 13 days 16 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on HzB_TestServer?
The game's browser takes its cue from the tags HzB_TestServer has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^r (Roleplay): Roleplay is the focus here; ^k (Build server): Design and practise your bases here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): The server browser lists it under Europe. 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 HzB_TestServer?
These Rust Server Score lists count HzB_TestServer among them: European Rust servers, graded, Modded Rust servers, graded, Rust build and creative servers and Roleplay servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Roleplay ^r, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
Which rules does HzB_TestServer enforce, and what are its settings?
You will find no gather rate in the name of HzB_TestServer. With no change from the game default, groups take up to 8 players. It runs build & creative, no gathering, just sandbox building. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
HzB_TestServer runs which map?
HzB_TestServer runs a procedural map, which the game generates.
How to join
How do you get onto HzB_TestServer?
To connect, start Rust, press F1, and type client.connect 87.169.186.237:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^m,^r,^k,EU,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^r
RoleplayRoleplay is the focus here.
^k
Build serverDesign and practise your bases here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EU
EuropeThe server browser lists it under Europe.
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. Even marks across the subjects, from F to F.