Fandom

Wookieepedia

Unidentified teahouse (Daxam IV)

135,131pages on
this wiki
Add New Page
Talk0 Share
Queicon

The title of this article is conjectural.

Although this article is based on canonical information, the actual name of this subject is pure conjecture.

In 28 ABY,[2] the New Republic senator Ransolm Casterfo arranged to meet a local collector who specialized in Imperial artifacts at a teahouse on the planet Daxam IV. Casterfo was assisting Senator Leia Organa's investigation into the Amaxine warriors and posed as a collector of Imperial artifacts to investigate the Amaxine presence on Daxam IV. This dealer turned out to be Arliz Hadrassian, a former Imperial officer and the Amaxine leader.[1]

The teahouse was a rundown building that was staffed by human waiters since Daxam IV was too poor to afford droids. During their meeting, Hadrassian regaled Casterfo with stories about her work as a TIE fighter pilot and Imperial Security Bureau officer. Casterfo managed to gain her trust by posing as an admirer of the Old Empire. As a result, Hadrassian ascertained that he was a worthy buyer and arranged for him to collect the helmet at her compound in the Western Wastes.[1]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 Bloodline
  2. TwitterLogo @DelReyStarWars (Del Rey) on Twitter. “So excited to have @claudiagray writing a #StarWars novel with us. SW: New Republic: Bloodline coming 2016. Set 6 years before TFA.” (screenshot) The tweet in question states that the events of Bloodline take place six years before the events of the film Star Wars: Episode VII The Force Awakens. Star Wars: Galactic Atlas establishes that the events of The Force Awakens take place in the year 34 ABY and so using simple math it can be concluded that the events of Bloodline take place in 28 ABY.

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.