FANDOM


"Rhen Var is merely an outpost... So: Nam Chorios?"
"Instruct Belderone to send the Liberator there."
―Wilhuff Tarkin and Darth Vader[src]

The Liberator was a Venator-class Star Destroyer belonging to the starfleet of the Galactic Empire. Five years after the inception of the Empire, it was parked at R/M Facility Four deepdock at Belderone.

CharacteristicsEdit

In its dorsal flight deck, there were passing starfighters, ground-effect vehicles and, at least, one shuttle craft.[2]

HistoryEdit

Fifteen years before the Battle of Yavin, following the attack on Galidraan Station by Berch Teller's rebel cell on the Carrion Spike, Moff Wilhuff Tarkin and Darth Vader contacted Belderone to send the Liberator to Nam Chorios to protect its resources―a mining colony and a small Imperial prison facility―from Berch Teller even after losing track of the Carrion while trying to capture them with the Parsec Predator.[2]

As ordered, the captain of the Liberator commandeered the starship to Nam Chorios, where instead of facing the insurgents, the ship was boarded by Tarkin and Vader shortly before the attack on Lucazec, when the Liberator received Teller's HoloNet transmission of the attack. Though Vader left the ship as soon as the Goliath arrived from Coruscant with his personal starfighter, Tarkin stayed at the Liberator’s data center for several hours. Finally, he asked Liberator’s captain to provide him with a shuttle for his personal use so as to rendezvous with the Goliath. Afterwards, instead of returning to Belderone, the Liberator was deployed to Ord Cestus, down the Perlemian Trade Route, as a result of the attack on the TaggeCo mining facility.[2]

Ship-stub This article is a stub about a ship or starship. You can help Wookieepedia by expanding it.

AppearancesEdit

Notes and referencesEdit

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.