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.
AveragePeak
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
Next wipe Friday 30 October, 06:04 UTC, in 1d 10h.
Weekly: 7 days after its last 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 won't find a region tag on [GER] Hafensaenger, but its name indicates Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 85.16.185.7:28015.
Is [GER] Hafensaenger up, and how steady is its uptime?
You cannot join now: [GER] Hafensaenger is offline, last seen 39 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 18 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [GER] Hafensaenger sit?
The server [GER] Hafensaenger is on Rust network protocol 2633 and build 164530 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does [GER] Hafensaenger wipe, and how often?
The estimate for [GER] Hafensaenger's next wipe comes from weekly: 7 days after its last wipe. Expect the next wipe on Friday 30 October at 06:04 UTC. The world it runs now was created 54 days 13 hours. Its tags state that it wipes weekly.
Player numbers
Where does [GER] Hafensaenger place in the wider field of Rust servers?
In the top – of all ranked servers, [GER] Hafensaenger sits at #15,458 for player hours over the last seven days.
What does the population on [GER] Hafensaenger look like?
It has been 39 days 18 hours since [GER] Hafensaenger was last seen, and it is offline right now.
Lists and filters
What do [GER] Hafensaenger's tags stand for?
You'll see [GER] Hafensaenger tagged with gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): Its slot count is 20; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^p (PvE): Players do not fight one another here; the world is the danger in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature [GER] Hafensaenger?
Rust Server Score lists that include [GER] Hafensaenger: European Rust servers, graded, Best community servers, graded, Rust PvE servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Weekly ^w, Vanilla ^v and PvE ^p; Group limit: 5 or more; Wipe schedule: Weekly.
Map and rules
How is [GER] Hafensaenger set up, and what rules does it keep?
The name of [GER] Hafensaenger gives no gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. VAC, Valve's anti-cheat, is enabled.
[GER] Hafensaenger runs which map?
[GER] Hafensaenger runs a procedural map, which the game generates.
Connecting
How should you connect to [GER] Hafensaenger?
To connect, start Rust, press F1, and type client.connect 85.16.185.7:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,^p,^w,^v,gmrust,cs164530,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersIts slot count is 20.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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.