RUST METRICSFlight deck · live data
Data live Servers11,841 Players73,926 Populated3,704 Fresh wipes 3 h221 Scan5 min
‹ All servers65.108.207.14:28015
Offline Full Queue Fresh wipe Wipe due No query

b3r1k Rust — HEL (procedural)

Offline 65.108.207.14:28015 checked 43d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% 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#15,480no region published
Last wipe66d agono schedule published
Next wipe–no wipe 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 schedule

How often does b3r1k Rust — HEL (procedural) wipe, and when?

Its rhythm cannot be told from the wipes of b3r1k Rust — HEL (procedural) on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 66 days 5 hours ago.

Tag meanings

Which tags does b3r1k Rust — HEL (procedural) carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2632 (Protocol): Your game must run protocol 2632 to get in; cs161125 (Build): Build 161125; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from b3r1k Rust — HEL (procedural). Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show b3r1k Rust — HEL (procedural)?

On Rust Metrics, b3r1k Rust — HEL (procedural) sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does b3r1k Rust — HEL (procedural) hold among Rust servers?

Player hours over seven days put b3r1k Rust — HEL (procedural) at #15,480, in the top – of all ranked servers.

What is the population on b3r1k Rust — HEL (procedural)?

Reading for b3r1k Rust — HEL (procedural): offline at this moment; last seen 43 days 7 hours ago.

Server

Where does b3r1k Rust — HEL (procedural) sit?

Reading: location. b3r1k Rust — HEL (procedural) gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 65.108.207.14:28015.

What Rust version is b3r1k Rust — HEL (procedural) on?

Version check: Rust network protocol 2632 and build 161125 on Linux, run by b3r1k Rust — HEL (procedural). Check: protocol. To join, your game must match; Steam handles the update.

How reliable is b3r1k Rust — HEL (procedural), and is it online now?

Reading: offline. b3r1k Rust — HEL (procedural) last answered 43 days 7 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 13 September 2026.

Settings and map

How is b3r1k Rust — HEL (procedural) configured, and what rules are in force?

No gather rate appears in the name: b3r1k Rust — HEL (procedural). The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

Which map is live on b3r1k Rust — HEL (procedural)?

The game generates a procedural map for b3r1k Rust — HEL (procedural).

Connection

How do you connect to b3r1k Rust — HEL (procedural)?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2632,gmrust,cs161125,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2632
Protocol Your game must run protocol 2632 to get in.
cs161125
Build Build 161125.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.