RUST METRICSFlight deck · live data
Data live Servers11,750 Players59,433 Populated3,457 Fresh wipes 3 h135 Scan5 min
‹ All servers82.99.41.2:28015
Offline Full Queue Fresh wipe Wipe due No query

ALEKSEYKA2

Offline 82.99.41.2:28015 checked 24d 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#14,600top 64%
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 Sep24 Sep29 Sep3 Oct6 Oct10 Oct

Top 64% 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 gap12.2 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 1 OctSat 19 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:53 UTC FW26d ago 1 – running 1
Sat 19 Sep, 12:53 UTC38d ago 1 held half 12.2 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 schedule

What happens on ALEKSEYKA2 when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 40 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does ALEKSEYKA2 wipe?

The rhythm of ALEKSEYKA2's wipes cannot be told yet: too few are on record. 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 26 days 4 hours ago.

Tags

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

Tags published by ALEKSEYKA2, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does ALEKSEYKA2 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry ALEKSEYKA2: 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.

Player count

What position does ALEKSEYKA2 hold among Rust servers?

Ranking for ALEKSEYKA2: #14,600 on seven-day player hours, top 64% of all ranked servers.

How full does ALEKSEYKA2 get?

Status for ALEKSEYKA2: offline. Last seen 24 days 12 hours ago.

Operator and location

What location is ALEKSEYKA2 hosted in?

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.41.2:28015.

What Rust version is ALEKSEYKA2 on?

Reading: ALEKSEYKA2, Rust network protocol 2634 and build 166494, Windows. 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 24 days 12 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 18 September 2026.

Rules and settings

What settings and rules apply on ALEKSEYKA2?

No gather rate appears in the name: ALEKSEYKA2. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is ALEKSEYKA2 on?

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

How to join

How can you get onto ALEKSEYKA2?

Press F1 in Rust and enter client.connect 82.99.41.2: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,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players The server holds 3 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Build 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.