Fandom

Dragon Ball AF Fanon Wiki

Boysenberry

988pages on
this wiki
Add New Page
Talk0 Share

Boysenberry is a fictional character in the Dragon Ball franchise. He makes his debut (and ultimately, his only appearance) in the 1990 special Bardock: The Father of Goku. His name is an allusion to the boysenberry fruit. Boysenberry belongs to the same unnamed race as Appule and Orin.

Biography

Boysenberry is a member of an elite platoon led by Dodoria, Frieza's most esteemed minion. By Frieza's orders, he and his comrades meet Bardock's crew, sans their leader who is still out of commission while recovering from an attack on Planet Kanassa, on Meat, where they betray and make short work of the Saiyans.

Meanwhile, Bardock, after having been met with what he passes off as a delusion where he witnesses the destruction of his homeplanet by the hand of Frieza (the result of the ability of precognitive foresight instilled in him by a weakened survivor of the Kanassan rampage), still has yet to fully recover. When he is informed that his team has accepted an offer on Meat, he hurriedly makes preparations to pursue his friends anyways, unaware of the dangers that await at his destination. Eventually once upon Meat, Bardock discovers his ravaged teammates, and to some fortune finds that Tora is alive but in critical condition. Vowing to avenge the four, Bardock removes Tora's armband, now soaked in blood, and dons it over his head (providing an emotional backstory for one of Bardock's most recognizable physical features). Boysenberry is the first elite to be killed, when his attempts at defending himself with several beam attacks fails to stop the Saiyan from caving in his skull.

Special abilities

  • Flight, the ability to fly with the use of ki.

Voice actors



From Dragon Ball Wiki, a Wikia wiki.

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.