Nanatsu no Taizai Wiki

Episode 8

902pages on
this wiki
Add New Page
Comment1 Share
The Fearsome Pursuer
Title | Screenshots | Eyecatch | Endcard

Episode 8 Title

Kanji/Kana 恐るべき追跡者
Rōmaji Osorubeki Tsuiseki-sha
Air Date November 23, 2014
Chapter(s) 21, 22, 23, 24, SS1
Story Arc Capital of the Dead arc
Opening Theme Netsujō no Spectrum
Ending Theme 7 -seven-
Episode Credits
Episode Director Ken'ichi Imaizumi
Screenplay Shoutarou Suga
Storyboard Ken'ichi Imaizumi
Animation Director Yuuichi Terada
Kiminori Itou
Episode 7 Episode 9
Episode 8 Screenshots

The Fearsome Pursuer恐るべき追跡者 Osorubeki Tsuiseki-sha」 is the 8th episode of The Seven Deadly Sins anime series.


The mysterious Holy Knight, is revealed to be Guila, who threatens the kids and succeeds in gaining entry to the Capital of the Dead. Meanwhile, inside the Capital of the Dead, King petrifies Ban in an act of revenge for his sister, Elaine. However the spirit of Elaine chooses to reverse the petrification, much to the surprise of King. Here, Ban and Elaine's pasts are explored.

Whilst looking for Ban and King, the two now split from the rest of the group to chase after Elaine, Meliodas and the others have a run-in with Guila. The battle begins between Meliodas and Diane fighting against Guila, however tremors from the battle with Guila reach where Ban and King are, forcing Ban to join the fight against Guila. Left alone with his sister now, King listens to her plea to help Ban, and switches sides. With that done, King leaves to help out the other Sins, who are still struggling (even with the arrival of Ban) in defeating Guila.


Characters In Order of Appearance

Manga & Anime Differences


Capital of the Dead arc
Fights and Events
Meliodas vs. OsloBan vs. King (Part 1)Ban vs. King (Part 2)Meliodas, Diane & Ban vs. GuilaKing vs. Guila

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.