FANDOM


Unknown-1
This article, Megakame, is still being created. The author apologizes for the inconvenience.


Megakame was a category VI Kaiju that was known for its unique turtle- like appearence and its ability to curl up into a protective, yet destructive ball.


Megakame
http://3.bp.blogspot.com/_2ywfUIjQQs0/S-yILFksi-I/AAAAAAAADyU/vXNo-bBnOMw/s1600/75_Ton_Creature_by_VegasMike.jpg
Technical Information
Kaiju Species Protective turtle
Breach Date 09/27/19
Category Category VI
Status Unknown
Origin He came from the breach and was resurrected by kaiju cults
Kaiju Specifications
Height 250 ft
Weight 27,000 tons
Speed Very slow
Strength Medium
Armor Very high
Battle Information
Attack Behavior sluggish, yet he can land a very deadly blow if caught ungaurded.
Toxicity Almost none
Powers Medium high
Weaknesses Underbelly, armpits.
Target Information
City Targeted New Orleans
Jaegers Targeted
or Destroyed
Chrome Brutus

HistoryEdit

First Kaiju war

 Megakame was one of the heaviest Kaiju to ever make land in the Kaiju war. It stood up on its two hind legs, however, it would occasionaly get down on all fours to headbutt, bite a Jaeger's leg, or to protect itself. It was one of the largest Kaiju ever recorded.

Second Kaiju war

Megakame was resurected like how most Kaiju where, but was destroyed quickly after by Chrome Brutus.

BiologyEdit

Megakame's shell was made up of very durable and hardy keratin. It covered his sides, back and tail. His arms, legs, and forehead was covered with scales made up of less hard and durable keratin. His weak underbelly was a critical area to be injured in, and death was near certain if it was injured to badly. His chin was also a weak area, but it was harder to target and hit. long claws and teeth could rip through Jeager armor like a tin can. Its four eyes help it prevent incoming Jeager attacks.

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.