This article covers the Canon version of this subject.  Click here for Wookieepedia's article on the Legends version of this subject. 

Master Qui-Gon, more to say, have you?

It is requested that this article, or a section of this article, be expanded.

See the request on the listing or on this article's talk page. Once the improvements have been completed, you may remove this notice and the page's listing.


We're Doomed!

This article covers an essential topic and is in need of major additions and/or work.

Please follow the guidelines in the Manual of Style and complete this article to the highest level of quality before continuing on other articles.

"Warning. Enemy capital ships. Venator-class."
―A tactical droid[src]

The Venator-class Star Destroyer, also known as a Republic attack cruiser or Jedi Cruiser, was a line of wedge-shaped Star Destroyers in service with the Galactic Republic Navy during the Clone Wars. The backbone of the Galactic Republic's naval forces, the Venator was a versatile capital ship capable of serving as a troop carrier, a cargo transport, and a warship for ship-to-ship combat. Its front section contained a large flight deck and hangars to accommodate a complement of Republic starfighters and gunships.

The Republic deployed the Venator-class Star Destroyers across the galaxy during the conflict with the Confederacy of Independent Systems. Often utilized as flagships by the Jedi Generals of the Grand Army of the Republic, the Venator-class was closely associated with the Jedi Order as a result. Venators served in several major engagements of the Clone Wars, including the Battle of Christophsis, the Battle of Sullust, and the Battle of Coruscant.

Following Order 66 and the rise of the Galactic Empire, Venator-class Star Destroyers remained in service to the Imperial Navy during the early days of the Imperial Era. Ultimately, though, the Venator-class was decommissioned and replaced by the Imperial-class Star Destroyer, a larger warship that was modeled on its Republic predecessor.

Characteristics[edit | edit source]

Hangar space[edit | edit source]

"Control failed to report in. We think they'll make their move to escape via the main hangar."
"Affirmative, I want squads marshaled at position 2-5 and 2-7."
―A clone trooper and CT-5597 "Jesse"[src]

The Venator-class Star Destroyer was a resourceful cruiser suited for transport and ship-to-ship combat.

During the early period of the Clone Wars, the Venator-class Star Destroyer featured a wide array of hangar space. The forward section of the Star Destroyer featured a passage down the middle, with bays for starships on either side. It was mainly accessed by large doors on top of the ship.[8] At the fore of this passage, at the bow the ship, was a collection of hyperspace transport rings.[11] Towards the aft of the passage, doors in the floor could open, leading to a space where Republic frigates could dock.[12] If no cruiser was docked, however, the space could be used by personnel to jump out of the Star Destroyer directly onto the battlefield,[13] or to deploy walkers without the need for dropships.[11] Overseeing the passage was a raised command station positioned at the aft.[9] Even further aft, the Venator-class had two independent docking bays on their port and starboard sides, again protected by blast doors.[8]

A new version of the Venator-class featured smaller doors on the ship's dorsal side.

Towards the end of the war, a different type of Venator was used. These featured a set of smaller doors on the dorsal side of the ship, and lacked access from the ventral side altogether, with the blast doors that previously lead to the main hangar space replaced with additional lighting, a crane and sometimes additional weaponry, such as a built-in beam weapon. Additionally, the side doors no longer led to independent hangars, but another passage that linked the two sides of the ship. The central hangar row then joined the smaller passage in the middle, replacing where the command station used to be. At the front of the main passage was a small opening starfighters could launch from without having to go through any of the main doors.[14]

Bridges[edit | edit source]

"We've entered the atmosphere. Fire retro-rockets!"
"We've lost lateral control. We're gonna break apart—"
―Clone navigation officers[src]

The starboard bridge was designated as the command center, while the port bridge was for starfighter operations.

Venator-class Star Destroyers featured two bridges, with the starboard bridge serving as the primary command center of the ship and the port bridge being dedicated to starfighter operations.[15] These bridges were raised from the main body of the destroyer and provided a wide, panoramic view of the battle. However, the bridges' exposed nature made them vulnerable to attack.[15][16] The bridges featured large windows at the front, with two sunken pits behind, with a raised command walkway in between. This design would become a staple in Imperial vessels, giving emphasis to the command hierarchy. Further behind, a holotable sat between two sets of blast doors which could be used for communication, ship analysis and troop movements.[8][10]

Engines[edit | edit source]

"Sir, the hyperdrive generators are failing!"
"Disengage! Disengage!"
"It's too late!"
―Clone navigation officers[src]

The Venator-class Star Destroyer featured ion thrust engines.

