RUST METRICSFlight deck · live data
Data live Servers11,668 Players53,558 Populated3,336 Fresh wipes 3 h86 Scan5 min
‹ All servers178.95.117.12:28015
Offline Full Queue Fresh wipe Wipe due No query

zalupka

Offline 178.95.117.12:28015 checked 42d 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#15,418no region published
Last wipe43d 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 timing

When does zalupka wipe?

The rhythm of zalupka's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 43 days 18 hours ago.

Tag meanings

How should you read the tags on zalupka?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from zalupka. 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?

These Rust Metrics lists carry zalupka: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does zalupka sit in the rankings?

Ranking for zalupka: #15,418 on seven-day player hours, top – of all ranked servers.

What is the population on zalupka?

Reading for zalupka: offline at this moment; last seen 42 days 17 hours ago.

Server details

Where does zalupka sit?

Reading: location. zalupka gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 178.95.117.12:28015.

What Rust version is zalupka on?

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

Is zalupka up, and how often does it stay up?

Check: connection. zalupka is offline at this moment. Last contact was 42 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on zalupka?

Check: gather rate. The name zalupka does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is zalupka on?

The game generates a procedural map for zalupka.

Join

How can you get onto zalupka?

Press F1 in Rust and enter client.connect 178.95.117.12:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.