No signal: too few hourly readings to draw a record yet.
Now
40of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated
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.
AveragePeakWipe
Daily average and peak, UTC.
Channel 2 · instrument health
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.
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Channel 3 · rank movement
Rank
daily · 1 is best
RankRank in region
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Expected events
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap
1.1 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
70players, last three wipes
crowd held
100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctWed 14 Oct
Players each hour, from the hour of the wipe. The latest peaked at 70, 2 hours in.
Event catalogue
Wipes
newest first
Wiped
M
Peak
First 48 h
Crowd
Lasted
Players before
Fri 16 Oct, 20:06 UTC13d ago
M1.4▲rising
70
–
running
47
Thu 15 Oct, 03:09 UTC14d ago
M0.0■steady
70
–
1.7 days
70
Wed 14 Oct, 14:39 UTC15d ago
M1.3▲rising
70
–
0.5 days
52
Sun 11 Oct, 15:26 UTC18d ago
M1.0▲rising
70
held half
3 days
59
Sat 10 Oct, 07:20 UTC19d ago
M1.1▲rising
70
–
1.3 days
57
Fri 9 Oct, 17:44 UTC20d ago
M1.3▲rising
70
–
0.6 days
50
Fri 9 Oct, 03:28 UTC20d ago
M1.0▲rising
70
–
0.6 days
61
Wed 7 Oct, 14:50 UTC22d ago
M1.4▲rising
70
–
1.5 days
44
Tue 6 Oct, 19:25 UTC23d ago
M0.0▲rising
70
–
0.8 days
69
Mon 5 Oct, 22:24 UTC24d ago
M1.4▲rising
70
–
0.9 days
45
Sun 4 Oct, 15:44 UTC25d ago
M1.2▲rising
70
–
1.3 days
54
Sat 3 Oct, 13:49 UTC26d ago
M0.8▲rising
70
–
1.1 days
63
Sat 3 Oct, 07:38 UTC26d ago
M1.3▲rising
70
–
0.3 days
49
Fri 2 Oct, 13:04 UTC27d ago
M1.3▲rising
70
–
0.8 days
48
Thu 1 Oct, 12:12 UTC28d ago
M1.0▲rising
70
–
1 days
61
Thu 1 Oct, 05:38 UTC28d ago
M1.4▲rising
70
–
0.3 days
46
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Nearby stations
Similar servers
the same kind of game, then region, group limit, rate and wipes
Which map is running on Rusty Moose |EU Biweekly|?
Rusty Moose |EU Biweekly| runs a procedural map of size 4,500 with seed 771306, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Rusty Moose |EU Biweekly|?
No gather rate appears in the name of Rusty Moose |EU Biweekly|. No group limit is published. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Rusty Moose |EU Biweekly| right now?
Rusty Moose |EU Biweekly| is not responding at this moment and is offline, last seen 11 days 11 hours ago.
How does Rusty Moose |EU Biweekly| rank against other Rust servers?
On player hours for the past week, Rusty Moose |EU Biweekly| sits at #4,846, which puts it inside the top 22% of every ranked server.
Operator and location
How reliably does Rusty Moose |EU Biweekly| stay online?
Rusty Moose |EU Biweekly| is down at the moment; the last recorded contact was 11 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 1 October 2026 is when Rust Server Trends first recorded it.
Where in the world is Rusty Moose |EU Biweekly| hosted?
Its name points to Europe, but Rusty Moose |EU Biweekly| publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 4.182.234.116:27034.
What build of Rust does Rusty Moose |EU Biweekly| use?
Rusty Moose |EU Biweekly| is running Rust network protocol 2634 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Rusty Moose |EU Biweekly|?
The recent wipes averaged a busiest count of 70 players. 2 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does Rusty Moose |EU Biweekly| wipe, and on which days?
There is no next wipe to predict at Rusty Moose |EU Biweekly|, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 13 days 4 hours.
Lists and tags
What do the server tags on Rusty Moose |EU Biweekly| mean?
These are the tags Rusty Moose |EU Biweekly| publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; v2634 (Protocol): Your game needs to be on protocol 2634 to join; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; vanilla (Vanilla): Rates, kits and rules are as Facepunch ships them; everytwoweeks (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; official (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; hbff4ad10 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; stok (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Rusty Moose |EU Biweekly| appear?
The Rust Server Trends lists that take in Rusty Moose |EU Biweekly| are: EU Rust servers and Rust community servers without the side modes. These filters bring it up on the server list: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks; Players now: At least 10.
Connecting
What steps get you onto Rusty Moose |EU Biweekly|?
Enter client.connect 4.182.234.116:27034 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://moose.gg.
Instrument codes
Server tags
what each one means
Published asmp100,ptrak,v2634,everytwoweeks,official,vanilla,hbff4ad10,stok,gmrust
Game
gmrust
Game modeThe game mode is standard Rust survival.
mp100
Max players100 slots are available.
v2634
ProtocolYour game needs to be on protocol 2634 to join.
ptrak
NetworkingRakNet is the standard network layer for the game, and it's used here.
Difficulty
vanilla
VanillaRates, kits and rules are as Facepunch ships them.
Other
everytwoweeks
Custom tagA custom tag, not standard Rust: set by the owner or a plugin.
official
Custom tagA custom tag, not standard Rust: set by the owner or a plugin.
hbff4ad10
Custom tagA custom tag, not standard Rust: set by the owner or a plugin.
stok
Custom tagA custom tag, not standard Rust: set by the owner or a plugin.
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.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.
