RUST METRICSFlight deck · live data
Data live Servers11,837 Players77,657 Populated3,729 Fresh wipes 3 h257 Scan5 min
‹ All servers37.215.6.144:28015
Offline Full Queue Fresh wipe Wipe due No query

YoilkaVUgol

Offline 37.215.6.144:28015 checked 33d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,939top 69%
Last wipe33d 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
15k10k15k20k23 Sep25 Sep27 Sep29 Sep1 Oct3 Oct

Top 69% 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

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 06:16 UTC33d 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

Wipe schedule

What should you expect from wipe day on YoilkaVUgol?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does YoilkaVUgol wipe, and when?

To tell the rhythm of YoilkaVUgol, 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 in play was created 33 days 7 hours ago.

Tag meanings

How should you read the tags on YoilkaVUgol?

These are the tags YoilkaVUgol publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163501 (Build): The server runs game build 163501; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.

Which lists and filters on Rust Metrics show YoilkaVUgol?

Rust Metrics lists featuring YoilkaVUgol: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does YoilkaVUgol hold among Rust servers?

Ranking for YoilkaVUgol: #15,939 on seven-day player hours, top 69% of all ranked servers.

What player count does YoilkaVUgol carry?

YoilkaVUgol is not responding; status offline, last seen 33 days 6 hours ago.

Server details

Where does YoilkaVUgol sit?

No region comes from YoilkaVUgol. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 37.215.6.144:28015.

What Rust version is YoilkaVUgol on?

Rust network protocol 2633 and build 163501 on Windows is the build YoilkaVUgol runs. Check: protocol. To join, your game must match; Steam handles the update.

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

YoilkaVUgol reports offline. The last reading came 33 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 23 September 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for YoilkaVUgol. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is YoilkaVUgol on?

Procedural map on YoilkaVUgol, made by the game's generator.

Join

What do you do to join YoilkaVUgol?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs163501,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163501
Build The server runs game build 163501.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.