The Venator-class featured ten engines, with three distinct sizes.[10] They were powerful enough to successfully destroy a Lucrehulk-class Battleship by ramming.[16]

Landing capabilities[edit | edit source]

A Venator usually required specialized landing strips to perform atmospheric landings, such as those on Coruscant,[10] while the similar Acclamator-class assault ships could perform surface landings with their legs.[17] However, surface landings could occur, as exemplified during the Battle of Kashyyyk.[10]

Complement[edit | edit source]

Along with its impressive starfighter complement, the Venator also carried several gunships, shuttles, a variety of ground vehicles and modular components in order to deploy a planetary garrison.[18]

History[edit | edit source]

Clone Wars[edit | edit source]

Warships of the Republic[edit | edit source]

With the outbreak of the Clone Wars, the Galactic Republic turned to the Venator-class Star Destroyer for its versatility.[5] Leading the Republic war effort, the Jedi assigned the role of flagship to the Venator-class. As a result, the Venators became known by the colloquial term "Jedi Cruiser" due to their affiliation with the Jedi Generals of the Grand Army of the Republic.[7]

Battle of Christophsis[edit | edit source]

The Galactic Republic deployed a fleet of Venator-class Star Destroyers to break through the Separatist blockade of Christophsis.

Several months after the outbreak of the Clone Wars with the First Battle of Geonosis, the Confederacy of Independent Systems had established a 30-warship blockade over the planet Christophsis led by the Harch Admiral Trench,[19] which allowed the Separatists to gain access to the Corellian Run and the resources on the surface.[20] The Separatists' occupation soon led to the Battle of Christophsis, where their blockade was engaged by a fleet of three Venator-class Star Destroyers and three Pelta-class frigates led by Jedi General Anakin Skywalker aboard the Resolute. However, Skywalker's fleet was severely outnumbered and outgunned, leading to the loss of one of the supply ships and all three Star Destroyers taking heavy damage.[19]

Skywalker was later reinforced by fellow Jedi General Obi-Wan Kenobi, who arrived aboard the Venator-class Star Destroyer Negotiator. After Kenobi arrived to assist Skywalker, the former ordered the latter to withdrawal his ships and regroup on the other side of Leesis, Christophsis' moon, where Skywalker would be asked to pilot a new prototype stealth ship and continue with his mission to deliver the supplies to Senator Bail Organa and his troops, who were attacked by the droid forces by air and ground.[19] Deciding to take matters into his own hands, Skywalker went on the offensive and engaged Trench's flagship, Invincible, and managed to destroy the command ship, although Trench managed to survive,[21] sending the remaining ships of the Separatist fleet into disarray, allowing Kenobi and the remaining Republic ships to engage the rest of the fleet.[19]

After establishing a base on the planet's surface,[22] the Republic fleet was once again engaged by Separatist warships, forcing Admiral Wullf Yularen aboard the Resolute to retreat to a Haven-class medical station. After retreating, Jedi Master Mace Windu contacted a clone officer to summon Admiral Wurtz, requesting three star cruisers from his fleet. Gaining additional reinforcements, Admiral Yularen and Master Yoda managed to break through the Separatist blockade with the Venator-class Star Destroyers, which fled the system, and allowed the Acclamator-class assault ships from Wurtz's fleet to land on the surface, supplying additional clone troopers and winning the battle.[23]

Battle of Ryloth begins[edit | edit source]

In the first year of the war, the Separatist Alliance led a planetary-wide invasion of the Outer Rim world of Ryloth, establishing a blockade under the command of Captain Mar Tuuk of the Confederacy of Independent Systems Navy. However, a fleet of at least two Venator-class Star Destroyers under Republic Admiral Dao were providing protection for Jedi General Ima-Gun Di and the Outer Rim garrison clone troopers, but his fleet's necessary resources began to diminish, and were soon destroyed after the Star Destroyers' shields were disabled.[24]

Malevolence campaign[edit | edit source]

"And we have had no further contact with General Plo Koon. The absence of distress beacons indicates that his fleet was… that his fleet was destroyed, like the others. We are about to prepare a rescue mission."
―Anakin Skywalker — (audio) Listen (file info)[src]

Three Venator-class Star Destroyers were destroyed by the Malevolence, a Separatist Subjugator-class heavy cruiser.

