RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h98 Scan5 min
‹ All servers46.163.136.175:28015
Offline Full Queue Fresh wipe Wipe due No query

Berilland

Offline 46.163.136.175:28015 checked 22d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 2 /2

Players now

100% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#12,178top 54%
Last wipe23d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep1 Oct4 Oct7 Oct10 Oct13 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

usual gap7 daysbetween real wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Mon 5 OctMon 28 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 15:07 UTC23d ago 2 – running 1
Mon 28 Sep, 14:07 UTC30d ago 1 – 7 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on Berilland when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does Berilland wipe, and when?

To tell the rhythm of Berilland, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 23 days 3 hours ago.

Tags

How should you read the tags on Berilland?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Berilland. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Berilland appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Berilland: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Berilland hold among Rust servers?

Ranking for Berilland: #12,178 on seven-day player hours, top 54% of all ranked servers.

What is the population on Berilland?

Berilland is not responding; status offline, last seen 22 days 1 hours ago.

Operator and location

Which location does Berilland run from?

No region comes from Berilland. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 46.163.136.175:28015.

What Rust version is Berilland on?

Reading: Berilland, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Berilland, and is it online?

Reading: offline. Berilland last answered 22 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 28 September 2026.

Settings and map

How is Berilland configured, and what rules are in force?

Check: gather rate. The name Berilland does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Berilland on?

Check: map. Procedural, generated by the game, on Berilland.

Connection

How can you get onto Berilland?

To join: start Rust, press F1 and type client.connect 46.163.136.175:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players The server holds 2 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.