StatusLive Servers online11,795 Players69,100 Populated3,591 Wiped · 3 h187 Interval5 min Date29 OCT 2026

DWG RG-S12984Server sheetchecked 11d ago

pomerovsky

Offline 143.179.99.252:28015 checked 11d ago

Connect
Players now 1/ 1 100% full
7-day average0peak –
Rank#12,984top 59%
Last wipe18d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on pomerovsky
Fig. 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.

Fig. 2FPS, entities and memory
Fig. 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.

Fig. 3Rank on player hours, daily
Schedule

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average
508 / 550
02
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
423 / 450
03
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average
57 / 250
04
Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average
58 / 250
05
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average
57 / 100
06
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 241 on average
151 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is pomerovsky, and is it online now?

pomerovsky is offline at this moment; 11 days 18 hours ago is when it was last seen. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 11 October 2026 is when Rust Graphs first saw it.

What location is recorded for pomerovsky?

A region is not published by pomerovsky. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 143.179.99.252:28015.

On which Rust version is pomerovsky running?

Rust network protocol 2634 and build 167398 on Windows: that is what pomerovsky runs. Steam updates your game, which must be on the same protocol for you to join.

Player data

What does the population history show for pomerovsky?

pomerovsky is not responding at the latest refresh; the last record of it online is 11 days 18 hours ago.

Against other Rust servers, where is pomerovsky placed?

Over the last seven days, pomerovsky records #12,984 for player hours: the top 59% of all ranked servers.

Schedules

What happens on pomerovsky on the day of a wipe?

The recent wipes averaged a busiest count of 1 players. At 0 hours after the latest wipe the crowd was at its peak.

What wipe schedule has been recorded for pomerovsky?

pomerovsky's rhythm cannot be told yet: too few of its wipes are on record. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 18 days 1 hours ago.

Settings

What settings and rules apply on pomerovsky?

Gather rate for pomerovsky: not stated in the name. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. It appears under Community in the server browser. VAC is on: that is Valve's anti-cheat.

What is the map for pomerovsky?

A procedural map, generated by the game, is what pomerovsky runs.

Filters

On Rust Graphs, which lists and filters contain pomerovsky?

The Rust Graphs lists that carry pomerovsky are: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

On pomerovsky, what is meant by each tag?

gmrust (Game mode): Survival in standard Rust style; mp1 (Max players): The slot count is 1; ts8 (Group limit): The default team size of 8 applies; v2634 (Protocol): Your game must match protocol 2634 to join; cs167398 (Build): Build: 167398; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty are the tags pomerovsky publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

How is pomerovsky joined?

Enter client.connect 143.179.99.252:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp1
Max players The slot count is 1.
ts8
Group limit The default team size of 8 applies.
v2634
Protocol Your game must match protocol 2634 to join.
cs167398
Build Build: 167398.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

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.

KeyTag string decoded