Skip to the page
RUST ANALYTICS
LIVE38,406PLY11,450SRV
QUOTE 5.130.150.236:28015 Offline checked 17d ago

Budka bypass

Players · last
0/ 500
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 500
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#16,818
top 72%
Rank · 7d ago
#14,762
2056 places down
Last wipe
17d ago
no schedule published
Next wipe
–
no wipe seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
3500
Procedural Map · seed 1234567
First seen
26 Sep 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

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
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 406 on average299/325−22−6.9%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 355 on average46/225−133−74.3%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 336 on average217/250+40+22.7%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 333 on average168/200−14−7.6%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average24/250−15−39.1%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 281 on average134/175−34−20.2%

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on Budka bypass?

No gather rate is given in the name of Budka bypass. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Community is its listing in the server browser. VAC, Valve's anti-cheat, is enabled.

What is the current map on Budka bypass?

The map on Budka bypass is procedural, size 3,500, with seed 1234567, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.

Player Count

Where does Budka bypass sit in the rankings?

In the top 72% of all ranked servers, Budka bypass is #16,818 on player hours over the last seven days.

How full is Budka bypass?

Right now, Budka bypass is offline; the last sighting was 17 days 10 hours ago.

Wipe Cycle

On what cycle does Budka bypass wipe?

No rhythm can be told for Budka bypass yet: too few of its wipes are on record. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 17 days 12 hours.

Server Details

What is the location of Budka bypass?

There is no region published for Budka bypass. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 5.130.150.236:28015 is its address.

Budka bypass runs which version of Rust?

The version in use at Budka bypass: Rust network protocol 2633 and build 165217, on Windows. The protocol has to match for you to join, and Steam applies that update.

How reliable is Budka bypass and is it currently online?

No response from Budka bypass. It was last seen 17 days 10 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. 26 September 2026 is when Rust Analytics first saw it.

Tags & Filters

How should you interpret the tags on Budka bypass?

These tags are published by Budka bypass and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp500 (Max players): Capacity: 500 slots; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): To join, your game needs protocol 2633; cs165217 (Build): Game build: 165217; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Budka bypass appears in which of the lists and filters on Rust Analytics?

These Rust Analytics lists include Budka bypass: Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to Join

What is the process to join Budka bypass?

Type client.connect 5.130.150.236:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Rust's standard survival mode.
mp500
Max players Capacity: 500 slots.
ts8
Group limit Team size stays at the game default of 8.
v2633
Protocol To join, your game needs protocol 2633.
cs165217
Build Game build: 165217.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code No region code has been 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.