RUST METRICSFlight deck · live data
Data live Servers11,851 Players93,847 Populated3,878 Fresh wipes 3 h391 Scan5 min
‹ All servers185.177.189.150:28015
Offline Full Queue Fresh wipe Wipe due No query

bolgarka test

Offline 185.177.189.150:28015 checked 28d 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 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,212top 60%
Last wipe28d agono schedule published
Next wipe–no wipe 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does bolgarka test wipe?

The rhythm of bolgarka test's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 28 days 4 hours ago.

Lists and filters

How should you read the tags on bolgarka test?

These are the tags bolgarka test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show bolgarka test?

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

Player count

What position does bolgarka test hold among Rust servers?

Player hours over seven days put bolgarka test at #14,212, in the top 60% of all ranked servers.

What player count does bolgarka test carry?

bolgarka test is not responding; status offline, last seen 28 days 3 hours ago.

Server

Where does bolgarka test sit?

No region comes from bolgarka test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 185.177.189.150:28015.

What Rust version is bolgarka test on?

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

Is bolgarka test up, and how often does it stay up?

Reading: offline. bolgarka test last answered 28 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on bolgarka test?

Check: gather rate. The name bolgarka test does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. 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.

Which map is live on bolgarka test?

Check: map. Procedural, generated by the game, on bolgarka test.

Join

What do you do to join bolgarka test?

Press F1 in Rust and enter client.connect 185.177.189.150: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 mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
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.