Later on in the Clone Wars, the Separatists secretly created the Malevolence, a Subjugator-class heavy cruiser equipped with two devastating mega-ion cannons that could easily disable the systems of any ship, starfighter or station, including an entire fleet of three Venator-class Star Destroyers led by Jedi General Plo Koon. Koon, commanding the hunt for the mystery weapon from the Venator-class Star Destroyer Triumphant, was able to report his fleet's position in the Abregado system before the Republic transmissions were jammed. The Malevolence then fired it's portside mega-ion cannon at the Republic fleet, disabling all three Venators, before unleashing a barrage of turbolaser fire on the helpless warships. Completely defenseless, all three ships were torn apart by the barrage with the Triumphant being the last to fall, seconds after Koon and some of the crew managed to evacuate in escape pods.[25]

After Plo Koon's forces were decimated by the Malevolence at the Battle of Abregado, the Republic, learning of the warship and its ion cannons, attempted to locate the Malevolence, which was placed under the commander of the notorious Separatist General Grievous. However, after receiving information of the destruction of a Republic medical convoy of three Pelta-class frigates escorted by a lone Venator-class Star Destroyer at the hands of the Malevolence in the Ryndellia system, which was close to Naboo and the Kaliida Shoals Medical Center, the Republic's secret Haven-class medical station, which was tending to over 60,000 wounded clone troopers, and would become Grievous' next target, leading to the loss of both of the Malevolence's ion cannons and the deactivation of the ship's hyperdrive.[26]

After losing its primary weapons and the hyperdrive being disabled, Jedi Master Kenobi led a fleet of three Venator-class Star Destroyers, including Kenobi's flagship Negotiator and Skywalker's flagship Resolute, against the Malevolence, which was retreating to Separatist-controlled space.[26] Despite it's crippled state, the Malevolence's sheer size meant that that it was able to absorb the full firepower of all three Star Destroyers. Hoping to destroy Grievous whilst the vessel was unable to flee, Kenobi ordered all batteries to target the Malevolence's command bridge at maximum firepower, but the ships were forced to cease their assault when an arriving Republic senator, lured to the battle zone under false pretenses, was drawn into the cruiser and taken hostage. The three Venators maintained their pursuit of the Malevolence, however, and resumed firing at Koon's order when the senator was safely extracted, though their participation was ultimately rendered unnecessary when, thanks to some internal sabotage, the Malevolence crashed into a nearby moon when it attempted to jump to hyperspace.[27]

Liberation of Ryloth[edit | edit source]

The Defender collided with a Lucrehulk-class Battleship during the Ryloth Campaign.

Some time after the Separatists gained full control of Ryloth, with the Separatist blockade holding a tight grip around the planet, the Republic sent a fleet of three Venator-class Star Destroyers—the Resolute, Defender, and Redeemer—under Jedi General Anakin Skywalker, Admiral Yularen and Skywalker's Padawan Ahsoka Tano, to break through the blockade to allow the Republic to land their forces on the planet's surface. While Skywalker and Yularen commanded the fleet from the Resolute, Tano was to command a squadron of V-19 Torrent starfighters to engage the attacking vulture droid starfighters, and after breaking through the vulture droids, she pressed her attack on the blockade, but were caught off guard as the Separatists summoned four additional Munificent-class star frigates, and launched their fighters to attack the Venator-class Star Destroyers. Outflanked and overwhelmed, Skywalker and Yularen both ordered the young Jedi back to defend them from the enemy vulture droids, which were launching suicide runs against the three Star Destroyers. After Ahsoka was ordered a final time by Skywalker to return to the fleet and Admiral Yularen was severely injured after the Resolute's bridge was rammed by a vulture droid, Tano reluctantly ordered the remaining pilots of her squadron to return to the Resolute so the Star Destroyers could flee the system, before jumping to hyperspace, the Star Destroyer Redeemer was unfortunately destroyed.[16]

After the Resolute and the Defender fled the system, Skywalker was contacted by Jedi Masters Mace Windu and Obi-Wan Kenobi, and informed them of their lack of progress and their losses. Windu warned Skywalker that if his attempt to break the blockade was unsuccessful, the Republic's planned invasion would have to be postponed, although Skywalker stated that the Twi'leks could not afford the postponement, and assured them that he would break through the blockade. Indeed, after he crashed the Defender into the Droid Control Ship, and Tano used a Marg Sabl tactic to outmaneuver the other CIS ships, the Republic invasion fleet was able to arrive and land on Ryloth.[16]

Carida incident[edit | edit source]

"The Jedi Council will be there, along with Republic officers from around the galaxy and… What the… The Separatists are going to ram the station with this ship!"
―Meebur Gascon[src]

