RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers88.201.154.64:28015
Offline Full Queue Fresh wipe Wipe due No query

ZALUPA_EBATb

Offline 88.201.154.64:28015 checked 32d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 3 6 9 12 PAX 1 /12

Players now

8% 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#14,347top 61%
Last wipe32d agono schedule published
Next wipe–no wipe 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does ZALUPA_EBATb follow?

Its rhythm cannot be told from the wipes of ZALUPA_EBATb 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. 32 days 3 hours ago the current world was made.

Tags

How should you read the tags on ZALUPA_EBATb?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp12 (Max players): 12 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from ZALUPA_EBATb. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does ZALUPA_EBATb appear in Rust Metrics lists and filters?

Rust Metrics lists featuring ZALUPA_EBATb: 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.

Player count

What position does ZALUPA_EBATb hold among Rust servers?

Player hours over seven days put ZALUPA_EBATb at #14,347, in the top 61% of all ranked servers.

How full does ZALUPA_EBATb get?

ZALUPA_EBATb is not responding; status offline, last seen 32 days 2 hours ago.

Operator and location

Which location does ZALUPA_EBATb run from?

No region comes from ZALUPA_EBATb. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 88.201.154.64:28015.

What Rust version is ZALUPA_EBATb on?

Reading: ZALUPA_EBATb, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. ZALUPA_EBATb last answered 32 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 26 September 2026.

Settings and map

What rules does ZALUPA_EBATb enforce, and what are its settings?

Check: gather rate. The name ZALUPA_EBATb does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is ZALUPA_EBATb on?

Procedural map on ZALUPA_EBATb, made by the game's generator.

How to join

How can you get onto ZALUPA_EBATb?

Check: join. Open Rust, press F1, then enter client.connect 88.201.154.64:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp12
Max players 12 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.