TARDIS Index File

Abslom Daak... Dalek Killer (comic story)

58,927articles in progress
Add New Page
Talk0 Share
Abslom Daak... Dalek Killer
Daak Dalek Killer Taiyin is Dead
Main character(s): Abslom Daak
Featuring: Taiyin
Main enemy: Daleks
Main setting: Earth and Mazam
Key crew
Publisher: Marvel Comics
Editor: Dez Skinn
Writer: Steve Moore
Artist: Steve Dillon
Release details
Printed in: Doctor Who Weekly 17-20
Release date: 6-27 February 1980
Format: B&W 4 parts / 16 pages
←Previous Next→
DWM backup comic stories
Deathworld Twilight of the Silurians

Abslom Daak... Dalek Killer was a backup comic story published in Doctor Who Weekly Issues 17-20.

Summary Edit

Hardened criminal Abslom Daak chooses a suicide mission as a Dalek Killer as an alternative to vapourisation. Daak survives transmission through space and arrives on the newly-colonised Dalek world of Mazam where the puppet ruler, Princess Taiyin, is about to be exterminated by her masters. Daak rescues her and together they make their escape from the palace and launch an attack on the Dalek base nearby. The attack is successful, but a stray Dalek survivor manages to kill Taiyin while Daak holds her in his arm. Half-crazed with grief, Daak swears to revenge himself on "every damned stinking Dalek in the galaxy!"

Plot Edit

to be added

Characters Edit

References Edit

  • Mazam is a planet occupied by the Daleks.

Notes Edit

  • This back-up strip is introduced by the Fourth Doctor.
  • Part Four is wrongly captioned as Part Three in DWM 20

Original print details Edit

Publication with page count and closing captions
  1. DWM 17 (4) End of Episode One.
  2. DWM 18 (4) End of Episode Two.
  3. DWM 19 (4) End of Instalment 3.
  4. DWM 20 (4) Next Week: Twilight of the Silurians!

Reprints Edit

Continuity Edit

to be added

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.