In the final year of the Clone Wars,[28] the Galactic Republic had held a strategy conference in the Carida system, aboard the Valor orbiting the planet Carida. However, unknown to the Republic, the Confederacy of Independent Systems was planning to bomb Valor and end the conference. As part of their plan,[9] the Separatist forces managed to hijack one of the Republic's Venator-class Star Destroyers, which had been held in orbit above the Outer Rim world of Abafar, a planet rich in an extremely valuable and highly volatile starship fuel known as rhydonium, which the Separatists were mining from a mining facility established on the surface by the Confederacy, with the intent of loading the Star Destroyer with thousands of canisters of rhydonium to transform the vessel into an unassuming bomb.[29]

Following their escape from Abafar, the Republic's D-Squad, a covert unit of Republic astromech droids and one DUM-series pit droid, led by Zilkin Colonel Meebur Gascon,[30] managed to board the Star Destroyer, assuming that the Republic had sent the Venator to rescue them. However, once they arrived on the Star Destroyer's command bridge, they discovered that Separatist forces had hijacked the vessel, and, after narrowly escaping the pursuing battle droids, Colonel Gascon and the droids found a detonator painted in the respective colors of the Separatist Alliance in the center of the hangar bay control room, coming to the realization that the ship was truly a massive, unassuming bomb, opening the doors inside the hangar, revealing thousands of rhydonium canisters stacked together in each hangar, and upon sight of the canisters, Colonel Gascon remarked that the amount of rhydonium aboard the vessel could possibly destroy the entire Republic Navy.[9]

A hijacked Venator was destroyed in a rhydonium-fueled explosion.

While aboard the Venator in hyperspace, D-Squad came across a small group of Republic droids that served aboard the Star Destroyer before the Separatists took control, one of which was the LEP servant droid BNI-393, who informed the squad that the ship had been hijacked by the Separatists, and that its destination was a space station located within the Carida system, bringing the Zilkin to realize that the Separatists intended to use it to kamikaze the Republic space station Valor, the location of the Republic's strategy conference, forcing the team to take matters into their own hands and thwart the Separatists' plans by triggering the ship's explosion sooner than intended. However, the team soon ran into a series of complications as the super tactical droid in charge of the operation sent a swarm of buzz droids after the squad to dispatch them, but were eventually defeated at the cost of one of the team's members, M5-BZ, who sacrificed himself in order to defeat the buzz droids by opening the airlock, pulling the buzz droids into hyperspace. After BZ's sacrifice, the Star Destroyer exited hyperspace in the Carida system, and the engines were put to maximum power.[9]

Before the super tactical droid could initiate the countdown sequence, he crossed paths with the astromech droid R2-D2, who managed to keep the Separatist droid out of reach of the detonator, granting him a small amount of time to trigger the detonation before it reached the station, resulting in a simultaneous explosion of the rhydonium canisters, destroying the Star Destroyer and creating a large blast that engulfed the station and all vessels flanking it, sending large pieces of debris hurtling through space, obliterating a single Arquitens-class light cruiser, and damaging the station.[9]

Battle of Coruscant[edit | edit source]

"Anakin, Rex, prepare all forces. We're jumping to hyperspace immediately."
―Obi-Wan Kenobi[src]

Nearing the end of the Clone Wars and, subsequently, the Galactic Republic, the Confederacy of Independent Systems—under the orders of Darth Sidious, the true leader of the Confederacy—launched a massive and startling assault on the planet Coruscant in the Core Systems, the capital of the Republic, in an attempt to capture Supreme Chancellor Sheev Palpatine, who secretly orchestrated the battle and arranged for himself to be kidnapped by the Kaleesh cyborg Grievous as part of his plan to bring Jedi Knight Anakin Skywalker closer to the dark side of the Force.[10]

Prior to the assault, the Republic and Separatist Alliance became enmeshed in the climax of the Outer Rim Sieges campaign, which was primarily fought on various worlds of the Outer Rim Territories, far from the Core Worlds and, consequently, Coruscant.[10] As a result of the Sieges, most of the Republic's fleets, experienced officers and Jedi Generals were preoccupied on the various fronts of the campaign, leaving Coruscant sparsely protected by the Republic's remaining officers and the ill-prepared Coruscant Home Defense Fleet, which had seen little to no action in the duration of the Clone Wars, giving the Separatists an opportunity to launch an unexpected and seemingly effortless attack on the Republic's capital.[31]

Over a thousand Venators defended the Republic capital during the Battle of Coruscant.

Despite the high belief that the Separatists would never attempt such an attack, the Confederacy unexpectedly attacked Coruscant with a fleet of over 1,000 starships led by Grievous' flagship, the modified[20] Providence-class Dreadnought Invisible Hand,[32] catching the Home Defense Fleet off guard and quickly overwhelming them, with the Chancellor, after a lengthy chase through the Federal District, taken captive by Grievous back to the Invisible Hand.[33]

