bolgarka test
Offline 185.177.189.150:28015 checked 16d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 368/ 375
- 592/ 600
- 391/ 475
- 108/ 200
- 648/ 625
- 261/ 250
Quick answers
Tags and listings
Where does bolgarka test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry bolgarka test are: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on bolgarka test?
bolgarka test's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp500 (Max players): The slot count is 500; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): It's on build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server info
Where can you find bolgarka test?
There is no published region for bolgarka test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 185.177.189.150:28015.
What's the uptime like for bolgarka test?
The server bolgarka test is not reachable at the moment; the last sighting was 16 days 22 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 1 October 2026.
What is the Rust version for bolgarka test?
On Windows, bolgarka test runs Rust network protocol 2633 and build 165217. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does bolgarka test follow for wipes?
The wipes recorded for bolgarka test are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 16 days 23 hours.
Settings and map
Which rules and settings is bolgarka test running?
No gather rate appears in the name of bolgarka test. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Community is where the server browser puts it, as a community server. VAC is on: Valve's anti-cheat is active.
Which map is active on bolgarka test?
The map on bolgarka test is procedural, made by the game.
Player stats
How many players are on bolgarka test?
The last sighting of bolgarka test was 16 days 22 hours ago; it is offline right now.
What position does bolgarka test hold in the server rankings?
Over the last seven days, bolgarka test is #14,212 by player hours, among the top 60% of all ranked servers.
Join info
What's the process to join bolgarka test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 185.177.189.150:28015.