Fig. 1Players on Rusty Moose |EU Biweekly|RG-S4846-01 · Sheet 1 of 11
Fig. 2
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.
Fig. 2FPS, entities and memoryRG-S4846-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S4846-03 · Sheet 3 of 11
Schedule
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 gap1.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak70players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctWed 14 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 70, 2 hours in.
ScheduleExpected wipesRG-S4846-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 20:06 UTC12d ago
70
–
running
47
Thu 15 Oct, 03:09 UTC14d ago
70
–
1.7 days
70
Wed 14 Oct, 14:39 UTC14d ago
70
–
0.5 days
52
Sun 11 Oct, 15:26 UTC17d ago
70
held half
3 days
59
Sat 10 Oct, 07:20 UTC19d ago
70
–
1.3 days
57
Fri 9 Oct, 17:44 UTC19d ago
70
–
0.6 days
50
Fri 9 Oct, 03:28 UTC20d ago
70
–
0.6 days
61
Wed 7 Oct, 14:50 UTC21d ago
70
–
1.5 days
44
Tue 6 Oct, 19:25 UTC22d ago
70
–
0.8 days
69
Mon 5 Oct, 22:24 UTC23d ago
70
–
0.9 days
45
Sun 4 Oct, 15:44 UTC24d ago
70
–
1.3 days
54
Sat 3 Oct, 13:49 UTC25d ago
70
–
1.1 days
63
Sat 3 Oct, 07:38 UTC26d ago
70
–
0.3 days
49
Fri 2 Oct, 13:04 UTC26d ago
70
–
0.8 days
48
Thu 1 Oct, 12:12 UTC27d ago
70
–
1 days
61
Thu 1 Oct, 05:38 UTC28d ago
70
–
0.3 days
46
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.
Table 1Wipe logRG-S4846-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for Rusty Moose |EU Biweekly|, and is it up?
Last seen 10 days 23 hours ago; right now Rusty Moose |EU Biweekly| is offline. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 1 October 2026.
2.
In which location is Rusty Moose |EU Biweekly| hosted?
Europe is where the name of Rusty Moose |EU Biweekly| points, with no region tag published. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 4.182.234.116:27034.
3.
What Rust version is recorded for Rusty Moose |EU Biweekly|?
On Linux, Rusty Moose |EU Biweekly| runs Rust network protocol 2634. The same protocol is required for joining, and Steam updates your game to it.
Counts
4.
What does the population history show for Rusty Moose |EU Biweekly|?
Rusty Moose |EU Biweekly| is not responding at the latest refresh; the last record of it online is 10 days 23 hours ago.
5.
Against other Rust servers, where is Rusty Moose |EU Biweekly| placed?
Player hours over seven days place Rusty Moose |EU Biweekly| at #4,846, within the top 22% of ranked servers.
Wipe times
6.
What happens on Rusty Moose |EU Biweekly| on the day of a wipe?
An average of 70 players was recorded at the busiest point of its recent wipes. At 2 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.
7.
On Rusty Moose |EU Biweekly|, when do wipes occur?
There is no next wipe to predict at Rusty Moose |EU Biweekly|, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 12 days 15 hours ago the current world was made.
Settings
8.
Which rules and settings are recorded for Rusty Moose |EU Biweekly|?
The name of Rusty Moose |EU Biweekly| records no gather rate. The group limit is not published. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. It appears under Community in the server browser. Anti-cheat: VAC, from Valve, is on.
9.
Which map has Rusty Moose |EU Biweekly| loaded?
Rusty Moose |EU Biweekly| runs a procedural map of size 4,500 with seed 771306, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
10.
Where does Rusty Moose |EU Biweekly| appear among the Rust Graphs lists and filters?
These Rust Graphs lists include Rusty Moose |EU Biweekly|: Europe servers, plotted and Rust community servers, plotted. These filters on the server list return it: 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.
11.
On Rusty Moose |EU Biweekly|, what is meant by each tag?
gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): The slot count is 100; v2634 (Protocol): To join, your game must be on protocol 2634; ptrak (Networking): The network layer is RakNet, the game's standard; vanilla (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; everytwoweeks (Custom tag): The owner or a plugin set this tag; it is not standard Rust; official (Custom tag): The owner or a plugin set this tag; it is not standard Rust; hbff4ad10 (Custom tag): The owner or a plugin set this tag; it is not standard Rust; stok (Custom tag): The owner or a plugin set this tag; it is not standard Rust are the tags Rusty Moose |EU Biweekly| publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
12.
How is Rusty Moose |EU Biweekly| joined?
Enter client.connect 4.182.234.116:27034 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://moose.gg.
NotesAnswered from the figuresRG-S4846-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp100,ptrak,v2634,everytwoweeks,official,vanilla,hbff4ad10,stok,gmrust
Game
gmrust
Game modeSurvival in standard Rust style.
mp100
Max playersThe slot count is 100.
v2634
ProtocolTo join, your game must be on protocol 2634.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
Difficulty
vanilla
VanillaNo changed rates, kits or rules: the game as Facepunch ships it.
Other
everytwoweeks
Custom tagThe owner or a plugin set this tag; it is not standard Rust.
official
Custom tagThe owner or a plugin set this tag; it is not standard Rust.
hbff4ad10
Custom tagThe owner or a plugin set this tag; it is not standard Rust.
stok
Custom tagThe owner or a plugin set this tag; it is not standard Rust.
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.