Learning of the Separatist attack, the Republic's Open Circle Fleet and Jedi Generals Kenobi and Skywalker were recalled to Coruscant to rescue the Chancellor from Grievous. The Coruscant Home Defense Fleet, despite being outnumbered, attempted to prevent the Invisible Hand from escaping with the Chancellor onboard.[20] Before the Separatists could make their escape from the besieged capital, the Open Circle Armada and the two Jedi arrived in time, bolstering the number of Venator-class Star Destroyers to the thousands, including the Star Destroyer Ro-ti-Mundi, to engage the large number of Munificent-class star frigates, Recusant-class light destroyers and Lucrehulk-class Battleships, which were escorting the Invisible Hand in order for it to flee, and allowed Generals Kenobi and Skywalker to enter the heart of the chaos of turbolaser fire and starships with their personal Eta-2 Actis-class light interceptors. Struggling to reach the flagship due to the interference of hundreds of Vulture droids, droid tri-fighters, and a brief evasion of discord missiles, two of which managed to deploy buzz droids onto Obi-Wan's starfighter, but were nonetheless destroyed. Returning to their flight path to the command ship, the Jedi quickly discovered that the hangar bay still had its deflector shields raised, forcing Anakin to open fire on a vulnerable point of the hangar to deactivate its shields, granting them mere seconds to enter the hangar before the blast shields were completely shut.[10]

The Guarlara sustained damage while trading fire with a Separatist warship.

While aboard the Invisible Hand, the Jedi released the Chancellor from captivity and managed to kill the Sith Lord Count Dooku, the Confederate Head of State, and following their triumph over Dooku, the dreadnought briefly came into confrontation with the Venator-class Star Destroyer Guarlara and the two starships exchanged turbolaser fire as they engaged one another, with Guarlara inflicting extensive damage upon the Invisible Hand, causing it to momentarily plummet towards the planet below before the crew regained control.[10] Despite rescuing the Chancellor and destroying a third of the CIS Navy, Grievous nonetheless managed to escape his flagship aboard an escape pod, which was retrieved by the Lucrehulk-class Battleship[31] Profusion. Only days later,[20] however, Kenobi killed Grievous and, shortly after that, Skywalker turned to the dark side of the Force. He slaughtered the Separatist Council on Mustafar and ordered the Trade Federation to deactivate all remaining Separatist droids immediately, officially ending the Clone Wars.[10]

Siege of Mandalore and Order 66[edit | edit source]

"This ship is going down, and those soldiers, my brothers, are willing to die and take you and me along with them."
―CT-7567 "Rex," to Ahsoka Tano[src]

The Tribunal was lost along with its crew during the onset of Order 66.

The Venator-class Star Destroyer Tribunal[34] was commanded by Ahsoka Tano and her special division of the 501st Legion. The cruiser ferried Tano, Commander Rex and the division back to Coruscant following the successful capture of former Sith Lord Maul on Mandalore, with Maul a restrained and guarded prisoner on the detention level. En route to Coruscant, however, Order 66 was implemented and the clones turned on Tano, also attempting to kill Maul on Darth Sidious' orders only for him to be freed by Tano as a distraction, allowing her to ambush Rex and have his control chip removed, freeing him from the brainwashing. The ensuing skirmish aboard the Venator resulted in it crashing onto a desolate moon after Maul destroyed the hyperdrive, with the loss of all hands aboard save for Maul, Tano and Rex. The wreckage of the Venator would remain on the moon well into the Imperial Era, becoming buried in snow, until it was discovered by the Empire and investigated personally by Darth Vader, Skywalker's Sith identity, who retrieved his former apprentice's lightsaber from the crash site before departing.[35][36]

Another Venator, commanded by Jedi Master Chiata, engaged in battle with a Separatist dreadnought in the final hours of the Clone Wars. Though it managed to destroy the opposing warship, the Venator was itself critically damaged and ended up crashing on the isolated world of Zeffo. Chiata, her Padawan Marseph, her unit's clone commander and a majority of the clone unit survived the crash, but the implementation of Order 66 saw the deaths of all involved, with Chiata being buried in the cruiser's wreckage by her Padawan before he succumbed to his own wounds and the clones being buried by the native villagers, who set up a shrine to them near the crash site. The wreckage of this Venator would as well endure into the time of the Empire, becoming inhabited by various native fauna.[37]

The Albedo Brave was destroyed by Jaro Tapal after his clone troopers turned against him.

