Fandom

Stitchipedia

Bog (512)

958pages on
this wiki
Add New Page
Comments0 Share
512 bog pfm by bricerific43-d8pqpji

Bog, A.K.A. Experiment 512, is an illegal genetic experiment created by Jumba Jookiba. He is designed to transform locations into wetlands and swamps (does so by being able to encourage plants and trees to grow incredibly fast and create large rainstorms causing floods, allowing him to turn any location into a wetland or swamp).

Bio

Experiment 512 was the 512nd genetic experiment created by Jumba with Hämsterviel's funding. He was designed to transform locations into wetlands and swamps. Jumba kept him activated during 626's creation for unknown purposes, other than perhaps causing limited amounts of chaos and confusion.

512 and the other first 624 experiments were deactivated and smuggled to Earth by Jumba during his mission to capture Experiment 626.

All of the experiment pods were released and scattered across the island of Kauai.

Lilo & Stitch: The Series

At the unknown point, he was activated, captured, tamed and named Bog.

Leroy & Stitch

All 624 experiments, including Bog, were round up by Leroy and taken to a stadium to be destroyed. However, Lilo, Stitch, Jumba, Pleakley, Reuben and Gantu arrived before the experiments could be destroyed.

It is unknown whether or not Bog participated in the following battle between the experiments and the Leroy clones.

The Leroys soon gained the upper hand in the battle, but were defeated when Lilo, Stitch, Reuben and several other experiments performed the song Aloha Oe, which caused the Leroy army to shut down due to the original Leroy's failsafe.

Biology

Appearance

Bog is a purple koala/bear-like expeirment with Pac-man-shaped ears, a lighter shade of purple on his lower jaw, a dark purple nose, and small black eyes.

Special Abilities

TBA

Weaknesses

TBA

Gallery

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.