RUST METRICSFlight deck · live data
Data live Servers11,809 Players80,805 Populated3,802 Fresh wipes 3 h104 Scan5 min
‹ All servers75.175.131.181:28015
Offline Full Queue Fresh wipe Wipe due No query

BZPVETEST

Offline 75.175.131.181:28015 checked 1d ago

moddedoxide
COM 1 · connect

Server instruments

last reading Tue 01:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 40 SERVER FPS

Server fps

48 h low 40 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 96,509 ×1000

Entities

48 h range 94,586–96,743 · memory 4,757 MB
1239 ET SINCE RESTART 8D 06H

Uptime

8 days 6 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,323top 69%
Last wipe10d agono schedule published
Next wipe–no rhythm it keeps
Memory4,757MBat the last reading
REC 1

Players

AveragePeak
0123421:0022:0023:0000:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304021:0022:0023:0000: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

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.

usual gap10.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 18:41 UTC10d ago 1 – running 0
Thu 1 Oct, 17:38 UTC FW27d ago 1 halved by day 8 17 days 0
Mon 28 Sep, 04:21 UTC30d ago 0 – 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.

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 schedule

What happens on BZPVETEST when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 8 when it didn't.

What wipe timing does BZPVETEST follow?

No next wipe can be predicted for BZPVETEST, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 10 days 1 hours ago.

Tag meanings

Which tags does BZPVETEST carry, and what do they mean?

These are the tags BZPVETEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does BZPVETEST appear in Rust Metrics lists and filters?

Rust Metrics lists featuring BZPVETEST: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does BZPVETEST hold among Rust servers?

Ranking for BZPVETEST: #15,323 on seven-day player hours, top 69% of all ranked servers.

How full does BZPVETEST get?

Status for BZPVETEST: offline. Last seen 42 hours ago. Check: player average. 0 over the last seven days.

Server details

Where does BZPVETEST sit?

No region comes from BZPVETEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 75.175.131.181:28015.

What Rust version is BZPVETEST on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by BZPVETEST. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for BZPVETEST?

Check: fps. Average 40 server fps over the last 48 hours, low of 40. Within range. Check: entities. The peak was 96,743, counting buildings, deployables and the rest of the world. Memory peak: 5,085 MB. Expect lag when fps falls and entities climb.

How reliable is BZPVETEST, and is it online now?

Reading: offline. BZPVETEST last answered 42 hours ago. Check: restart. The uptime it reports puts the last restart about 8 days 6 hours ago. Uptime for the last 7 full days: 146 of 168 hours, or 87%. The first sighting on Rust Metrics was 20 September 2026.

Map and rules

What rules does BZPVETEST enforce, and what are its settings?

No gather rate appears in the name: BZPVETEST. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is BZPVETEST on?

Check: map. Procedural, size 4,250, seed 1413175854, generated by the game on BZPVETEST. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Join

How can you get onto BZPVETEST?

Press F1 in Rust and enter client.connect 75.175.131.181:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://battlezone.gg/ is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.