The Albedo Brave was a Venator-class Star Destroyer commanded by Jedi Master Jaro Tapal and his 13th "Iron" Battalion. The Albedo Brave was stationed in orbit above Bracca, having successfully secured the planet after a lengthy campaign, and was due to move on to Mygeeto when Order 66 was issued, forcing Master Tapal and his Padawan Cal Kestis to fight for their lives against their formerly loyal comrades. Though the two Jedi managed to kill many of the clones in their path, including the battalion's commander, and reach the escape pod bay, but they were outnumbered and Tapal was fatally wounded just as they boarded an escape pod. The Albedo Brave was subsequently destroyed as a result of its reactors being sabotaged by Tapal to mask their escape, taking all the surviving clones aboard with it.[37]

Legacy[edit | edit source]

The Galactic Empire decommissioned the Venator-class, replacing it with the larger Imperial-class Star Destroyer.

In the years after the formation of the Galactic Empire, Venators were still in service; however, they were being gradually replaced by the newer Imperial I-class Star Destroyer, which had been introduced in 18 BBY,[source?] as the backbone of the Imperial Navy. By 14 BBY,[38] many Venator-class Star Destroyers used in the Clone Wars were scrapped on planets like Bracca, which were the sites of major campaigns during the war.[37] The salvaged parts were meticulously picked through by large numbers of workers and the salvageable material was used to support the construction of newer Imperial machinery and ships.[39]

The design of the Venator-class Star Destroyer ultimately evolved into the similarly wedge-shaped Victory-class Star Destroyer and Imperial-class Star Destroyer, the signature battleship of the Galactic Empire.[39][40] As of the Campaign at Salient, during which Venator-class Star Destroyers reassigned from Telos deployed ARC-170 starfighters, another ship that was heavily used in the Clone Wars but was beginning to be phased out, to assist Governor Wilhuff Tarkin and the Executrix, the vessel was considered an older-generation model.[41] However, it was still in production by 5 BBY[18] and at least one Venator-class was stationed at the Anthan Prime Orbital Dockyard several months after the Battle of Yavin.[42]

Vanguard Squadron happened upon the wreckage of a Venator in the Zavian Abyss.

In 4 ABY,[43] the New Republic's Vanguard Squadron came across the wreckage of a Venator-class, while escorting three GR-75 medium transports, before coming into contact with the Imperial II-class Star Destroyer Overseer. A part of a New Republic ambush in the Zavian Abyss, where they revealed their prototype Starhawk.[44]

The wreckage of a Venator-class Star Destroyer was located on the junk world of the Necropolis by the time of the New Republic Era. In 34 ABY,[45] the Force-sensitive scavenger Rey visited the Necropolis in order to repair the Millennium Falcon. She was granted permission to salvage spare parts by Ara-Nea, a proprietor of the Necropolis, who charged the scavenger five hundred credits. Surveying the junk field from the dorsal side of a Venator, Rey considered it a "feast" as opposed to a typical day of scavenging for her.[46]

Appearances[edit | edit source]

Explore all of Wookieepedia's images for this article subject.

Non-canon appearances[edit | edit source]

Sources[edit | edit source]

