Budka bypass
Offline 5.130.150.236:28015 checked 20d 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, measured since 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 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| 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
- 321/ 400
- 537/ 600
- 199/ 225
- 274/ 325
- 288/ 350
- 352/ 425
Quick answers
Tags and listings
Where does Budka bypass appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Budka bypass: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Budka bypass?
Budka bypass's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp500 (Max players): The slot count is 500; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): This server runs build 165217; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is Budka bypass in?
No region comes from Budka bypass. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 5.130.150.236:28015.
What's the uptime like for Budka bypass?
The server Budka bypass is not reachable at the moment; the last sighting was 20 days 23 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 26 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Budka bypass?
The version on Budka bypass is Rust network protocol 2633 and build 165217, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
When does Budka bypass wipe?
Too few wipes are on record for Budka bypass to show its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 21 days 2 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Budka bypass running?
The name of Budka bypass contains no gather rate. Up to 8 players per group, which is the 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, Valve's anti-cheat, is enabled.
What's the map on Budka bypass?
The map on Budka bypass is procedural and size 3,500, generated by the game with seed 1234567. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Population
What's the population like on Budka bypass?
Budka bypass was last seen 20 days 23 hours ago and is offline as you read this.
What position does Budka bypass hold in the server rankings?
For player hours in the last seven days, Budka bypass ranks #16,818, within the top 72% of ranked servers.
Join info
How do you get into Budka bypass?
Open Rust and press F1, then type client.connect 5.130.150.236:28015. Alternatively, click Launch Rust on this page to join via Steam.