Fandom

Memory Beta, non-canon Star Trek Wiki

IRW Elieth

49,015pages on
this wiki
Add New Page
Talk0 Share

The IRW Elieth was a Romulan Mogai-class heavy warbird starship in service to the Tal Shiar in the early 25th century. (STO - "Romulan Mystery" missions: "By Any Means", "Desperate Measures")

HistoryEdit

In 2409, the Tal Shiar coerced the civilian scientists at Gasko Station to research Borg technology. The Elieth was one of four Mogai-class warbirds outfitted with the technology. The Elieth and its sister ships, IRW Bloodfire, IRW Taseiv and IRW Tyrava were destroyed by a Starfleet starship, and the critical Borg research was purged from Gasko Station's computer by the lead scientist. (STO - "Romulan Mystery" mission: "Desperate Measures")

Alternate eventsEdit

Elieth was one four Mogai-class starships docked at Dimorus Station in the Dimorus system in 2409. When the station came under attack from a Starfleet vessel hunting down the Star Empire's Borg research, the crew attempted to quickly reactivate the ship while the prototype of a Borg-adapted Mogai, the IRW Esemar, engaged the Starfleet ship. All Mogai-class warbirds in the system were subsequently destroyed by the victorious Starfleet ship. (STO - "Romulan Mystery" mission: "By Any Means")

AppendicesEdit

ConnectionsEdit

Mogai/Norexan-class starships
Romulan Star Empire, Romulan Star Navy Aj'rmrAreinnye • (Bloodfire) • DekkonaDominusEletrixEliethEsemarFraireIntrakhuKerasKovalKytonisMakarRohallhikSoterusTaseivTerrinexTyravaValdore

Valdore-subclass: Aethra • (Stormcrow)

RomulanEmblem
Reman Resistance Valdore-subclass: Zdenia RemanEmblem
Romulan Star Empire (mirror universe) Valdore RomulanEmblem
Galactic Commonwealth, Starfleet (mirror universe) (Excalibur)
Parenthesis indicates Human translation or non-Romulan language renaming.

External linkEdit

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.