Station XX-14600 · no signal
ALEKSEYKA2
Offline 82.99.41.2:28015 checked 24d ago
- Players now
- 1/ 3
- 33% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,600
- top 64%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 3 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 12.2 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 40 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:53 UTC FW26d ago | M0.0■steady | 1 | – | – | running | 1 |
| Sat 19 Sep, 12:53 UTC38d ago | M0.0■steady | 1 | held half | 12.2 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on ALEKSEYKA2?
A procedural map runs on ALEKSEYKA2, generated by the game.
Which settings and rules apply on ALEKSEYKA2?
The name of ALEKSEYKA2 gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on ALEKSEYKA2 right now?
No players are recorded on ALEKSEYKA2 at this moment; it is offline, and the last sighting was 24 days 14 hours ago.
How does ALEKSEYKA2 rank against other Rust servers?
Over the last seven days, ALEKSEYKA2 recorded enough player hours to reach #14,600 worldwide, placing it in the top 64% of all ranked servers.
Server facts
How reliably does ALEKSEYKA2 stay online?
ALEKSEYKA2 is down at the moment; the last recorded contact was 24 days 14 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 18 September 2026 is when Rust Server Trends first recorded it.
Which region does ALEKSEYKA2 run from?
Nothing about a region comes from ALEKSEYKA2. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 82.99.41.2:28015.
Which Rust version is ALEKSEYKA2 running?
Rust network protocol 2634 and build 166494 on Windows is what ALEKSEYKA2 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on ALEKSEYKA2?
On average, the busiest point of its recent wipes drew 1 players. 40 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does ALEKSEYKA2 wipe, and on which days?
The rhythm of ALEKSEYKA2 cannot yet be told: too few of its wipes are on record. 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 26 days 6 hours.
Tags
What do the server tags on ALEKSEYKA2 mean?
These are the tags ALEKSEYKA2 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp3 (Max players): The server has 3 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. 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.
Join the server
How do you connect to ALEKSEYKA2?
Enter client.connect 82.99.41.2:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.