The site of a failed Skagaran colony (later known as North Star) was established in the 19th century as colony for the Skagarans in the Delphic Expanse.


In addition to Skagaran colonists, the colony had a population of Humans who had been kidnapped from the north-western United States of America in 1853 and were intended to serve as a slave or worker class. The humans led by a man named Cooper Smith led a rebellion against the Skagarans. The humans killed the many Skagarans, their women, children and their ship. The humans then became the dominant species of the colony after rebellion .(ST reference: Star Trek Encyclopedia; ENT episode: "North Star")

The colony was discovered by the Enterprise (NX-01) in 2153 when the ship was seeking to locate the Xindi who had recently attacked Earth. Upon its discovery by the Enterprise, the colony had a population of about 1,000 Skagarans and 6,000 Humans who resided in several settlements or towns all within a day or two's journey of each other. As its inhabitants had been isolated from Earth for centuries, the technology of the colony was still rooted in the 19th century. Moreover, settlements were reminiscent of the old west in the the United States. The planet on which the colony was located had a dry climate, similar to the North American southwest. (ENT episode: "North Star")

Sometime after the encounter with Enterprise in 2153, the colony had been named North Star by the inhabitants. By the 2380s, the North Star colony had established contact with the Federation, with one of the inhabitants, Ethan Kyzak, having joined Starfleet. (TTN novel: Sight Unseen)

Vulcan This article is a stub relating to a planet, moon or planetoid. You can help our database by expanding on it.

External Link Edit

Skagaran colony article at Memory Alpha, the wiki for canon Star Trek.

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.