Gundam Wikia

GF4-001NE Pharaoh Gundam IV

6,521pages on
this wiki
Add New Page
Talk0 Share

The GF4-001NE Pharaoh Gundam IV, (Mummy Gundam IV in the English dub) was a Mobile Fighter entered in the 4th Gundam Fight by Neo Egypt. It appears in Mobile Fighter G Gundam.

Technology & Combat Characteristics

The Pharaoh Gundam is designed to use it's whips to drag an opponent into a close ranged fight and finish the fight using its cannon and mummy cloth.


  • Mamba Whip
  • Vulcan Gun
  • Eye Cannon
  • Chest Cannon
  • Mummy Cloth


Neo Egypt's GF4-001NE Pharaoh Gundam IV was piloted by Dahal Muhammad, who was the winner of the 3rd Gundam Fight in FC 16. Dahal returned to the 4th Gundam Fight in FC 20 to represent his nation, but something went terribly wrong. During the Finals, Dahal was accidentally killed in a battle with Neo China's Sai Feilong and his GF4-005NC Feilong Gundam. More than 40 years later, Dahal's mummified corpse was resurrected by the JDG-00X Devil Gundam and was given its power of self-regeneration. The resurrected Dahal went on a rampage and destroyed his country's new Gundam, the GF13-051NE Pharaoh Gundam XIII. Afterwards, Dahal continuously attacked Neo China's Sai Saici and his GF13-011NC Dragon Gundam. Since Sai Saici was the grandson of Shaolin master Sai Feilong, Dahal's spirit wanted a second chance to fight. His resurrected Pharaoh Gundam IV was quite a match for the modern suits of the 13th Gundam Fight. Aside from the standard head vulcans and two mamba whips, the Pharaoh Gundam IV was also equipped with two eye cannons and a chest cannon. Also, its mummy cloth could be used to grab opponents and render them helpless. Since Dahal and his Gundam possessed the ability of self-regeneration, it took a Shining Finger from Domon Kasshu's GF13-017NJ Shining Gundam to finally put the ancient warrior to rest.

External links

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.