Official metadata checked · Sep 19 · Gameplay captured Sep 14Place ID 105011592530400 · Fan-made, independent
Independent data lab

Zombie & wave database

Map enemy health, incoming damage, first wave, wave scaling and cash rewards without turning estimates into facts.

Current answerOfficial badge wording names King 1x1x1x1 as a Hacker Event boss. Health, damage, spawn wave and current event access are not verified.

Wave data becomes reliable only when weapon damage, kill counts, vehicle durability and server version are controlled together. This table stores the fields needed to reproduce a result.

Public records: 1 · Field-level coverage

One boss name is supported by official badge wording. Its combat stats and current availability remain unknown.

Zombie & wave database table

Evidence tracked
Zombie / waveEnemy typeHealthDamageFirst waveEvidence / dateActions
King 1x1x1x1Hacker Event bossUnknownUnknownUnknownPublic evidence

Official badge title confirms the name; its description calls this the Hacker Event Great Boss. Badge metadata does not prove current event access, health, damage or spawn wave.

Capture ↗ · 2026-09-14
Read-only public record

Add a private field observation

Leave unmeasured values empty. Cash cost is not a Robux price or an estimated roll cost. Enter 1 average target only when intentionally comparing one-target damage.

JSON imports add private records only. They do not verify or publish a source claim.

Verification schema

A value enters the public table only when evidence proves that exact field. A screenshot of a name and price does not prove sustained DPS or an unlimited mount count.

FieldRequired evidenceAccepted state
Enemy nameReadable label or official update noteObserved
HealthControlled hits-to-kill multiplied by verified damageObserved
Vehicle damageBefore/after durability in a controlled hitObserved
First waveContinuous recording from wave counter to spawnObserved
Cash rewardVisible cash delta with bonuses documentedObserved

How to measure

  1. Start from a clean runRecord current cash, vehicle health, buffs and wave before testing.
  2. Use a known weaponHealth estimates inherit the uncertainty of the weapon damage value.
  3. Count one interactionSeparate contact damage, attack frequency and number of surviving zombies.
  4. Repeat across serversA result becomes strong only when it survives version and server variation.