RUST METRICSFlight deck · live data
Data live Servers11,894 Players101,584 Populated3,939 Fresh wipes 3 h404 Scan5 min
‹ All servers95.54.230.81:28015
Offline Full Queue Fresh wipe Wipe due No query

Pavka

Offline 95.54.230.81:28015 checked 37d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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,149top 62%
Last wipe37d agono schedule published
Next wipe–too few wipes 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 Sep22 Sep24 Sep25 Sep27 Sep29 Sep

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

PLAN

Wipe schedule

too few wipes seen yet

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

usual gap2.9 daysbetween real wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Tue 22 SepSat 19 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 22 Sep, 10:33 UTC37d ago 1 – running 1
Sat 19 Sep, 13:34 UTC40d ago 2 – 2.9 days 1

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 should you expect from wipe day on Pavka?

An average of 2 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Pavka follow?

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

Tag meanings

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

Tags published by Pavka, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Pavka appear in Rust Metrics lists and filters?

On Rust Metrics, Pavka sits in these lists: 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.

Occupancy

Where does Pavka sit in the rankings?

Ranking for Pavka: #14,149 on seven-day player hours, top 62% of all ranked servers.

What player count does Pavka carry?

Pavka is not responding; status offline, last seen 37 days 6 hours ago.

Server details

Which location does Pavka run from?

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

What Rust version is Pavka on?

Rust network protocol 2633 and build 164530 on Windows is the build Pavka runs. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. Pavka last answered 37 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Rules and settings

How is Pavka configured, and what rules are in force?

Check: gather rate. The name Pavka does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Pavka?

Check: map. Procedural, generated by the game, on Pavka.

Join

How do you connect to Pavka?

Press F1 in Rust and enter client.connect 95.54.230.81: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 mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.