Rust Server TrendsSeismic network · station log
Recording Stations11,877 Players95,616 Active4,087 Wipes · 3 h156 48 h

Station XX-14347 · no signal

ZALUPA_EBATb

Offline 88.201.154.64:28015 checked 31d ago

Connect
Players now
1/ 12
8% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,347
top 61%
Last wipe
31d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14347 · 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 12 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

Top 61% 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 · 501 on average
822/ 850
Rustoria.co - EU Main EU · groups of 16+ · weekly · 347 on average
51/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 342 on average
129/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 314 on average
463/ 525
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 281 on average
284/ 350
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 258 on average
213/ 300
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on ZALUPA_EBATb?

ZALUPA_EBATb uses a procedural map, which the game generates.

Which settings and rules apply on ZALUPA_EBATb?

The name of ZALUPA_EBATb gives no gather rate. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on ZALUPA_EBATb?

ZALUPA_EBATb is not responding at this moment and is offline, last seen 31 days 1 hours ago.

How does ZALUPA_EBATb rank against other Rust servers?

The last seven days of player hours place ZALUPA_EBATb at #14,347, in the top 61% of all ranked servers.

Operator and location

How reliably does ZALUPA_EBATb stay online?

No contact with ZALUPA_EBATb right now, and the last recorded contact was 31 days 1 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 26 September 2026.

Which region does ZALUPA_EBATb run from?

A region is not published by ZALUPA_EBATb. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 88.201.154.64:28015.

What build of Rust does ZALUPA_EBATb use?

Rust network protocol 2633 and build 165217 on Windows is what ZALUPA_EBATb runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

On what timetable does ZALUPA_EBATb run its wipes?

The rhythm of ZALUPA_EBATb 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. The present world dates from 31 days 2 hours.

Lists and tags

What do the server tags on ZALUPA_EBATb mean?

The game's server browser reads the tags ZALUPA_EBATb publishes: gmrust (Game mode): You'll find standard Rust survival here; mp12 (Max players): 12 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): It runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. 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 ZALUPA_EBATb appear?

These Rust Server Trends lists include ZALUPA_EBATb: 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 ZALUPA_EBATb?

Enter client.connect 88.201.154.64: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 mp12,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp12
Max players 12 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build It runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

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.