FANDOM


  • In episode 120, Gozaburo Kaiba uses this card during his Duel against his stepson Seto Kaiba. He summons this card via "Contract with Exodia". This card then attacks Kaiba's "Vorse Raider", but this card's effect prevented it from being destroyed. At the end of the Damage Step, this card gain 1000 ATK. Kaiba then tried to destroy this card with "Burst Breath" by Tributing his "Spirit Ryu", but this fails as "Exodia Necross" can't be destroyed by Spells and Traps. In the next episode, this card attacks "Vorse Raider", but Kaiba activates "Negate Attack" to negate the attack and end the Battle Phase. Kaiba then activates "Shrink" to halve this card's ATK until the End Phase. He then Tributes his "Vorse Raider" to summon "Luster Dragon 2". "Luster Dragon 2" then attacks this monster. This card was not destroyed due to its effect, but Gozaburo still take Battle Damage. This card then gained 1000 ATK at the end of the Damage Step. At the End Phase, "Shrink"'s effect expired. This card then attacks and destroys "Luster Dragon 2". This card then gained 1000 ATK at the end of the Damage Step. On Gozaburo's next turn, this card attacks and destroys Kaiba's set "Ancient Lamp". This card then gained 1000 more ATK at the end of the Damage Step. After Kaiba revives "Ancient Lamp" via "Monster Reborn", he uses the effect of "Ancient Lamp" to Summon "La Jinn the Mystical Genie of the Lamp". This allowed Kaiba to activate "Soul Demolition". Kaiba then uses the effect of "Soul Demolition" five times to banish the five Exodia pieces in Gozaburo's Graveyard. Because of this, this card lost all of its destruction immunity effects and its ATK decreased to its original value. "Blue-Eyes White Dragon" then attacks and destroys this card, winning Kaiba the duel.
  • In the original Japanese version, this card's attack name is Exodia Crush.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.