RUST METRICSFlight deck · live data
Data live Servers11,867 Players96,005 Populated3,901 Fresh wipes 3 h390 Scan5 min
‹ All servers46.8.63.249:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust_SERVER_HLEB

Offline 46.8.63.249:28015 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 3 /10

Players now

30% 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#11,121top 50%
Last wipe26d 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
15k10k15k20k20 Sep25 Sep1 Oct6 Oct12 Oct17 Oct

Top 50% 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.

wipe-day peak3players, last three wipes

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 3, 22 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 19:35 UTC26d ago 3 – running 0

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

What happens on Rust_SERVER_HLEB when wipe day comes?

An average of 3 players came at the busiest on its recent wipes. 22 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Rust_SERVER_HLEB follow?

The rhythm of Rust_SERVER_HLEB's wipes cannot be told yet: too few 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 it runs now was made 26 days 20 hours ago.

Tags

How should you read the tags on Rust_SERVER_HLEB?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): Game build reading: 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Rust_SERVER_HLEB. 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 Rust_SERVER_HLEB?

On Rust Metrics, Rust_SERVER_HLEB 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 Rust_SERVER_HLEB hold among Rust servers?

Ranking for Rust_SERVER_HLEB: #11,121 on seven-day player hours, top 50% of all ranked servers.

What player count does Rust_SERVER_HLEB carry?

Rust_SERVER_HLEB is not responding; status offline, last seen 18 days 22 hours ago.

Operator and location

Where does Rust_SERVER_HLEB sit?

No region comes from Rust_SERVER_HLEB. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 46.8.63.249:28015.

What Rust version is Rust_SERVER_HLEB on?

Rust network protocol 2634 and build 166586 on Windows is the build Rust_SERVER_HLEB runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Rust_SERVER_HLEB up, and how often does it stay up?

Rust_SERVER_HLEB reports offline. The last reading came 18 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.

Settings and map

What rules does Rust_SERVER_HLEB enforce, and what are its settings?

Reading the name gives no gather rate for Rust_SERVER_HLEB. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Rust_SERVER_HLEB on?

Procedural map on Rust_SERVER_HLEB, made by the game's generator.

Connection

How do you connect to Rust_SERVER_HLEB?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build Game build reading: 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.