Fandom

Wookieepedia

CS-321

134,554pages on
this wiki
Add New Page
Talk0 Share
Tab-canon-white  Tab-legends-black 

CS-321 was a tan-colored RA-7 protocol droid that was owned by Weequay pirates during the Clone Wars, a war between the Galactic Republic and the breakaway Confederacy of Independent Systems. He was destroyed during a battle between the two parties.

BiographyEdit

"Soon it will be us."
―CS-321 to C-3PO about fighting K0-5D[src]

At some point during the Clone Wars, CS-321 was captured by a band of Weequay pirates.[2] Over 1 year into the war,[1] CS-321 was present on the pirate ship Marauder watching a droid gladiatoral fight when two droids, R2-D2 and C-3PO, who had been captured on Balnab, were sent aboard the pirate ship. CS-321, R2-D2 and C-3PO observed the fight where the warrior K0-5D was competing against other droids. Artoo and Threepio were about to be sent into the ring when the Marauder was targeted by General Grievous and the Separatists for target practice. A laser blast ripped open the Marauder causing all aboard the to be sucked into space, the droids were captured by the Separatists and sent to be incinerated, CS-321 refused to be incinerated and was killed by battle droids.[2]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

  1. 1.0 1.1 According to Tarkin, the events of "The Citadel" occur a year after a battle on Murkhana, which itself took place nine months after the Battle of Geonosis. As a result, "The Citadel" takes place one year and nine months into the Clone Wars. Since SWCustom-2011 Star Wars: The Clone Wars Chronological Episode Order on StarWars.com (backup link on Archive.org) places "Nomad Droids" after "The Citadel," it can be concluded that "Nomad Droids" also takes place over a year into the war.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 TCW mini logo Star Wars: The Clone Wars – "Nomad Droids"

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.