RUST METRICSFlight deck · live data
Data live Servers11,814 Players69,594 Populated3,624 Fresh wipes 3 h187 Scan5 min
‹ All servers143.179.99.252:28015
Offline Full Queue Fresh wipe Wipe due No query

pomerovsky

Offline 143.179.99.252:28015 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#12,984top 59%
Last wipe18d 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
15k10k15k20k11 Oct14 Oct16 Oct19 Oct21 Oct24 Oct

Top 59% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+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
Sun 11 Oct, 11:26 UTC18d ago 1 – running 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 timing

What should you expect from wipe day on pomerovsky?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does pomerovsky follow?

To tell the rhythm of pomerovsky, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 18 days 1 hours ago.

Tags

How should you read the tags on pomerovsky?

These are the tags pomerovsky publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does pomerovsky appear in Rust Metrics lists and filters?

These Rust Metrics lists carry pomerovsky: 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.

Population

What position does pomerovsky hold among Rust servers?

Player hours over seven days put pomerovsky at #12,984, in the top 59% of all ranked servers.

How full does pomerovsky get?

Reading for pomerovsky: offline at this moment; last seen 11 days 18 hours ago.

Server

Where does pomerovsky sit?

No region tag on pomerovsky. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 143.179.99.252:28015.

What Rust version is pomerovsky on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by pomerovsky. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. pomerovsky last answered 11 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 11 October 2026.

Map and rules

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

No gather rate appears in the name: pomerovsky. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on pomerovsky?

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

How to join

How can you get onto pomerovsky?

To join: start Rust, press F1 and type client.connect 143.179.99.252:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.