Enemy HP Quick Reference

You are not fighting a spreadsheet, you are fighting a route-specific room pool

This page exists so you can stop treating enemy stats like floating trivia. 97 entries only become useful once they are anchored to act, area, tier, and pressure profile. Otherwise you memorize a number, walk into the wrong route variant, and die with a perfectly organized mistake.

That is why the page leads with route context and area filters instead of dumping raw HP alone. Hallway planning, elite routing, and burst math all depend on what can actually spawn where you are going, not on one remembered enemy portrait from somewhere else.

The data is grouped by real appearances, not by vague enemy reputation

Each entry is tied back to its known appearances, area membership, HP ranges, ascension HP ranges, move titles, attack pattern summaries, and pressure tags in the current enemy dataset. That gives the page enough structure to answer practical route questions without pretending to be a full combat simulator.

The verification line is intentionally narrow. This database tells you where the enemy appears, how much HP it carries, and what pressure shape it presents. If you need exact room totals for elite and boss encounters, the site sends you to the dedicated HP lookup instead of overloading this page with a second job.

• Area filters are built from the live appearance map.
• Danger labels summarize route pressure rather than inventing hidden combat formulas.
• Attack profile pills expose broad hit patterns, not a full turn-order script.

Route area, pressure tags, and hit profile are the fast answers

The most useful read on this page is usually not the exact HP line. It is whether the enemy even belongs to the route you are considering, whether the danger tag points to burst, scaling, summon pressure, or utility, and whether the attack profile punishes slow setup or weak front-load.

The appearance list matters for the same reason. It tells you when an enemy is a true route concern and when it is only a theoretical possibility. That keeps planning grounded instead of making every scary entry feel equally urgent all the time.

• Filter route first, then tier, then danger if you want a usable slice.
• Use pressure tags to see what kind of answer the room demands.
• Read multi-hit and peak-single lines differently, because block math and Doom math care about different pressure shapes.

Most enemy lookups fail because the user asks the wrong question

The classic mistake is searching an enemy by name, finding a clean HP range, and forgetting that the route or area filter was the real missing piece. That leads to planning around enemies that do not actually show up on the path you are walking.

The next mistake is treating the danger badge like destiny. It is only a pressure summary. A high-danger enemy can still be trivial for the current deck, while a medium tag can be a disaster if your shell is weak to that specific attack pattern or timing window.

• Do not read HP without reading appearances.
• Do not use one danger badge as a substitute for understanding the pressure tags.
• Do not expect this page to replace encounter-total math for elite and boss rooms.

Use the stronger planning page when the lookup becomes a real combat question

These pages take over once you know which enemy or room matters. The database gives you the identity. The pages below handle the threshold math and run-planning questions built on top of it.