FANDOM


MP-EpisodeVIII

It's time for the Jedi to end.

Warning! This page contains SPOILERS from Star Wars: The Last Jedi. If you don't want spoilers, leave the page!

The Vakbeor-class cargo frigate was a type of hybrid cargo frigate design manufactured by Kuat Drive Yards. They were used by the Resistance navy during its conflict with the First Order.

CharacteristicsEdit

The Vakbeor-class was envisioned a combination of basic anti-pirate defenses with an extensive cargo capacity. Its light armament was made up of four laser cannons; it also boasted two tractor beam projectors.[1]

HistoryEdit

After the bankruptcy of Gallofree Yards, Inc., the Galactic Empire engineered the company's takeover by Kuat Drive Yards. KDY coupled existing Gallofree designs with elements of its own Nebulon frigate line to create the Vakbeor-class.[1]

The new design would fare poorly on the galactic starship market, with many of them being dumped on the secondary market. Despite its initial role as an anti-pirate freighter, it became popular with pirate bands.[1]

One ship, the Vigil, was used by pirates until it was captured by the Resistance, a New Republic-sponsored paramilitary group, in a battle off the Chadrison Shoals.[1] The Vigil participated in the evacuation of D'Qar and the attack on the Resistance fleet where it was subsequently destroyed by a barrage of fire from First Order starships.[2] The Vigil played an escort and support cruiser role to the star cruiser Raddus until it was destroyed by the First Order attack.

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

Behind the scenesEdit

The Vakbeor-class cargo frigate appears in the 2017 Star Wars saga film Star Wars: Episode VIII The Last Jedi.

AppearancesEdit

SourcesEdit

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.