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 1h.
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
The name of [GER] Hafensaenger points to Europe, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 37.138.225.115:28015 is the address to use.
How dependable is [GER] Hafensaenger, and is it online at the moment?
You cannot join now: [GER] Hafensaenger is offline, last seen 39 days 4 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 19 September 2026.
On what Rust version does [GER] Hafensaenger sit?
The server [GER] Hafensaenger is on Rust network protocol 2633 and build 164530 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does [GER] Hafensaenger wipe its map?
weekly: 7 days after its last wipe gives the basis for estimating [GER] Hafensaenger's next wipe. It is due to wipe next on Friday 30 October at 06:04 UTC. 54 days 22 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
Player count
Where does [GER] Hafensaenger place in the wider field of Rust servers?
Over the last seven days, [GER] Hafensaenger has #15,441 for player hours, in the top – of all ranked servers.
How many players does [GER] Hafensaenger usually have?
The last sighting of [GER] Hafensaenger was 39 days 4 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on [GER] Hafensaenger?
The game's browser takes its cue from the tags [GER] Hafensaenger has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): Its slot count is 20; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every 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. 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.
Where does [GER] Hafensaenger appear in the Rust Server Score lists and filters?
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. These filters bring it up 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.
Server rules
Which rules does [GER] Hafensaenger enforce, and what are its settings?
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. Under Community in the server browser you will find this community server. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [GER] Hafensaenger?
[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 37.138.225.115: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 modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersIts slot count is 20.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every 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.