Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h57 48 h

Station XX-13183 · no signal

lexazabivnoi228

Offline 77.79.177.182:28015 checked 36d ago

Connect
Players now
1/ 15
7% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,183
top 57%
Last wipe
43d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13183 · 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 15 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
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 57% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 552 on average
636/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
485/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 299 on average
59/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 298 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 270 on average
138/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 256 on average
255/ 300
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on lexazabivnoi228?

lexazabivnoi228 uses a procedural map, which the game generates.

Which settings and rules apply on lexazabivnoi228?

You will find no gather rate in the name of lexazabivnoi228. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on lexazabivnoi228 right now?

A reading taken now finds lexazabivnoi228 offline; the most recent activity was 36 days 1 hours ago.

How does lexazabivnoi228 rank against other Rust servers?

Over the last seven days, lexazabivnoi228 recorded enough player hours to reach #13,183 worldwide, placing it in the top 57% of all ranked servers.

Server facts

How reliably does lexazabivnoi228 stay online?

lexazabivnoi228 is down at the moment; the last recorded contact was 36 days 1 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 22 September 2026 is when Rust Server Trends first recorded it.

Which region does lexazabivnoi228 run from?

No region is published by lexazabivnoi228. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 77.79.177.182:28015 is the address it uses.

What build of Rust does lexazabivnoi228 use?

lexazabivnoi228 is running Rust network protocol 2633 and build 165217 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

How often does lexazabivnoi228 wipe, and on which days?

Too few wipes of lexazabivnoi228 are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 43 days 8 hours is how long the current world has been running.

Lists and tags

What do the server tags on lexazabivnoi228 mean?

Tags published by lexazabivnoi228 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp15 (Max players): The server has 15 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does lexazabivnoi228 appear?

These Rust Server Trends lists include lexazabivnoi228: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto lexazabivnoi228?

To join, enter client.connect 77.79.177.182:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp15
Max players The server has 15 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build Game build: 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been 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.

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.