Fig. 1Players on BURN ZOMBIE TESTSERVERRG-S15383-01 · Sheet 1 of 11
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S15383-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S15383-03 · Sheet 3 of 11
Schedule
Wipe schedule
from its schedule tag
Next wipe Monday 2 November, 06:31 UTC, in 5d 11h.
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
5d 11hMon 2 Nov, 06:31 UTC
8d 23hThu 5 Nov, 19:00 UTCFW
19d 11hMon 16 Nov, 06:31 UTC
33d 11hMon 30 Nov, 06:31 UTC
36d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Mon 19 OctSun 11 OctSun 4 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 7 hours in.
ScheduleExpected wipesRG-S15383-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 06:31 UTC8d ago
2
–
running
0
Sun 11 Oct, 12:42 UTC16d ago
1
halved by day 2
7.7 days
0
Sun 4 Oct, 10:47 UTC23d ago
1
halved by day 1
7.1 days
0
Thu 1 Oct, 17:41 UTCFW26d ago
1
halved by day 1
2.7 days
1
Sun 27 Sep, 05:11 UTC30d ago
1
held half
4.5 days
0
Sat 26 Sep, 05:07 UTC31d ago
2
–
1 days
0
Sat 19 Sep, 06:13 UTC38d ago
0
–
7 days
0
Wed 16 Sep, 04:16 UTC41d 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.
Table 1Wipe logRG-S15383-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is BURN ZOMBIE TESTSERVER online, and what uptime has been recorded?
Right now, BURN ZOMBIE TESTSERVER is recorded as online. About 8 days 9 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.
2.
Is BURN ZOMBIE TESTSERVER stable in the figures recorded?
The last 48 hours give an average of 31 server fps and a floor of 18. Counted at its highest: 75,553 entities, buildings, deployables and the rest of the world included. Memory use peaked at 6,723 MB. What players feel as lag is low fps together with a climbing entity count.
3.
What location is recorded for BURN ZOMBIE TESTSERVER?
A region is not published by BURN ZOMBIE TESTSERVER. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 136.243.93.153:29025.
4.
What Rust version is recorded for BURN ZOMBIE TESTSERVER?
On Linux, BURN ZOMBIE TESTSERVER runs Rust network protocol 2634 and build 167398. To join, your game must be on the same protocol; Steam handles the update.
Population
5.
How many players are plotted on BURN ZOMBIE TESTSERVER?
0 of 80 slots on BURN ZOMBIE TESTSERVER are taken at the latest refresh. The seven-day mean on this server is 0 players.
6.
What rank has been recorded for BURN ZOMBIE TESTSERVER?
Within the top 70% of all ranked servers: BURN ZOMBIE TESTSERVER at #15,383 for player hours, seven days recorded.
Wipe times
7.
What is recorded on BURN ZOMBIE TESTSERVER on wipe day?
The recent wipes averaged a busiest count of 1 players. At 7 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 25% of its recent wipes. In the other cases the crowd was below half by day 1.
8.
On BURN ZOMBIE TESTSERVER, when do wipes occur?
The prediction follows its tag, because too few wipes of BURN ZOMBIE TESTSERVER are on record to confirm the schedule. On Monday 2 November at 06:31 UTC its next wipe is due. 8 days 11 hours ago the current world was made. Its tags give a wipe schedule of one wipe every two weeks.
Settings
9.
What settings and rules apply on BURN ZOMBIE TESTSERVER?
The name of BURN ZOMBIE TESTSERVER records no gather rate. The group limit is 8 players, the game's default. pve, no fighting other players, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.
10.
On which map is BURN ZOMBIE TESTSERVER played?
Seed 1337 and size 5,250 define the procedural map BURN ZOMBIE TESTSERVER generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Last Oasis.
Tags
11.
Where does BURN ZOMBIE TESTSERVER appear among the Rust Graphs lists and filters?
These Rust Graphs lists include BURN ZOMBIE TESTSERVER: Modded Rust servers, PvE Rust servers, plotted and Rust zombie servers, plotted. On the server list, these filters bring it up: 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.
12.
On BURN ZOMBIE TESTSERVER, what is meant by each tag?
The game's server browser reads these tags from BURN ZOMBIE TESTSERVER: gmvanilla (Game mode): The mode is vanilla survival; mp80 (Max players): Slots: 80; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
13.
What is the way to connect to BURN ZOMBIE TESTSERVER?
In Rust, press F1 and type client.connect 136.243.93.153:29025 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://rust-burn.com/.
NotesAnswered from the figuresRG-S15383-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp80,ptrak,$r?,v2634,^b,^p,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
Game modeThe mode is vanilla survival.
mp80
Max playersSlots: 80.
ts8
Group limitTeams are capped at 8, the default setting.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^p
PvEThe world is the danger; players do not fight each other.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is 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.
KeyTag string decodedRG-S15383-11 · Sheet 11 of 11
