On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 800% full
7-day average0peak –
Rank#15,419top 69%
Last wipe8d agobiweekly schedule
Next wipe4d 23hMon 2 Nov, 06:31 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 80 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,419 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
52/ 100
D
Slows down under load at times: 31 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 1,812 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W··W·
·····WW
···F··W
······W
·······
W······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Monday 2 November, 06:31 UTC, in 4d 23h.
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
4d 23hMon 2 Nov, 06:31 UTC
8d 12hThu 5 Nov, 19:00 UTCFW
18d 23hMon 16 Nov, 06:31 UTC
32d 23hMon 30 Nov, 06:31 UTC
36d 12hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Mon 19 OctSun 11 OctSun 4 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 7 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 06:31 UTC9d 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 UTC31d ago
1
✓ held half
4.5 days
0
Sat 26 Sep, 05:07 UTC32d ago
2
–
1 days
0
Sat 19 Sep, 06:13 UTC39d ago
0
–
7 days
0
Wed 16 Sep, 04:16 UTC42d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
BURN ZOMBIE TESTSERVER leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 136.243.93.153:29025.
How reliable is BURN ZOMBIE TESTSERVER, and is it up?
Right now, BURN ZOMBIE TESTSERVER is online. About 8 days 21 hours ago, it restarted, based on the uptime it reports. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does BURN ZOMBIE TESTSERVER perform well?
It averaged 31 server fps over the last 48 hours, with a low of 18. Up to 76,143 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 6,815 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is BURN ZOMBIE TESTSERVER running?
You will find BURN ZOMBIE TESTSERVER on Rust network protocol 2634 and build 167398, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does BURN ZOMBIE TESTSERVER reset?
The prediction follows its tag, because too few of BURN ZOMBIE TESTSERVER's wipes are on record to confirm the schedule. Monday 2 November at 06:31 UTC is the date set for its next wipe. It has been running its current world for 8 days 23 hours. Its tags give a wipe schedule of every two weeks.
What happens on BURN ZOMBIE TESTSERVER when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 7 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 25% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does BURN ZOMBIE TESTSERVER place in the wider field of Rust servers?
In the top 69% of all ranked servers, BURN ZOMBIE TESTSERVER sits at #15,419 for player hours over the last seven days.
How many players does BURN ZOMBIE TESTSERVER usually have?
With 80 slots available, BURN ZOMBIE TESTSERVER currently has 0 players. Over the past seven days, the average player count was 0.
Tags and filters
How should you read the tags on BURN ZOMBIE TESTSERVER?
The game's browser takes its cue from the tags BURN ZOMBIE TESTSERVER has set: gmvanilla (Game mode): You play vanilla survival here; mp80 (Max players): The server holds 80 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature BURN ZOMBIE TESTSERVER?
These Rust Server Score lists count BURN ZOMBIE TESTSERVER among them: Modded Rust servers, graded, Rust PvE servers, graded and Rust zombie servers, graded. You can find it under these server-list filters: 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.
Map and rules
How is BURN ZOMBIE TESTSERVER set up, and what rules does it keep?
Nothing in the name of BURN ZOMBIE TESTSERVER states a gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map BURN ZOMBIE TESTSERVER uses?
The game generates the procedural map on BURN ZOMBIE TESTSERVER at size 5,250 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Last Oasis.
Connecting
How do you get onto BURN ZOMBIE TESTSERVER?
To connect, start Rust, press F1, and type client.connect 136.243.93.153:29025. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://rust-burn.com/.
Server tags
what each one means
Published asmp80,ptrak,$r?,v2634,^b,^p,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp80
Max playersThe server holds 80 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).