Skip to the page
Network live 11,722 servers online 55,260 players aboard 135 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

BZPVETEST

Offline 75.175.131.181:28015 checked 22h ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 9d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 50 players now 0% full
07-day averagepeak –
#15,409ranktop 69%
9d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
0123400:0005:0010:0015:0020:0001:00

Hourly average and peak, UTC.

Server performance

01020304000:0005:0010:0015:0020:0001:00

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
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

10.3 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 8

The first 48 hours of its last wipes

Sun 18 OctThu 1 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

every wipe as a delivery, newest first
  1. Sun 18 Oct, 18:41 UTC 19:41 UK · 9d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 1 Oct, 17:38 UTC FW 18:38 UK · 26d ago
    Force wipe delivered
    Peak
    1
    Crowd
    halved by day 8
    Lasted
    17 days
    Players before
    0
  3. Mon 28 Sep, 04:21 UTC 05:21 UK · 29d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    3.6 days
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 163 on average 48 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average 130 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 113 on average 61 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average 58 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average 13 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average 17 / 1000
Help desk

Quick answers

From the figures on this page.

Player activity

Where does BZPVETEST place among Rust servers?

Over the past seven days, BZPVETEST has climbed to #15,409 for player hours, putting it in the top 69% of all ranked servers.

Is BZPVETEST busy at the moment?

At the moment BZPVETEST is offline, having last been seen 22 hours ago. The seven-day average for this server is 0 players.

Map and rules

On what map does BZPVETEST take place?

Generated by the game with seed 1413175854, the procedural map on BZPVETEST is size 4,250. Size and seed match means the map matches, so you can view it on RustMaps from this page. You will see this map name: Custom Map.

What settings and rules should you know for BZPVETEST?

The name of BZPVETEST gives no gather rate. The game's default applies: 8 players to a group at most. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Oxide supplies the plugins. The VAC anti-cheat from Valve is enabled.

About the server

In which region is BZPVETEST based?

You will find no region published by BZPVETEST. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 75.175.131.181:28015.

What is the performance like on BZPVETEST?

The 48-hour average for server fps stands at 40, never dipping below 40. The world held as many as 96,786 entities: buildings, deployables and the rest. Memory use peaked at 5,085 MB. Players feel a rising entity count and low fps as lag.

Is BZPVETEST up, and how good is its uptime?

Offline for now: BZPVETEST was last seen 22 hours ago. About 8 days 6 hours ago is when it last restarted, judged by the uptime it gives. It was up 168 of 168 hours over the last 7 full days, 100% of the time. The first sighting of it by Rust Wipe Tracker came on 20 September 2026.

On what Rust version does BZPVETEST operate?

Rust network protocol 2634 and build 167781 on Linux is what BZPVETEST runs. The same protocol is required to join, and Steam takes care of updating it.

Wipe schedule

What happens on BZPVETEST when wipe day arrives?

The average busiest point of its recent wipes was 1 players. After 0 hours the latest wipe's crowd hit its peak. Half the peak or more was held until the next wipe in 0% of recent wipes. By day 8 it had fallen below half where the crowd did not hold.

On what schedule does BZPVETEST reset its map?

There is no next wipe to predict for BZPVETEST: it wipes at irregular times. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 9 days 5 hours.

Tags and listings

Where does BZPVETEST appear in Rust Wipe Tracker lists and filters?

You will find BZPVETEST on the following Rust Wipe Tracker lists: Modded Rust servers. You will find it under these filters 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 tags on BZPVETEST?

gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Team limit: 8, the standard default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it's listed under Modded are the tags BZPVETEST publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

How to join

What is the process to join BZPVETEST?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 75.175.131.181:28015. You will find its website at https://battlezone.gg/.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit Team limit: 8, the standard default.
v2634
Protocol Join only if your game runs protocol 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code A region code isn't set.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.