RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,840 Populated3,354 Fresh wipes 3 h124 Scan5 min
‹ All servers82.99.58.139:28015
Offline Full Queue Fresh wipe Wipe due No query

ALEKSEYKA2

Offline 82.99.58.139:28015 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% 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#13,631top 62%
Last wipe18d 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
15k10k15k20k6 Oct8 Oct10 Oct13 Oct15 Oct17 Oct

Top 62% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 14:05 UTC18d ago 1 – running 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 should you expect from wipe day on ALEKSEYKA2?

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

What wipe timing does ALEKSEYKA2 follow?

The rhythm of ALEKSEYKA2's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 18 days 9 hours ago.

Tag meanings

Which tags does ALEKSEYKA2 carry, and what do they mean?

These are the tags ALEKSEYKA2 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does ALEKSEYKA2 appear in Rust Metrics lists and filters?

On Rust Metrics, ALEKSEYKA2 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.

Population

Where does ALEKSEYKA2 sit in the rankings?

Ranking for ALEKSEYKA2: #13,631 on seven-day player hours, top 62% of all ranked servers.

How full does ALEKSEYKA2 get?

Reading for ALEKSEYKA2: offline at this moment; last seen 18 days 6 hours ago.

Operator and location

Which location does ALEKSEYKA2 run from?

Reading: location. ALEKSEYKA2 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 82.99.58.139:28015.

What Rust version is ALEKSEYKA2 on?

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

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

Reading: offline. ALEKSEYKA2 last answered 18 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 6 October 2026.

Map and rules

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

Reading the name gives no gather rate for ALEKSEYKA2. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on ALEKSEYKA2?

The game generates a procedural map for ALEKSEYKA2.

Join

How can you get onto ALEKSEYKA2?

Press F1 in Rust and enter client.connect 82.99.58.139:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players The server holds 3 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Build 167398.
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.