RUST METRICSFlight deck · live data
Data live Servers11,665 Players33,246 Populated2,811 Fresh wipes 3 h81 Scan5 min
‹ All servers95.104.205.191:28015
Offline Full Queue Fresh wipe Wipe due No query

zalupka

Offline 95.104.205.191:28015 checked 43d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% 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,464no region published
Last wipe44d 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
15k10k15k20k20 Sep21 Sep22 Sep
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

When does zalupka wipe?

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

Tag meanings

Which tags does zalupka carry, and what do they mean?

These are the tags zalupka publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does zalupka appear in Rust Metrics lists and filters?

On Rust Metrics, zalupka sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does zalupka hold among Rust servers?

Player hours over seven days put zalupka at #14,464, in the top – of all ranked servers.

What is the population on zalupka?

zalupka is not responding; status offline, last seen 43 days 15 hours ago.

Server

Where does zalupka sit?

No region tag on zalupka. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 95.104.205.191:28015.

What Rust version is zalupka on?

Rust network protocol 2633 and build 163794 on Windows is the build zalupka runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is zalupka, and is it online now?

Check: connection. zalupka is offline at this moment. Last contact was 43 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 14 September 2026.

Map and rules

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

Check: gather rate. The name zalupka does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is zalupka on?

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

Join

How do you connect to zalupka?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.