Notes and references[edit | edit source]

  1. 1.0 1.1 Ultimate Star Wars
  2. Tarkin
  3. Twitch-Logo.png Atomic Mass Transmissions Live Star Wars! on the atomicmassgames Twitch channel (original link)
  4. FantasyFlightGamesLogo.png Republic Reinforcements on Fantasy Flight Games' official website (backup link)
  5. 5.0 5.1 5.2 StarWars-DatabankII.png Republic Attack Cruiser in the Databank (backup link)
  6. Star Wars Encyclopedia of Starfighters and Other Vehicles
  7. 7.0 7.1 7.2 7.3 7.4 StarWars-DatabankII.png Imperial Star Destroyer in the Databank (backup link)
  8. 8.0 8.1 8.2 8.3 Star Wars: The Clone Wars film
  9. 9.0 9.1 9.2 9.3 9.4 9.5 TCW mini logo.jpg Star Wars: The Clone Wars – "Point of No Return"
  10. 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 Star Wars: Episode III Revenge of the Sith
  11. 11.0 11.1 TCW mini logo.jpg Star Wars: The Clone Wars – "Cargo of Doom"
  12. TCW mini logo.jpg Star Wars: The Clone Wars – "Jedi Crash"
  13. TCW mini logo.jpg Star Wars: The Clone Wars – "Gungan Attack"
  14. Star Wars Battlefront II
  15. 15.0 15.1 TCW mini logo.jpg Star Wars: The Clone Wars – "Nightsisters"
  16. 16.0 16.1 16.2 16.3 TCW mini logo.jpg Star Wars: The Clone Wars – "Storm Over Ryloth"
  17. TCW mini logo.jpg Star Wars: The Clone Wars – "Innocents of Ryloth"
  18. 18.0 18.1 Star Wars: The Rebel Files
  19. 19.0 19.1 19.2 19.3 TCW mini logo.jpg Star Wars: The Clone Wars – "Cat and Mouse"
  20. 20.0 20.1 20.2 20.3 Star Wars: On the Front Lines
  21. TCW mini logo.jpg Star Wars: The Clone Wars – "The Unknown"
  22. TCW mini logo.jpg Star Wars: The Clone Wars – "The Hidden Enemy"
  23. Star Wars: The Clone Wars film
  24. TCW mini logo.jpg Star Wars: The Clone Wars – "Supply Lines"
  25. Encyclopedia Malevolence in the Encyclopedia (content now obsolete; backup link)
  26. 26.0 26.1 TCW mini logo.jpg Star Wars: The Clone Wars – "Shadow of Malevolence"
  27. TCW mini logo.jpg Star Wars: The Clone Wars – "Destroy Malevolence"
  28. Star Wars: Rogue One: The Ultimate Visual Guide states that the Onderonian Civil War began 22 years before the Rogue One mission, and that it ended 19 years before the mission. Star Wars: Galactic Atlas dates the Rogue One mission to 0 BBY. Therefore, the Onderonian Civil War began in 22 BBY and ended in 19 BBY. Because the end of the war was depicted in "Tipping Points," the events of the episode must be set in 19 BBY. Star Wars: The Clone Wars Chronological Episode Order on (backup link) establishes that the events of "Point of No Return" take place after "Tipping Points" and before the events of "Eminence," which Star Wars: Galactic Atlas dates to 19 BBY. Therefore, the events of "Point of No Return" must take place in 19 BBY, which Galactic Atlas notes to be the final year of the Clone Wars.
  29. TCW mini logo.jpg Star Wars: The Clone Wars – "Missing in Action"
  30. TCW mini logo.jpg Star Wars: The Clone Wars – "Secret Weapons"
  31. 31.0 31.1 Star Wars: Complete Locations
  32. StarWars-DatabankII.png General Grievous in the Databank (backup link)
  33. Star Wars Lightsabers: A Guide to Weapons of the Force
  34. Amazon favicon.png Star Wars The Clone Wars Character Encyclopedia: Join the battle! on (backup link)
  35. TCW mini logo.jpg Star Wars: The Clone Wars – "Shattered"
  36. TCW mini logo.jpg Star Wars: The Clone Wars – "Victory and Death"
  37. 37.0 37.1 37.2 Star Wars Jedi: Fallen Order
  38. The events of Star Wars Jedi: Fallen Order take place about five years after the end of the Clone Wars, which Star Wars: Galactic Atlas dates to 19 BBY. Therefore, it can be deduced that the events of Star Wars Jedi: Fallen Order take place around 14 BBY.
  39. 39.0 39.1 The Art of Star Wars Jedi: Fallen Order
  40. Encyclopedia Imperial Star Destroyer in the Encyclopedia (content now obsolete; backup link)
  41. Catalyst: A Rogue One Novel
  42. Darth Vader 9
  43. Star Wars: Squadrons dates the game's main story to four years after the battle at Fostar Haven, which takes place shortly after the Disaster. As Star Wars: Galactic Atlas dates the destruction to 0 BBY, the main story must take place around 4 ABY.
  44. Star Wars: Squadrons
  45. Age of Resistance - Rey 1 takes place concurrently with Star Wars: Episode VII The Force Awakens, which Star Wars: Galactic Atlas places in 34 ABY.
  46. Age of Resistance - Rey 1
