A quiet classroom so far: 2 of 50 on average. Plenty of space to grow.
Standingrank on player hours
89/ 100
A−
Holds a respectable place: #2,480 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
68/ 100
C+
Slows down under load at times: 41 server fps on average.
Wipeskeeping the crowd after a wipe
67/ 100
C+
Keeps a fair share of its players through a wipe: 67% of wipes kept half their crowd.
Momentumrank now against a week ago
62/ 100
C
Moving up: up 577 places this week.
A fair term, with more to come.
Strongest in uptime (A+); population 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.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 11% of all ranked servers, top 32% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
···W···
······W
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 21h.
The force wipe · high confidence
usual gap14 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak7players, last three wipes
crowd held67%else halves by day 13
Coming wipes
8d 21hThu 5 Nov, 19:00 UTCFW
11d 14hSun 8 Nov, 11:54 UTC
25d 14hSun 22 Nov, 11:54 UTC
36d 21hThu 3 Dec, 19:00 UTCFW
39d 14hSun 6 Dec, 11:54 UTC
The first 48 hours of its last wipes
Sun 25 OctThu 15 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 8, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 11:54 UTC2d ago
8
–
running
4
Thu 15 Oct, 18:01 UTC12d ago
5
✓ held half
9.7 days
0
Thu 1 Oct, 18:19 UTCFW26d ago
8
halved by day 13
14 days
3
Thu 17 Sep, 18:04 UTC40d ago
4
✓ held half
14 days
1
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 what location does [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ sit?
The EU tag on [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ puts it in Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 65.21.78.175:28000.
How dependable is [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++, and is it online at the moment?
Right now, [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ is online. According to its reported uptime, the last restart was about 14 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ run?
It never fell below 4 server fps in the last 48 hours, averaging 41. Up to 137,069 entities were in the world, covering buildings, deployables and the rest. Up to 4,462 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ on?
You will find [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ reset?
Its tag sets the prediction, as the record holds too few of [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++'s wipes to confirm its schedule. 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 2 days 9 hours. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++?
Across its recent wipes, the busiest moments averaged 7 players. Peak numbers came 3 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 67% of its recent wipes. In the other wipes it slipped under half by day 13.
Population
Where does [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ place in the wider field of Rust servers?
In Europe, [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ is #949, and overall it is #2,480 on player hours over the last seven days, in the top 11% of all ranked servers.
Is [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ a busy server?
[EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ is showing 3 players right now, with 50 slots in total. The seven-day average is 2 players, with a peak of 8. The busiest time in the last 48 hours was 19:00 UTC, with an average of 6 players.
Lists and filters
How should you read the tags on [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++?
You'll see [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): In the server browser it appears under Europe in the browser, which picks them up from the server. 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 [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++?
These Rust Server Score lists count [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ among them: European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.
Map and rules
Which rules does [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ enforce, and what are its settings?
The name of [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ gives no gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++?
[EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++ runs a game-generated procedural map at size 4,750, seed 479873. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to [EU/NO]Galehuset PVE | BiWeekly | Raids | Events | ++?
Enter client.connect 65.21.78.175:28000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/6RTCTkHHKJ.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^b,EU,^p,gmrust,cs168909,ts8,^o^z,modded
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EU
EuropeIn the server browser it appears 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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).