RUST METRICSFlight deck · live data
Data live Servers11,626 Players40,285 Populated2,838 Fresh wipes 3 h132 Scan5 min
‹ All servers188.112.144.154:28015
Offline Full Queue Fresh wipe Wipe due No query

ALEKSEYKA2

Offline 188.112.144.154:28015 checked 4d ago

COM 1 · connect

Server instruments

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

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,270top 69%
Last wipe19d 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
15k10k15k20k24 Sep29 Sep14 Oct19 Oct25 Oct30 Oct

Top 69% 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, 24 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 14:05 UTC19d 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 schedule

What happens on ALEKSEYKA2 when wipe day comes?

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

When does ALEKSEYKA2 wipe?

Its rhythm cannot be told from the wipes of ALEKSEYKA2 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 19 days 14 hours ago the current world was made.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): Slots: 3; 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): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from ALEKSEYKA2. 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. 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.

Occupancy

Where does ALEKSEYKA2 sit in the rankings?

Ranking for ALEKSEYKA2: #15,270 on seven-day player hours, top 69% of all ranked servers.

What is the population on ALEKSEYKA2?

Status for ALEKSEYKA2: offline. Last seen 4 days 10 hours ago. Check: player average. 0 over the last seven days.

Operator and location

What location is ALEKSEYKA2 hosted in?

Reading: location. ALEKSEYKA2 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.112.144.154:28015.

What Rust version is ALEKSEYKA2 on?

Rust network protocol 2634 and build 167398 on Windows is the build ALEKSEYKA2 runs. To get in, your game needs the same protocol; Steam applies the update.

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

ALEKSEYKA2 reports offline. The last reading came 4 days 10 hours ago. Uptime for the last 7 full days: 1 of 168 hours, or 1%. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on ALEKSEYKA2?

Check: gather rate. The name ALEKSEYKA2 does not state one. 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. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is ALEKSEYKA2 on?

The game generates a procedural map for ALEKSEYKA2.

Join

How can you get onto ALEKSEYKA2?

Press F1 in Rust and enter client.connect 188.112.144.154: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 Slots: 3.
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 This is RakNet, Rust's usual network layer.
$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.