Rust StatisticsWorking papers on every public Rust server · 34,643 players now

Budka bypass

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 31d ago · 5.130.150.236:28015

Abstract

We describe the public Rust server Budka bypass, reached at 5.130.150.236:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #16,818 of all servers, the top 72%. It last wiped 31d 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 now0/5000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#16,818top 72%
Last wipe31d 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, measured since 26 Sep.

4Rank

The server stands in the top 72% 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 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

Map of Budka bypass
Figure 4: The map: Procedural Map, size 3500, seed 1234567. Open on RustMaps.
Table 3: The server's published settings.
Address5.130.150.236:28015
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe26 Sep 2026, 19:54 UTC
Hostname–
First seen26 Sep 2026
MapProcedural Map
Size3500
Seed1234567

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2] and predicted wipe schedule [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 · 533 on average233/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 325 on average14/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 323 on average19/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average143/200
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average41/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average40/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Budka bypass?

A region is not published by Budka bypass. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 5.130.150.236:28015.

A.2What is the reliability of Budka bypass, and is it online?

At the present moment, Budka bypass is offline; it was last seen 31 days 6 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 26 September 2026 by Rust Statistics.

A.3What version of Rust is run on Budka bypass?

Budka bypass is running Rust network protocol 2633 and build 165217 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4When are wipes carried out on Budka bypass?

There are not yet enough recorded wipes for Budka bypass to reveal its rhythm. 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 31 days 9 hours.

Population

A.5How does Budka bypass compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Budka bypass at #16,818, within the top 72% of ranked servers.

A.6What is the population level of Budka bypass?

At this moment Budka bypass is offline, having last been seen 31 days 6 hours ago.

Tags and filters

A.7What do the tags associated with Budka bypass signify?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): It offers 500 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set, which Budka bypass publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.8Where can Budka bypass be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Budka bypass: 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.

Rules, settings, map

A.9What are the settings and rules that govern Budka bypass?

No gather rate appears in the name of Budka bypass. 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. Players may raid and fight one another. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.10What map is in use on Budka bypass?

Generated by the game from seed 1234567, the procedural map on Budka bypass measures 3,500. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.11What is the process for joining Budka bypass?

Enter client.connect 5.130.150.236: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. Teams are limited to 8, as the game defaults.
v2633Protocol. Your game must run protocol 2633 to connect.
cs165217Build. The game build is 165217.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.