Online 136.243.93.153:29025 checked 22m ago
BURN ZOMBIE TESTSERVER
Connect
srv = rust.server("136.243.93.153:29027")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Monday 2 November, 06:31 UTC, in 4d 20h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 4d 20h | Mon 2 Nov, 06:31 UTC | wipe |
| 1 | 8d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 18d 20h | Mon 16 Nov, 06:31 UTC | wipe |
| 3 | 32d 20h | Mon 30 Nov, 06:31 UTC | wipe |
| 4 | 36d 9h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 7 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 06:31 UTC9d ago | 2 | NaN | running | 0 |
| 1 | Sun 11 Oct, 12:42 UTC16d ago | 1 | halved by day 2 | 7.7 days | 0 |
| 2 | Sun 4 Oct, 10:47 UTC23d ago | 1 | halved by day 1 | 7.1 days | 0 |
| 3 | Thu 1 Oct, 17:41 UTC FW26d ago | 1 | halved by day 1 | 2.7 days | 1 |
| 4 | Sun 27 Sep, 05:11 UTC31d ago | 1 | held half | 4.5 days | 0 |
| 5 | Sat 26 Sep, 05:07 UTC32d ago | 2 | NaN | 1 days | 0 |
| 6 | Sat 19 Sep, 06:13 UTC39d ago | 0 | NaN | 7 days | 0 |
| 7 | 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 246 on average | 94/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 236 on average | 166/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 100 on average | 34/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 59 on average | 83/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 53 on average | 41/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 51 on average | 11/250 |
Quick answers
From the figures on this page.
Population data
What position does BURN ZOMBIE TESTSERVER take in the server rankings?
Player hours over seven days put BURN ZOMBIE TESTSERVER at #15,396, in the top 69% of the ranked set.
How full does BURN ZOMBIE TESTSERVER run?
Current row: 0 players on BURN ZOMBIE TESTSERVER, against 80 slots. Over the last seven days it averaged 0 players.
About the server
How well does BURN ZOMBIE TESTSERVER perform?
The 48-hour average is 31 server fps, with a low of 18. The entity count peaked at 76,143, covering buildings, deployables and the rest of the world. A high of 6,815 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on BURN ZOMBIE TESTSERVER?
Rust network protocol 2634 and build 167398 on Linux is what BURN ZOMBIE TESTSERVER runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is BURN ZOMBIE TESTSERVER, and is it online now?
The current sample puts BURN ZOMBIE TESTSERVER online. A restart about 9 days ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.
In which location is BURN ZOMBIE TESTSERVER hosted?
No region is published by BURN ZOMBIE TESTSERVER. Rust Data does not look up where the machine stands; it shows where a server says it is. 136.243.93.153:29025 is its address.
Rules, settings, map
Which settings and rules does BURN ZOMBIE TESTSERVER run?
You will not find a gather rate in the string BURN ZOMBIE TESTSERVER. Eight players per group: that is the game's default, and it applies here. pve is the game mode here, and no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has BURN ZOMBIE TESTSERVER selected?
BURN ZOMBIE TESTSERVER runs a procedural map of size 5,250 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Last Oasis.
Wipe schedule
When does BURN ZOMBIE TESTSERVER wipe, and how often?
The prediction follows the tag, because BURN ZOMBIE TESTSERVER's wipes on record are too few to confirm the schedule. On Monday 2 November at 06:31 UTC the next wipe is due. The world it runs now was generated 9 days 2 hours ago. The tags list a two-weekly wipe cycle.
On BURN ZOMBIE TESTSERVER, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 7 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 25% of recent wipes. The drop under half arrived by day 1 in the other cases.
Tags and filters
Which Rust Data filters and lists contain BURN ZOMBIE TESTSERVER?
These Rust Data lists include BURN ZOMBIE TESTSERVER: Modded Rust servers, Rust PvE servers and Rust servers named for the undead. Under these filters on the server list, it is listed: 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.
How should you read the server tags on BURN ZOMBIE TESTSERVER?
Read by the game's server browser, the tags BURN ZOMBIE TESTSERVER publishes are: gmvanilla (Game mode): Survival in vanilla form; mp80 (Max players): 80 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into BURN ZOMBIE TESTSERVER?
Enter client.connect 136.243.93.153:29025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://rust-burn.com/.
