Rust Server TrendsSeismic network · station log
Recording Stations11,669 Players53,688 Active3,358 Wipes · 3 h88 48 h

Station XX-13631 · no signal

ALEKSEYKA2

Offline 82.99.58.139:28015 checked 17d ago

Connect
Players now
1/ 3
33% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,631
top 62%
Last wipe
17d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13631 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 3 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 10 Oct, 14:05 UTC17d ago M0.0steady 1 – running 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 540 on average
500/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
313/ 325
Rustoria.co - EU Main EU · groups of 16+ · weekly · 314 on average
35/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 313 on average
35/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 273 on average
157/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
75/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on ALEKSEYKA2?

ALEKSEYKA2 uses a procedural map, which the game generates.

Which settings and rules apply on ALEKSEYKA2?

No gather rate appears in the name of ALEKSEYKA2. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on ALEKSEYKA2 right now?

A reading taken now finds ALEKSEYKA2 offline; the most recent activity was 17 days 17 hours ago.

How does ALEKSEYKA2 rank against other Rust servers?

On player hours for the past week, ALEKSEYKA2 sits at #13,631, which puts it inside the top 62% of every ranked server.

Operator and location

How reliably does ALEKSEYKA2 stay online?

As recorded now, ALEKSEYKA2 is not reachable, the last contact having been 17 days 17 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 6 October 2026 is when Rust Server Trends first recorded it.

Which region does ALEKSEYKA2 run from?

No region is published by ALEKSEYKA2. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 82.99.58.139:28015 is the address it uses.

Which Rust version is ALEKSEYKA2 running?

On Windows, ALEKSEYKA2 runs Rust network protocol 2634 and build 167398. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on ALEKSEYKA2?

On average, the busiest point of its recent wipes drew 1 players. 2 hours into the latest wipe, the crowd reached its peak.

On what timetable does ALEKSEYKA2 run its wipes?

On record so far are too few of ALEKSEYKA2's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 17 days 19 hours.

Tags

What do the server tags on ALEKSEYKA2 mean?

Tags published by ALEKSEYKA2 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp3 (Max players): Slots: 3; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): Game build: 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does ALEKSEYKA2 appear?

The Rust Server Trends lists that take in ALEKSEYKA2 are: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to ALEKSEYKA2?

Enter client.connect 82.99.58.139:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp3
Max players Slots: 3.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167398
Build Game build: 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.