FANDOM


Utapau
Astrographical
Region

Outer Rim Territories

Sector

Tarabba sector

System

Utapau system

Suns

1: Utapau]

Moons

9 (including Utapau 7)

Coordinates

N-19

Distance from Core

51,000 light years

Rotation period

27 standard hours

Orbital period

351 local days

Physical
Class

Terrestrial

Diameter

12,900 kilometers

Atmosphere

Type 1

Climate

Temperate, windy and arid

Gravity

Standard

Primary terrain
  • Scrublands
  • Savanna
  • Canyons
  • Sinkholes
  • Desert surface
  • Grottoes
  • Underground oceans
Surface water

Less than 0.9%

Points of interest
  • Grottoes of Coranth
  • Imperial storehouses
  • Promenade of Seven Guilds
  • Pahum Cultural Center
Societal
Native species
Official language
  • Utapese
  • Utai language
  • Galactic Basic Standard
Population

95 million

  • 30% (28,500,000) Pau'ans
  • 70% (66,500,000) Utai
Major cities

Pau City (capital)

Major imports
  • Medicine
  • Technology
  • Foodstuffs
Major exports
  • Water
  • Ore
  • Starships
Affiliation
  [Source]

Utapau was a planet in the outer rim, located in the Tarabba Sector near Dagobah. It was covered in sinkholes that were filled with communities and cities. Utapau was also one of the locations of a key battle in the Clone Wars, where Obi-Wan Kenobi led the attack and killed the Separatist general, Grievous.

Star Wars: Battlefront IIEdit

In Star Wars: Battlefront II Utapau looks a much like the way it looks like in Star Wars: Episode III: Revenge of the Sith, with many of the key areas seen being present. Vehicles on the planet include AAT battle tanks, AT-RTs and IFT-Ts. Some areas are very open but there are also many chokepoints making it a challenging environment fight in, especially when choosing a class.

AppearancesEdit

Manaan eaw This article is a stub about a planet. You can help SWGames by expanding it.

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.