FANDOM


Tab-canon-black  Tab-legends-white 

Ringo Vinda was a planet around which a ring-shaped ring station had been built. During the Clone Wars, that world was aligned with the Confederacy of Independent Systems, and the space station was controlled by Admiral Trench[2] in 20 BBY.[3] It was there that Republic clone trooper Tup killed Jedi Master Tiplar,[2] due to a malfunctioning inhibitor chip causing him to prematurely execute Order 66. Supreme Chancellor Palpatine declared that Tup's inhibitor chip was infected with a rare parasite that lived on the planet.[4]

Behind the scenesEdit

Ring Planet

Concept art by Ryan Church

Ringo Vinda was a planet that first appeared in the Star Wars: The Clone Wars television series, although its design was derived from concept art meant for Star Wars: Episode III Revenge of the Sith.[5]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 SWCustom-2011 Star Wars: The Essential Atlas Online Companion on StarWars.com (article) (backup link on Archive.org)
  2. 2.0 2.1 2.2 TCW mini logo Star Wars: The Clone Wars – "The Unknown"
  3. The Official Star Wars Fact File Part 23 (PLO5–6, Clone Wars Ace Pilot) dates "Sabotage" to the final month of the Clone Wars, which The New Essential Chronology establishes as occurring in 19.1 BBY. The Official Star Wars Fact File Part 46 (20 BBY 61–64, Crisis on Scipio) dates "An Old Friend" to 20 BBY. Since SWCustom-2011 Star Wars: The Clone Wars Chronological Episode Order on StarWars.com (backup link on Archive.org) places "The Unknown" between those two episodes, it can be concluded that "The Unknown" also takes place in 19.1 BBY.
  4. TCW mini logo Star Wars: The Clone Wars – "Orders"
  5. SWCustom-2011 "The Unknown" - The Clone Wars Episode Guide on StarWars.com (backup link on Archive.org)

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.