Rust Data

rustdata.spaceservers4.182.216.127:27012.ipynb

Run all rust-data · live

‹ All servers

Offline 4.182.216.127:27012 checked 27d ago

Rusty Moose |EU Biweekly

Connect

srv = rust.server("4.182.216.127:27012")
print(srv.connect_command)

Right now

srv.summary()
players now 69/100 # 69% full
7-day average 0 # peak –
rank #4,847 # top 21%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 21% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak70players, last three wipes

The first 48 hours of its last wipes

020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 70, 6 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 05:01 UTC27d ago 70 NaN running 57

# 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.

display(srv.map, srv.info())

Map

4500 · seed 662616
No map picture published
map
Procedural Map
size
4500
seed
662616
Open on RustMaps

Server

srv.info()
address
4.182.216.127:27012
region
–
max players
100
group limit
not published
wipe schedule
–
last wipe
2 Oct 2026, 05:01 UTC
hostname
–
first seen
2 Oct 2026

About this server · in its own words

print(srv.description)
Official Rusty Moose EU Biweekly Wipe Schedule - Map: Biweekly (every other Thursday) @ 15:00 London Time (unless force wipe) - Blueprints: Monthly @ Force Wipe Join our Discord server for announcements and to get more involved with the community! https://moose.gg/vip https://discord.gg/moose Force wipes are always on the first Thursday of the month at 2pm EST / 19:00 London time.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 512 on average335/400
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average435/500
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average979/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average45/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average981/1000
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 235 on average787/800

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Rusty Moose |EU Biweekly rank?

Over the last seven days Rusty Moose |EU Biweekly sits at #4,847 on player hours, in the top 21% of ranked servers.

What population does Rusty Moose |EU Biweekly carry?

Rusty Moose |EU Biweekly returns no live count at this refresh, having last been seen 27 days 7 hours ago.

About the server

What Rust version does Rusty Moose |EU Biweekly run?

Rust network protocol 2634 on Linux is what Rusty Moose |EU Biweekly runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Rusty Moose |EU Biweekly, and is it up?

Rusty Moose |EU Biweekly is offline at this refresh; the last response came 27 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 2 October 2026.

In which location is Rusty Moose |EU Biweekly hosted?

No region tag is published by Rusty Moose |EU Biweekly, though its name points to Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 4.182.216.127:27012 is its address.

Map and rules

Which rules apply on Rusty Moose |EU Biweekly, and what settings?

The name Rusty Moose |EU Biweekly carries no gather rate. The field for group size is empty. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on Rusty Moose |EU Biweekly?

Size 4,500, seed 662616: the procedural map on Rusty Moose |EU Biweekly, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does Rusty Moose |EU Biweekly wipe, and how often?

A rhythm cannot be read from the wipes of Rusty Moose |EU Biweekly on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 27 days 13 hours ago, and that is the one in play.

On Rusty Moose |EU Biweekly, what happens on wipe day?

The average peak over recent wipes is 70 players. Peak population on the latest wipe came 6 hours in.

Tags and filters

Which Rust Data filters and lists contain Rusty Moose |EU Biweekly?

The Rust Data lists that Rusty Moose |EU Biweekly fits are: EU Rust servers and Rust community servers, unfiltered. Under these filters on the server list, it is listed: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Players now: At least 50.

How should you read the server tags on Rusty Moose |EU Biweekly?

These tags are published by Rusty Moose |EU Biweekly and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; v2634 (Protocol): To join, your game must run protocol 2634; ptrak (Networking): Network traffic runs over RakNet, the game standard; vanilla (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; everytwoweeks (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; official (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; h57ebc29a (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; stok (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way into Rusty Moose |EU Biweekly?

In Rust, F1 opens the console: type client.connect 4.182.216.127:27012. Launch Rust on this page does the same by opening the game through Steam and connecting. https://moose.gg is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,v2634,everytwoweeks,official,vanilla,h57ebc29a,stok,gmrust

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players Slot count: 100.
v2634
Protocol To join, your game must run protocol 2634.
ptrak
Networking Network traffic runs over RakNet, the game standard.

Difficulty

vanilla
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Other

everytwoweeks
Custom tag This tag comes from the owner or a plugin, not from Rust itself.
official
Custom tag This tag comes from the owner or a plugin, not from Rust itself.
h57ebc29a
Custom tag This tag comes from the owner or a plugin, not from Rust itself.
stok
Custom tag This tag comes from the owner or a plugin, not from Rust itself.

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.

Rust Data 103,751 players 11,890 servers online