FANDOM


Adambo[2] was a human[1] vice general in the Galactic Empire who was captured by a team of New Republic Imperial-hunters led by pilot Norra Wexley sometime between the rebellion on the planet Akiva and the team's mission to the planet Vorlag[2] in 5 ABY.[3] After the vice general was successfully captured, the team put Adambo's image up on a board in their SS-54 gunship the Halo, which included images of all the Imperial targets they had successfully captured.[2]

Behind the scenesEdit

Adambo was first mentioned in the novel Aftermath: Life Debt, which was written by Chuck Wendig and released in 2016.

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 According to TwitterLogo @ChuckWendig (Chuck Wendig) on Twitter. “@lelalmekha Yes!”, All Imperial officers seen or mentioned in Aftermath: Life Debt are human.
  2. 2.0 2.1 2.2 2.3 2.4 Aftermath: Life Debt
  3. Star Wars: Galactic Atlas places the Battle of Endor During the year 4 ABY. Shattered Empire, Part IV, which shows Shara Bey and Kes Dameron settling on Yavin 4, takes place three months after the Battle of Endor, and Galactic Atlas places Bey and Dameron's move to Yavin 4 in the year 5 ABY.
    In the novel Aftermath it is said that months have passed since the Battle of Endor. Aftermath: Life Debt begins two months after the end of Aftermath, therefore the events of the former take place at least four months after the Battle of Endor. Since three months after the Battle of Endor is part of 5 ABY, as shown with Bey and Dameron's settling on Yavin 4, events of Life Debt must take place in 5 ABY at the earliest. On the other hand, the Galactic Atlas dates the Battle of Jakku, as depicted in Life Debt's sequel Aftermath: Empire's End, to 5 ABY, as well, leading to the conclusion that Life Debt is set in 5 ABY.
In other languages

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.