FANDOM


Neebo
Neebo
Biographical Information
HomeworldRodia
Died22 BBY, Sanjin
Physical Description
SpeciesRodian
GenderFemale
Hair colorRed
Skin colorGreen
Chronological and Political Information
EraRise of the Empire Era
Affiliation
  • Old Jedi Order
  • Old Galactic Republic
  • Grand Army of the Republic

  • Neebo was a Rodian female Jedi Master who served the Old Jedi Order during the last decades of the Old Galactic Republic. During the Clone Wars, Neebo went missing on a mission to the moons of Sanjin, and her lightsaber was later found by Jedi Master Kit Fisto in the castle of the Separatist General Grievous, a famed Jedi killer.

    BiographyEdit

    Neebo was a Force-sensitive female Rodian wh owas brought to the Jedi Temple on Coruscant where she would learn the ways of the Force during the last decades of the Galactic Republic. After passing every trial that every Jedi did, Neebo would eventually attain the rank of Jedi Master. In 22 BBY, when the Clone Wars started, Neebo went on a mission to protect refugees on the moons of the Colonies planet Sanjin. Neebo went missing in the conflict, and was killed by Confederate cyborg General Grievous—who would often collect the weapons of Jedi he had killed. After her death, Jedi Master Kit Fisto later found Neebo's lightsaber in Grievous' trophy room during his mission to the third moon of Vassek. After infiltrating General's castle, Fisto examined Neebo's weapon and then went on to duel Grievous.

    Behind the scenesEdit

    Neebo was first mentioned in The Complete Star Wars Encyclopedia, released on December 9, 2008. She was later referenced in the corresponding episode guide for "Lair of Grievous," part of the first season of the Star Wars: The Clone Wars television series, which aired on December 12, 2008.

    AppearancesEdit

    SourcesEdit

    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.