FANDOM


Tab-canon-white  Tab-legends-black  
"Look around—your Mandalorians have been crushed. Only my droids remain now. Your battle is already lost."
"We're not finished yet. My gauntlet fighters have yet to enter the fight!"
General Grievous and Darth Maul during a battle on Zanbar[src]

The Kom'rk-class fighter,[7] also known as the Gauntlet starfighter,[2] was a type of starfighter and troop transport used by the Mandalorian splinter faction known as Death Watch during the Clone Wars. The fighters were utilized as part of a move by Death Watch leader Pre Vizsla to end Satine Kryze's pacifist rule of Mandalore and restore the Mandalorians to their former warrior past. These ships were later used by Darth Maul's Shadow Collective army during battles on Zanbar, Ord Mantell, and Vizsla Keep 09. During each of these battles, Darth Maul utilized a gauntlet fighter called the Nightbrother,[8] colored red and black rather than the normal white and blue color scheme, as a transport and a Shadow Collective flagship.[9] During the reign of the Galactic Empire, a gauntlet fighter known as the Splendour was owned by the Besalisk criminal Galus Vez, who used it to race opponents on his private racing track, the Fool's Run.[10]

30 years after the Battle of Endor, the retired pirate Delphi Kloda owned a Gauntlet called the Sparrowhawk, which he lent to his former protege Bazine Netal.[11] The Journeyman Protectors used a similar fighter known as the Fang fighter.[12]

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

Behind the scenesEdit

Gauntlet starfighters were created for the canon animated series Star Wars: The Clone Wars.

AppearancesEdit

SourcesEdit

Notes and referencesEdit

Wiki-shrinkable
Wookieepedia has 6 images related to Kom'rk-class fighter.
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.