Fandom

Dragon Ball Updates Wiki

Future Vegeta

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

Directory: CharactersSaiyansZ FightersAlternate Timeline

Future Vegeta
VegetaFutureGokusDead02
未来のベジータ
Mirai no Bejīta
Alternate names Mirai Vegeta
Vegeta of the Future
Debut Cameo: "Mystery Revealed"
Full Appearance: "Ghosts from Tomorrow"
Appears in
Z Ball.svg
Race Saiyan
Gender Male
Date of birth Age 732
Date of death Age 762 (Revived)
May 12th, Age 767
Height 5'3"
Weight 123 lbs.
Address WST 3338926 K.
Occupation Warrior
Allegiance Planet Trade Organization (Saiyan Army)
Z Fighters (Age 762 - 767)
Family
  • Vegeta (alternate timeline counterpart)
  • King Vegeta (father)
  • Tarble (brother)
  • Future Bulma (lover)
  • Gure (sister-in-law)
  • Future Trunks (son)
  • Nappa (comrade)
  • Raditz (comrade)
  • Future Cell (modified clone)
  • Future Vegeta is the alternate timeline counterpart of Vegeta who appeared in the alternate timeline in which Future Trunks and Future Gohan lived. This Vegeta appears in the brief opening scene of Dragon Ball Z: The History of Trunks and in a flashback during an episode of Dragon Ball Z. Future Vegeta was the lover of Future Bulma, and the father of Future Trunks.

    BiographyEdit

    VegetaFutureVsFutureAndroid17

    Future Vegeta as a Super Saiyan battles Future Android 17 (anime flashback)

    Future Vegeta's life was the exact same as his main timeline counterpart's life until August of Age 764 when Future Goku used the Instant Transmission to arrive on Earth and kill Frieza and King Cold. Sometime afterward, Vegeta trained and became a Super Saiyan.

    In Age 766, Future Goku had been stricken down by a deadly Heart Virus that had no cure. Future Vegeta, along with the other Z Fighters and company await the news of Future Goku's health. However, Future Goku passes away, leaving Future Vegeta shocked about Future Goku's death and finds himself very upset due to the fact that he will never get his chance to defeat his rival in battle.

    FuturVegetaDeath

    Future Vegeta lies in his grave (anime flashback)

    Six months later on May 12th, Age 767, the Androids attack and Future Vegeta is the second Z Fighter to be killed by them. In the TV special, Vegeta is shown receiving a hard kick to the stomach by Future Android 17, and in the episode "Ghosts from Tomorrow" it is shown during a flashback that he dies after being struck by 17's Photon Flash while stuck in the ground after a receiving the brutal attack. In both instances, he retains his Super Saiyan power and abilities.

    Future Vegeta was 35 years old when he died.

    TriviaEdit

    • In Future Trunks' flashback, he claimed that Future Vegeta was the first to die at the hands of Androids 17 and 18, and Future Piccolo was the second. However in The History of Trunks, it was said Future Piccolo was the first to die and Future Vegeta was the second.

    GalleryEdit

    Saiyans
    Pure-blooded Saiyans BardockBorgosBroly (Bio-Broly) • FashaFuture GokuGokuKing VegetaNappaOnioOriginal Super SaiyanParagusRaditzScarfaceShortyShugeshTarbleToraTurlesFuture VegetaVegetaZorn
    Hybrid Saiyans BullaFuture GohanFuture TrunksTime Patrol TrunksGohanGotenTrunksPanVegeta Jr.'s motherGoku Jr.Vegeta Jr.
    Saiyan Fusions GotenksGogetaGokuleVegitoHypothetical fusion of Goku and Dende
    Saiyan Transformations Great ApeSuper Saiyan (Ascended Super SaiyanUltra Super SaiyanFull-Power Super Saiyan) • Super Saiyan 2Super Saiyan 3Super Saiyan 4Golden Great ApeFalse Super SaiyanLegendary Super Saiyan
    Related Articles FriezaPlanet Trade OrganizationIllusion SaiyanTufflePlanet VegetaPlanet Frieza 79Saiyan-Tuffle warKanassan warInvasion of Planet MeatGenocide of the SaiyansTritek warPower BallAttack BallScouterBlutz WavesFailed FusionsMonkey Boy (Charles Chen)Goku (Justin Chatwin)

    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.