Fandom

Wookieepedia

Sibensko complex

134,576pages 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.

A complex was located underwater on the planet Sibensko. By the time of the New Republic era, it was regarded as a crime haven and also hosted the headquarters of a paramilitary faction known as the Amaxine warriors. The Sibensko complex also hosted a cantina that contained a computer which could access the city's computer core.[1]

In 28 ABY,[2] Senator Leia Organa and her team traveled to Sibensko to investigate the Amaxine warriors. While Leia's companions Greer Sonnel and Joph Seastriker loaded a shipment of thermal detonators, Leia and C-3PO managed to download banking records proving that the Amaxines were linked to Rinnrivin Di's cartel. Leia later killed Rinnrivin and his bodyguards during a brief shootout. The complex and the Amaxine base was destroyed during a brief skirmish when a starfighter crashed into the city's ammunition depot. This triggered a massive explosion that wiped out all of the city's inhabitants.[1]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 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.