Tab-canon-white  Tab-legends-black 
"I need you to convince the Senate, or the Jedi Council, or whoever is in charge of this terrible war that we are threatened."
―Queen Neeyutnee, to Padmé Amidala[src]

Neeyutnee was a human female who served as the Queen of Naboo during the fall of the Galactic Republic. She was elected to the throne during the pan-galactic conflict known as the Clone Wars, succeeding Jamillia as head of the Royal House of Naboo. During her time in office, one of Neeyutnee's advisers was Padmé Amidala, a former queen who went on to represent the people of Naboo as their senator in the Galactic Senate.

Char-stub This article is a stub about a character. You can help Wookieepedia by expanding it.


Neeyutnee succeeded Jamillia as Queen of Naboo following the outbreak of the Clone Wars.[2]

The Clone WarsEdit

During this time, Neeyutnee moved the fighter operations out of the palace as a security measure.[3]

When battle droids were discovered and captured in the grassy wetlands, Neeyutnee recalled Senator Padmé Amidala and Representative Jar Jar Binks to Naboo and implored them to convince the Senate or the Jedi Council to assist Naboo against this threat. Neeyutnee then listened as Amidala's protocol droid, C-3PO, interrogated the tactical droid before Binks inadvertently destroyed it. However, they were able to deduce that the droids came from the Eastern swamps. They then contacted Masters Yoda and Windu and told them that they believed the Separtists were planning an attack on Naboo.[1]

Following the crisis,[4] Neeyutnee asked Amidala and her Jedi protector, Anakin Skywalker, to assist Binks in talking sense into Boss Lyonie and the Gungan Grand Army.[5]

By the end of the Clone Wars, Apailana succeeded Neeyutnee as Queen of Naboo.[6]



Notes and referencesEdit

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.