RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h42 Scan5 min
‹ All servers5.130.150.236:28015
Offline Full Queue Fresh wipe Wipe due No query

Budka bypass

Offline 5.130.150.236:28015 checked 31d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /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#16,818top 72%
Last wipe31d 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, measured since 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

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

Wipe timing

When does Budka bypass wipe?

Its rhythm cannot be told from the wipes of Budka bypass on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 31 days 23 hours ago.

Tag meanings

Which tags does Budka bypass carry, and what do they mean?

These are the tags Budka bypass publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Budka bypass?

These Rust Metrics lists carry Budka bypass: 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.

Occupancy

What position does Budka bypass hold among Rust servers?

Player hours over seven days put Budka bypass at #16,818, in the top 72% of all ranked servers.

How full does Budka bypass get?

Budka bypass is not responding; status offline, last seen 31 days 21 hours ago.

Server details

Which location does Budka bypass run from?

Reading: location. Budka bypass gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 5.130.150.236:28015.

What Rust version is Budka bypass on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by Budka bypass. Matching protocol is required to join. Let Steam update your game.

How reliable is Budka bypass, and is it online now?

Check: connection. Budka bypass is offline at this moment. Last contact was 31 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 26 September 2026.

Rules and settings

How is Budka bypass configured, and what rules are in force?

Reading the name gives no gather rate for Budka bypass. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is Budka bypass on?

From seed 1234567, the game generates the procedural map on Budka bypass. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto Budka bypass?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.