AION 2 Ludra Normal Mode: Under 2% of Week-One Runs End in a Ludra Kill
NC says Normal Abyssal Forge: Ludra lets players keep progressing without Hard. In 2,404 Global Normal runs tracked by the AionFlex meter in the first week, 55% never got past Rahu or Ketu and only 44 runs (1.8%) ended in a recorded Ludra kill.
Last updated: November 10, 2026
What NC said Normal mode is for
Abyssal Forge: Ludra opened on the Global servers with the November 4 update, in Normal (item level 2,800) and Hard (item level 3,000), each run with a 1-hour time limit. In the official patch notes, NC describes Hard as content "designed for top-tier players" and presents Normal as the way everyone else keeps up:
"Players can continue progressing and earning rewards even without clearing Hard difficulty, as Normal difficulty also offers the same types of item rewards as Hard difficulty."
The same notes add a warning about the entry requirement:
"The minimum entry item level is only a requirement for entering the content and does not guarantee a successful clear."
Normal is therefore meant to be the progression path for most players. Here is how that path looked in its first week. Background on the launch is in our post on Ludra's November 4 return.
Where the data comes from
The figures below come from AionFlex, the AION 2 damage meter. When a boss dies, the meter uploads the fight and records how many times that boss was reset during the same instance visit before the kill. We counted every Abyssal Forge: Ludra fight on the Global servers uploaded between the November 4 maintenance and November 10, 02:35 UTC: 4,343 uploads. When several members of one party ran the meter, their copies of the same fight are counted once.
Every run starts with the Central Abyss Fusion Reactor. The party then fights either Isolation Specialist Rahu or Abyssal Wings Ketu, and Eternal Ludra comes last. That order is what lets us see how far each run got.
How far Normal runs got
We tracked 2,404 Normal runs and 55 Hard runs from the Reactor kill onward:
| Outcome | Normal runs | Hard runs |
|---|---|---|
| Stopped after the Reactor (no Rahu or Ketu kill) | 1,335 (55.5%) | 36 (65%) |
| Killed Rahu or Ketu, no Ludra kill recorded | 1,025 (42.6%) | 15 (27%) |
| Killed Eternal Ludra | 44 (1.8%) | 4 (7%) |
| Total | 2,404 | 55 |
More than half of all Normal runs never killed the second boss. Of the runs that did, about 1 in 24 went on to record a Ludra kill. In total the meter recorded 54 Normal Ludra kills; the 10 not in the table came from runs where the Reactor kill was not uploaded (usually the meter was started late), so they cannot be placed in a run.
Boss by boss: tries and kills
A try here is a kill plus every reset the meter saw before it in the same instance visit (a reset is a wipe or a leash: the boss back at full health).
| Boss | Mode | Tries | Kills | Kills per try |
|---|---|---|---|---|
| Central Abyss Fusion Reactor | Normal | 2,405 | 2,404 | ~100% |
| Isolation Specialist Rahu | Normal | 2,149 | 730 | 34% |
| Abyssal Wings Ketu | Normal | 1,398 | 621 | 44% |
| Eternal Ludra | Normal | 137 | 54 | 39% |
| Central Abyss Fusion Reactor | Hard | 56 | 55 | 98% |
| Isolation Specialist Rahu | Hard | 19 | 12 | 63% |
| Abyssal Wings Ketu | Hard | 34 | 22 | 65% |
| Eternal Ludra | Hard | 8 | 7 | 88% |
Rahu is the hardest boss before Ludra on Normal: 1,419 resets for 730 kills, about two failed pulls for every success. These rates count only pulls that eventually led to a kill. Pulls by groups that gave up are never uploaded, so the true success rate per pull is lower than shown. The Hard figures are small samples from the first few days.
Players, not runs
Most players run the dungeon more than once, so the share of players with a clear is higher than the share of runs. About 10,200 different character names appear in the party lists of Normal Reactor kills, and about 361 of them were in a party that recorded a Normal Ludra kill: roughly 3.5%. This is an approximation, because names are unique only per server.
It is not mainly the 1-hour timer
It is natural to blame the time limit, but the timings do not support that for most runs. Runs that killed Rahu or Ketu but recorded no Ludra kill finished that second boss a median of 17 minutes after pulling the Reactor, so most of them still had more than half the hour left. The 44 runs that killed Ludra did so a median of 45 minutes after the Reactor pull. Most runs end either at the second boss or at Ludra itself, not because the clock ran out on the way.
What this data can and cannot show
- Only kills are uploaded. A run with no further kill could mean the group wiped until it gave up, left on purpose (for example after collecting the second boss's loot), or ran out of time. The data cannot tell these apart.
- Some Ludra kills may be missing. The meter recognises a kill by a zero-health reading, or else by at least 90% of the boss's health bar dealt. For Ludra, 26 of the 57 Normal kill uploads (and 6 of 7 on Hard) were recognised only by the 90% rule, against 1 to 4% for the other bosses. A kill that meets neither rule is never uploaded, so the real Ludra clear rate may be somewhat higher than 1.8%.
- Runs are rebuilt from each player's consecutive kills, because the meter does not record when an instance starts or ends. Changing the rules (60, 90 or 120 minutes between runs; how many party members must match) moves the Normal figures by under one percentage point: 55.0 to 56.4% stopped at the second boss, 1.7 to 1.9% killed Ludra.
- The sample is AionFlex users, who tend to be more engaged players. The wider player base is unlikely to do better.
- Global servers only. Korea and Taiwan have had Ludra for months, and most of their uploads come from meter versions that do not record resets.
Our take
NC sells Normal as the mode that lets you "continue progressing" without Hard. The first week says otherwise. A Normal mode that does its job should see something like 30 to 40% of runs end in a kill. Ludra Normal managed 1.8%, roughly twenty times short of that, and more than half of all runs never got past the second boss.
Missed kills do not explain it. Even if the meter missed as many Ludra kills as it recorded, the clear rate would still be under 4%. Nor does the timer: the groups that beat Rahu or Ketu did it with most of the hour still left. Rahu costs about two wipes for every kill, and of the runs that got past the second boss, about 96% never recorded a Ludra kill.
This is not an on-ramp. It is a Hard-mode wall with a Normal label on it. NC's own notes warn that the entry item level "does not guarantee a successful clear"; at 1.8%, it barely makes one possible. If Normal is supposed to carry the players who will never run Hard, it needs tuning now, not after weeks of failed runs.
Week one always runs harder than later weeks, as gear improves and groups learn the mechanics. We will re-run these numbers in the coming weeks and update this page, including if NC adjusts the dungeon.
Sources
Frequently asked questions
How many AION 2 Ludra Normal runs end in a Ludra kill?
Of 2,404 Global Normal runs tracked by the AionFlex meter from November 4 to November 10, 2026, 44 (1.8%) ended with a recorded Eternal Ludra kill. 55.5% never killed Rahu or Ketu, and 42.6% killed one of them but recorded no Ludra kill.
Which Ludra boss wipes groups the most?
Isolation Specialist Rahu on Normal: 1,419 resets for 730 kills, about two failed pulls per kill. Abyssal Wings Ketu follows at 777 resets for 621 kills.
What did NC say about Normal and Hard Ludra?
The November 4 patch notes say players "can continue progressing and earning rewards even without clearing Hard difficulty, as Normal difficulty also offers the same types of item rewards as Hard difficulty", with different drop rates. Normal needs item level 2,800 and Hard 3,000, each run has a 1-hour limit, and the entry level "does not guarantee a successful clear".
Is the 1-hour time limit the reason runs fail?
Mostly not. Runs that killed the second boss but recorded no Ludra kill did so a median of 17 minutes after pulling the first boss, so they had most of the hour left.