Fandom

Warhammer 40,000 Wiki

Grashkar Gitface

1,117pages on
this wiki
Add New Page
Talk0 Share
This article, Grashkar Gitface, was written by Jed Revenant man. Please do not edit this article without their explicit permission.
TemplateCog
This article, Grashkar Gitface, is still being written. The author, Jed Revenant man, apologises for the inconvenience.
TemplateCog

Grashkar Gitface was an Ork Warlord in the 41st Millenium who held a small Empire in the Ragnarok system.

Gitface was so named because, prior to ascending to being a Warlord, he was the servant of a Warlord whose name has been unrecorded, who referred to him as "Gitface" for the entirety of their association (i.e: "oi! Gitface!"), until Grashkar killed him, and reclaimed the title for himself. Whether he did this as an act of respect for his former master or hatred of him, no one knows.

He then, after securing the loyalty of his former master's Orks (mainly through judicious - as well as gratuitous - use of stomping, shooting and hacking), led his Orks to claim the worlds of the Ragnarok system (a system near the Eastern Fringe - most Imperial Analysts believe it belonged to the Tau prior to the Orks arival), and carved himself an empire, dominating it with an iron fist.

Once there, he lauched raids at the nearby Imperial Worlds. He became known first as a minor pest, then a major problem, until finally Imperial authorities could take no more of his presence and decided to act. At the High Lord's behest, elements of the Revenants Chapter and three regiments of Imperial Guard were sent to destroy the Empire of Ragnarok. During the final assault, Grashkar, holed up in his palace, fought Yan Rill of the Revenants in single combat; though the Ork was a powerful warrior, fate was with Rill, who broke the Ork Warlord and hurled him from a balcony. With his death, his Orks scattered.

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.