A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
49/ 100
D
Working its way up from the back of the class: #11,456 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); uptime 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.
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
No rank history yet.
Top 51% of all ranked servers, top 80% 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 6d 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
You'll see HzB_TestServer listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 87.169.191.5:28015.
How dependable is HzB_TestServer, and is it online at the moment?
You cannot join now: HzB_TestServer is offline, last seen 1 hours ago. The first sighting by Rust Server Score was on 30 October 2026.
On what Rust version does HzB_TestServer sit?
Rust network protocol 2635 and build 168909 on Windows is what HzB_TestServer runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
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 15 days 10 hours. The tags show a monthly wipe schedule.
Population
Where does HzB_TestServer sit among Rust servers?
In Europe, HzB_TestServer is #2,334, and overall it is #11,456 on player hours over the last seven days, in the top 51% of all ranked servers.
How many players does HzB_TestServer usually have?
HzB_TestServer is offline at the moment; the last time it was seen was 1 hours ago. It peaked at 1 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 00:00 UTC, averaging 1 players.
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): 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; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^r (Roleplay): You play a role on this server; ^k (Build server): Bases can be designed and practised here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EU (Europe): The server browser lists it under Europe. 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 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.
Server rules
How is HzB_TestServer set up, and what rules does it keep?
The name of HzB_TestServer gives no gather rate. The group limit stays at the game's default of 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on HzB_TestServer?
The game generates a procedural map for HzB_TestServer.
Connecting
How do you get onto HzB_TestServer?
To connect, start Rust, press F1, and type client.connect 87.169.191.5:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,^m,^r,^k,EU,gmrust,cs168909,ts8,^o^z
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.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^r
RoleplayYou play a role on this server.
^k
Build serverBases can be designed and practised here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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. Strongest in standing (D); uptime is the one to work on (F).