Working its way up from the back of the class: #15,493 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
41/ 100
F
Slipped a little: down 2,753 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.
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
Top 67% 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
Next wipe Friday 30 October, 06:04 UTC, in 2d 6h.
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. You can connect at 85.16.182.182:28015.
How reliable is [GER] Hafensaenger, and is it up?
At this moment, [GER] Hafensaenger is offline; the last time it was seen was 35 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 21 September 2026.
Which Rust version is [GER] Hafensaenger running?
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.
Resets
How frequently does [GER] Hafensaenger wipe its map?
The next wipe on [GER] Hafensaenger is a projection 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 53 days 17 hours. Its tags state that it wipes weekly.
Population
Where does [GER] Hafensaenger sit among Rust servers?
Over the last seven days, [GER] Hafensaenger has #15,493 for player hours, in the top 67% of all ranked servers.
What does the population on [GER] Hafensaenger look like?
[GER] Hafensaenger is offline at the moment; the last time it was seen was 35 days 23 hours ago.
Tags
How should you read the tags on [GER] Hafensaenger?
gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): 20 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^p (PvE): The danger comes from the world, not from other players are the tags [GER] Hafensaenger publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [GER] Hafensaenger appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [GER] Hafensaenger among them: European Rust servers, graded, Best community servers, graded, Rust PvE servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Rules and settings
How is [GER] Hafensaenger set up, and what rules does it keep?
Nothing in the name of [GER] Hafensaenger states a gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. Under Community in the server browser you will find this community server. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [GER] Hafensaenger uses?
[GER] Hafensaenger runs a procedural map, which the game generates.
Getting in
How should you connect to [GER] Hafensaenger?
To connect, start Rust, press F1, and type client.connect 85.16.182.182: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 modeRust survival, played by the standard rules.
mp20
Max players20 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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.