RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h4 Scan5 min
‹ All servers37.214.34.141:28015
Offline Full Queue Fresh wipe Wipe due No query

VladMurkov

Offline 37.214.34.141:28015 checked 5d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

Players now

0% full 7-day avg7-day peak
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 average1peak 1
Rank#11,550top 52%
Last wipe5d 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
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 52% 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
Thu 22 Oct, 22:09 UTC5d ago 1 – running 0

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

Reset cycle

What happens on VladMurkov when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does VladMurkov wipe?

To tell the rhythm of VladMurkov, 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. 5 days 21 hours ago the current world was made.

Lists and filters

How should you read the tags on VladMurkov?

These are the tags VladMurkov publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does VladMurkov appear in Rust Metrics lists and filters?

Rust Metrics lists featuring VladMurkov: 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; Last wipe: In the last week.

Occupancy

Where does VladMurkov sit in the rankings?

Ranking for VladMurkov: #11,550 on seven-day player hours, top 52% of all ranked servers.

What player count does VladMurkov carry?

Reading for VladMurkov: offline at this moment; last seen 5 days 20 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

Which location does VladMurkov run from?

Reading: location. VladMurkov gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 37.214.34.141:28015.

What Rust version is VladMurkov on?

Rust network protocol 2635 and build 168909 on Windows is the build VladMurkov runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. VladMurkov last answered 5 days 20 hours ago. Reading: 0% uptime over the last 5 full days. It was up 0 of 120 hours. The first sighting on Rust Metrics was 22 October 2026.

Settings and map

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

Check: gather rate. The name VladMurkov does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is VladMurkov on?

The game generates a procedural map for VladMurkov.

Connection

What do you do to join VladMurkov?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region 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.