FANDOM


Umigaron
Umigaron
Used by
Gallibon
Allies
Tsutabara (master)
Yamalgon, Muchi
Enemies
Kamen Rider Agito, Sailor Fighter, Earth Warrior Zeros
Species
Shark Monster
Age
Not known
Height
35 meters
Length
None
Faction
None
Category
Sailor Fight! Character

Umigaron (海怪獣ウミグロン, Sea Monster Umigaron) is a shark monster and a RP character used by Gallibon the Destroyer.

Personality

Umigaron is a destructive and wild beast and has little personality, asides from his wild and bestial behavior.

History

Debut: The Revenge of Tsutabara Pt. 1

Umigaron along with Yamalgon were both summoned by Tsutabara to wreak havoc at Sapporo to assist the kaijin in their efforts to destroy the city and kill Sailor Fighter. Umigaron and Yamalgon showed up later to Sapporo and once they arrived, they roared and challenged Sailor Fighter, Earth Warrior Zeros and Kamen Rider Agito, also giving the five kaijin enough time to escape.

The Revenge of Tsutabara Pt. 2

Umigaron and Yamalgon were soon joined by Tsutabara's last kaiju pawn, Muchi in efforts to defeat Zeros, Sailor Fighter and Kamen Rider Agito. Umigaron attacked Kamen Rider Agito and blasted at him with his water beam and laser eye beams, but Kamen Rider Agito managed to prevail his attacks and beat up Umigaron badly.

Umigaron charged up one last water beam at Kamen Rider Agito, but Kamen Rider Agito charged through his attack and slammed his fist into Umigaron's head, doing his signature Burning Rider Punch. Umigaron then let out a final roar and fell over and exploded, killing him off. Umigaron was the first of Tsutabara's Sapporo kaiju pawns to have been destroyed.

Abilities

  • Water Beam: Umigaron could fire out a large stream of water from his mouth.
  • Laser Beams: Umigaron could fire out laser beams from his eyes.

Trivia

  • Umigaron was the only aquatic-themed kaiju that Tsutabara had.

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.