RUST METRICSFlight deck · live data
Data live Servers11,640 Players44,156 Populated3,059 Fresh wipes 3 h105 Scan5 min
‹ All servers136.243.93.153:29025
Online Full Queue Fresh wipe Wipe due No query

BURN ZOMBIE TESTSERVER

Online 136.243.93.153:29025 checked 9m ago

biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 07:00 UTC
0 20 40 60 80 PAX 0 /80

Players now

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

Server fps

48 h low 23 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 78,693 ×1000

Entities

48 h range 71,826–78,693 · memory 4,285 MB
1239 ET SINCE RESTART 21:13

Uptime

21 h 13 min since its last restart, at the last reading
7-day average0peak –
Rank#15,338top 69%
Last wipe10d agobiweekly schedule
Next wipe3d 22hMon 2 Nov, 06:31 UTC
Memory4,285MBat the last reading
REC 1

Players

AveragePeak
0123409:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304009:0018:0003:0012:0022:0007: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 17 Sep. 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 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Monday 2 November, 06:31 UTC, in 3d 22h. Its biweekly schedule tag · low confidence

usual gap4.5 daysbetween real wipes
on rhythm14%of its recent wipes
wipe-day peak1players, last three wipes
crowd held25%else halves by day 1

Coming wipes

  1. WPT 1Mon 2 Nov, 06:31 UTC3d 22h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 10hFW
  3. WPT 3Mon 16 Nov, 06:31 UTC17d 22h
  4. WPT 4Mon 30 Nov, 06:31 UTC31d 22h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 10hFW

The first 48 hours of its last wipes

Mon 19 OctSun 11 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 7 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 06:31 UTC10d ago 2 – running 0
Sun 11 Oct, 12:42 UTC17d ago 1 halved by day 2 7.7 days 0
Sun 4 Oct, 10:47 UTC24d ago 1 halved by day 1 7.1 days 0
Thu 1 Oct, 17:41 UTC FW27d ago 1 halved by day 1 2.7 days 1
Sun 27 Sep, 05:11 UTC32d ago 1 held half 4.5 days 0
Sat 26 Sep, 05:07 UTC33d ago 2 – 1 days 0
Sat 19 Sep, 06:13 UTC40d ago 0 – 7 days 0
Wed 16 Sep, 04:16 UTC43d ago 1 halved by day 2 3.1 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 timing

What should you expect from wipe day on BURN ZOMBIE TESTSERVER?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 7 hours. The crowd stayed above half that peak until the next wipe in 25% of its recent wipes. When it didn't hold, by day 1 it fell below half.

How often does BURN ZOMBIE TESTSERVER wipe, and when?

The prediction follows its tag, because too few of BURN ZOMBIE TESTSERVER's wipes are on record to confirm its schedule. On Monday 2 November at 06:31 UTC its next wipe is due. The world it runs now was made 10 days 1 hours ago. A wipe schedule of every two weeks is published in its tags.

Tag meanings

How should you read the tags on BURN ZOMBIE TESTSERVER?

Tags published by BURN ZOMBIE TESTSERVER, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp80 (Max players): 80 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does BURN ZOMBIE TESTSERVER appear in Rust Metrics lists and filters?

On Rust Metrics, BURN ZOMBIE TESTSERVER sits in these lists: Modded Rust servers, checked live, Rust PvE servers and Rust servers: zombie readings. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

What position does BURN ZOMBIE TESTSERVER hold among Rust servers?

Ranking for BURN ZOMBIE TESTSERVER: #15,338 on seven-day player hours, top 69% of all ranked servers.

What player count does BURN ZOMBIE TESTSERVER carry?

0 of 80 slots are filled on BURN ZOMBIE TESTSERVER right now. Check: player average. 0 over the last seven days.

Server details

What location is BURN ZOMBIE TESTSERVER hosted in?

No region tag on BURN ZOMBIE TESTSERVER. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 136.243.93.153:29025.

What Rust version is BURN ZOMBIE TESTSERVER on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by BURN ZOMBIE TESTSERVER. To get in, your game needs the same protocol; Steam applies the update.

Is performance on BURN ZOMBIE TESTSERVER within range?

Over the last 48 hours the average was 32 server fps; the floor was 23. Check: entities. The peak was 78,693, counting buildings, deployables and the rest of the world. Memory peak: 6,815 MB. What players call lag comes from low fps and an entity count on the rise.

Is BURN ZOMBIE TESTSERVER up, and how often does it stay up?

BURN ZOMBIE TESTSERVER reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 21 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

How is BURN ZOMBIE TESTSERVER configured, and what rules are in force?

No gather rate appears in the name: BURN ZOMBIE TESTSERVER. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on BURN ZOMBIE TESTSERVER?

Size 5,250 and seed 1337: the game generates the procedural map on BURN ZOMBIE TESTSERVER from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Last Oasis.

How to join

How do you connect to BURN ZOMBIE TESTSERVER?

To join: start Rust, press F1 and type client.connect 136.243.93.153:29025. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://rust-burn.com/.

PLACARDS

Server tags

what each one means

Published as mp80,ptrak,$r?,v2635,^b,^p,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp80
Max players 80 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.