Offline 75.175.131.181:28015 checked 1d ago
BZPVETEST
Connect
srv = rust.server("75.175.131.181:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 6 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 18:41 UTC10d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 17:38 UTC FW27d ago | 1 | halved by day 8 | 17 days | 0 |
| 2 | Mon 28 Sep, 04:21 UTC30d ago | 0 | NaN | 3.6 days | 0 |
# 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.
display(srv.map, srv.info())Map
4250 · seed 1413175854
- map
- Custom Map
- size
- 4250
- seed
- 1413175854
Server
srv.info()- address
- 75.175.131.181:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 18:41 UTC
- hostname
- –
- first seen
- 20 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 132/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 117/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 33/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 33/1000 |
Quick answers
From the figures on this page.
Population data
What position does BZPVETEST take in the server rankings?
Rank #15,323 on seven-day player hours for BZPVETEST, within the top 69% of all ranked servers.
How full does BZPVETEST run?
BZPVETEST returns no live count at this refresh, having last been seen 42 hours ago. Over the last seven days it averaged 0 players.
Server facts
How smoothly does BZPVETEST run?
The 48-hour average is 40 server fps, with a low of 40. The entity count peaked at 96,743, covering buildings, deployables and the rest of the world. A high of 5,085 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on BZPVETEST?
Rust network protocol 2634 and build 167781 on Linux is what BZPVETEST runs. The protocol has to match before you can join, and Steam does the updating.
Is BZPVETEST up, and what does its uptime show?
Offline now for BZPVETEST, last seen 42 hours ago. A restart about 8 days 6 hours ago is what its reported uptime implies. Uptime of 87% across the last 7 full days: 146 hours of 168. Rust Data logged it first on 20 September 2026.
Which location does BZPVETEST run from?
For BZPVETEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 75.175.131.181:28015.
Rules, settings, map
Which settings and rules does BZPVETEST run?
No gather rate appears in the name: BZPVETEST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has BZPVETEST loaded?
The game generates the map on BZPVETEST: procedural, size 4,250, seed 1413175854. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe data
On what schedule does BZPVETEST wipe?
No next wipe can be predicted for BZPVETEST, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 10 days 2 hours ago, and that is the one in play.
On BZPVETEST, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 8.
Lists and tags
Which lists on Rust Data hold BZPVETEST, and which filters?
On Rust Data, BZPVETEST appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on BZPVETEST?
The game's server browser reads these tags from BZPVETEST: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into BZPVETEST?
In Rust, F1 opens the console: type client.connect 75.175.131.181:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://battlezone.gg/.