Galactic Republic starship classes
Space stations
DS-1 · FireStar II-class · Golan I · Haven-class · Starlight Beacon
Star Destroyers
Maelstrom-class · Venator-class (Venator I-class · Venator II-class) · Victory-class
Acclamator-class (Acclamator I-class · Acclamator II-class) · Dreadnought-class · Emissary-class · Pacifier-class
DP20 · MedStar-class · Pelta-class (Pelta-class Medical · Pelta-class strike · Pelta-class Transport) · Salvation-class
Light cruisers
Arquitens-class · Consular-class space (Consular-class Armed · Consular-class Charger c70)
Alderaanian diplomatic cruiser (CR70 corvette · CR90 corvette) · IPV-2C Stealth Corvette
AA-9 Freighter-Liner · CSS-1 · LH75 Low Orbit Specialty Live-Haul
Light craft
Eta-class · F-143 · G9 Rigger-class · GX1 short hauler · H-2 executive · HAET-221 · LAAT (LAAT/c · LAAT/i · LAAT/le · Space gunship) · Longbeam · Nu-class (Republic medical) · Republic executive · Republic space tug · T-6 · Theta-class T-2c · TUG-314 · Util-313
Starfighters & bombers
ARC-40b · ARC-170 · BTL-B Y-wing · Cord-class · Delta-series (Alpha-3 Nimbus-class V-wing (Alpha-3B "Besh" · Alpha-3E "Esk") · Delta-7 Aethersprite-class · Delta-7B Aethersprite-class · Eta-2 Actis-class) · SU-42RS Flashblind · V-19 Torrent · Z-28 Skywing · Z-95 Headhunter (Clone Z-95 Headhunter)
Escape pods
AO-1 orbital assault pod · Republic escape pod · Salon pod
Galactic Empire starship classes
Space stations
Class II · DS-1 · DS-2 · FireStar II-class · Golan I · Golan II · Golan III · Golan M3185 · Harbor-class · ICM-092792 · Imperial dockyard · Mk IX · Supertanker fuel depot
Star Dreadnoughts
Executor-class (Executor I-class · Executor II-class)
Assertor-class · Bellator-class · Mandator-class
Maelstrom-class · Secutor-class
Star Destroyers
Gladiator-class (Gladiator I) · Imperial-class (Imperial I-class · Imperial II-class) · qaz-class · Tector-class · Unidentified Interdictor vessel · Venator-class · Victory-class (Victory II-class)
Heavy cruisers
Dreadnought-class · Interdictor-class · Vindicator-class
Cantwell-class · Detainer CC-2200 · Immobilizer 418 · Onager-class
Active-class · CC-7700 · DP20 · EF76 Nebulon-B · IR-3F-class · Pelta-class (Pelta-class Medical) · Razor-class · Surveyor-class
Imperial escort carrier · Quasar Fire-class (Quasar Fire I-class · Quasar Fire II-class)
Light cruisers & corvettes
Arquitens-class command (Prison-tug) · Arquitens-class light · Carrack-class · Class 546 · Imperial Gozanti-class (Gozanti-class Assault · Gozanti-class espionage) · S-46I
Alderaanian diplomatic cruiser (CR90) · Raider-class (Raider I-class · Raider II-class)
Aerial landing platform · BFF-1 · Class four container · Eta-class · Theta-class · Xiytiar-class · Y-45 · Y-85 Titan
Light craft
Abecederian line (Delta-class T-3c · Lambda-class T-4a · T-5 Deliverance) · Action series (Action VI bulk freighter) · Assault gunboat · Escort gunboat · Harbinger courier · HAET-221 · Imperial Dropship Transport · Imperial heavy freighter · Imperial transport · Nu-class · Sentinel-class · Star Commuter 2000 · Stormtrooper transport · Theta-class T-2c · VT-49 Decimator · YT-2400 light freighter · Zeta-class Heavy Cargo · Zeta-class
Starfighters & bombers
Alpha-class Xg-1 · ARC-40b · ARC-170 · ARX-T3 Suncutter · Clone Z-95 · Delta-series (Alpha-3 Nimbus-class · Eta-2 Actis-class) ·
TIE line (Auto-fighter · Outland TIE · TIE Advanced v1 · TIE Advanced x1 · TIE Avenger · TIE fighter prototype · TIE lander · TIE scout · TIE training drone · TIE/ag "Aggressor" · TIE/ca "Punisher" · TIE/D "Defender" (TIE/D Defender Elite) · TIE/fc · TIE/gt · TIE/IN · TIE/LN · TIE/ph "Phantom" · TIE/rb "Brute" · TIE/rc · TIE/rp Reaper · TIE/sa · TIE/sh · TIE/sk "Striker" · TIE/sr) · XL-5 Guardian
Other classes
Imperial Planetary Occupation Facility · Praetor II-class
Star Destroyer classes
Star Dreadnoughts
Executor-class (Executor I-class · Executor II-class) · Mega-class
Maelstrom-class · Resurgent-class · Secutor-class
Imperial-class (Imperial I-class · Imperial II-class) · Venator-class (Venator II-class Star Destroyer)
Heavy cruisers
Acclamator-class (Acclamator I-class · Acclamator II-class) · Onager-class
Unknown designation
Gladiator-class (Gladiator I) · qaz-class · Tector-class · Unidentified Interdictor vessel · Victory-class (Victory II-class) · Xyston-class
Community content is available under CC-BY-SA unless otherwise noted.