Fandom

Dragon Ball Updates Wiki

Nameless Namek

1,053pages on
this wiki
Add New Page
Comments0 Share



Nameless Namekian
[1]
Alternate names "The Namek who has long since forgotten his name"

Kamiccolo Piccolo

Debut Anime: "Earth's Guardian Emerges"Manga: "The Mysterious Spaceship"
Appears in [2]

[3][4]

Race Namekian
Date of birth Before Age 242Resurrected in Age 767
Date of death Age 762 (revived)Age 789
Height 8'2" (originally)

7'4" (as Piccolo)

Weight 441 lbs. (originally)

255 lbs. (as Piccolo)[citation needed]

Family

The Nameless Namekian is a nameless Namekian, son of Katas. He was originally one being until he separated the evil out of his body, becoming Kami and removing King Piccolo from his soul. He makes his debut in a flashback during "Earth's Guardian Emerges", the 125th episode of the Dragon Ball anime, which premiered on August 31, 1988. He continues making cameo appearances in flashbacks throughout the Dragon Ball anime and manga, and reappears in the Dragon Ball Z episode "Plans for Departure", and continues to make brief cameo appearances until making his formal debut (in the form of Piccolo) in "The Reunion", the 141st episode ofDragon Ball Z, which premiered on May 27, 1992.


BiographyEdit

[5]The nameless Namekian exiting his spaceshipAdded by BeadtmdcThe nameless Namekian was born on planet Namek in Age 242 to the Namek Katas. As a child, the planet underwent a catastrophic natural disaster that killed everyone except him,Grand Elder Guru, and the movie-only Lord Slug. To survive, he was launched into outer space by his father in a spaceship which requires at least a basic knowledge of the ancientNamekian language to pilot. The spaceship landed on Earth in the frigid Yunzabit Heights, where the nameless Namek spent his life alone from youth through adolescence.

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.