The Verathans were a Gamma Quadrant civilization, now-extinct, who, at 30,000 years ago, reached their peak. Thier empire consisted of over 24 star systems, linked by an advanced communications and trade arrangement. Their history is divided into nineteen separate dynasties. (DS9: "Q-Less")


30,000 years ago, during the reign of their civilization, there was a Verathan event where massive offerings of flower pedals, native to their planet, were unloaded at one of their power-shrines. (Star Trek: Phoenix-X: "Department Heads")

Known statuesEdit

  • In 2410, Commander Barnes of Earth Spacedock attempted to share a Verathan sub-ossemite statue with Captain Aeris, which depicted it interacting with a baby ossemite. (The Adventures of Earth Spacedock!: Page 1) Captain Oroku Seifer would later acquire the same statue for his own study, where it was uncovered during his first meeting with his senior staff aboard the USS Ragnarok. There, the depiction of the baby was reported to be a "power source", as well as its head was identified as a bilitrium jewel; a highly powerful mineral. The sub-ossemite, one of three on the statue, was said to be a "power consumer", and when Seifer rotated the upper-half of the statue to align the third sub-ossemite's mouth with the baby, the statue began to emanate a low-level glow, and the baby's head began to emit hovering, short-range clumps of energized matter. This activation would have been fatal to the crew if not for the staff's quick-thinking of offering the statue a Saurian flower in place of a Verathan flower, to imitate the Verathan ritual, the result of which deactivated the statue. (Star Trek: Phoenix-X: "Department Heads")


  • Prime Ossemite
  • First Sub-Ossemite
  • Second Sub-Ossemite
  • Third Sub-Ossemite: The "power consumer"
  • Baby Ossemite: The "power source"

External linksEdit

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.