FANDOM


Lozen Tolruck's island fortress was a hidden fortress that Imperial Grand Moff Lozen Tolruck maintained on the planet Kashyyyk following the Battle of Endor. His fortress was fortified by wroshyr wood and contained a control module which programmed and controlled the inhibitor chips that had been implanted into the planet's Wookiee population. The island fortress was located at a great distance from Camp Sardo. The fortress had several Wookiee slaves and droids and was guarded by several forest troopers.[1] In 5 ABY,[2] the former Imperial loyalty officer–turned–New Republic operative Sinjir Rath Velus visited the fortress to rescue his friend Jom Barell and to disable Tolruck's control module. During the liberation of Kashyyyk, the Wookiee slaves rose up in revolt and killed Tolruck and his men.[1]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 Aftermath: Life Debt
  2. 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.