Rust StatisticsWorking papers on every public Rust server · 82,642 players now

bolgarka test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 28d ago · 185.177.189.150:28015

Abstract

We describe the public Rust server bolgarka test, reached at 185.177.189.150:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #14,212 of all servers, the top 60%. It last wiped 28d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/5000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#14,212top 60%
Last wipe28d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 60% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

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

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address185.177.189.150:28015
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 10:58 UTC
Hostname–
First seen1 Oct 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average538/575
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average430/475
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 290 on average167/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average57/100
Rustoria.co - EU MainEU · groups of 16+ · weekly · 275 on average221/250
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 236 on average304/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of bolgarka test?

There is no region published for bolgarka test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 185.177.189.150:28015.

A.2How reliable is bolgarka test, and is it currently online?

Right now, bolgarka test is offline, and the last time it was seen was 28 days 2 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 1 October 2026 by Rust Statistics.

A.3What is the Rust version for bolgarka test?

Rust network protocol 2633 and build 165217 is the version that bolgarka test runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does bolgarka test wipe?

Too few wipes by bolgarka test have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 28 days 3 hours.

Player count

A.5What position does bolgarka test occupy in the ranking of Rust servers?

Ranked by player hours across seven days, bolgarka test holds #14,212, in the top 60% of all ranked servers.

A.6What is the population level of bolgarka test?

The last recorded sighting of bolgarka test was 28 days 2 hours ago; it is offline now.

Tags and filters

A.7What is the meaning of the tags on bolgarka test?

Tags from bolgarka test, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): It offers 500 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs165217 (Build): Build 165217 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can bolgarka test be found among the Rust Statistics lists and filters?

The Rust Statistics lists that bolgarka test fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.9What are the settings and rules that govern bolgarka test?

No gather rate appears in the name of bolgarka test. At 8 players, the group limit equals the game's default. The mode is survival, which means gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

A.10On which map does bolgarka test take place?

On bolgarka test the terrain is procedural, built by the game itself.

Connection

A.11What is the process for joining bolgarka test?

Enter client.connect 185.177.189.150:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp500Max players. It offers 500 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs165217Build. Build 165217 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.