FANDOM


Greskrendtregk
Greskrendtregk DS9 RichB
Vital statistics
Position Ensign
Age Unknown
Status Active 2378
Physical attributes
Height Unknown
Weight Unknown

Greskrendtregk was a male Ktarian and a member of Starfleet who held the rank of ensign in 2371. Greskrendtregk was stationed on Deep Space 9. He was married to Ensign Samantha Wildman who was stationed on the USS Voyager. Greskrendtregk and Samantha had been visiting Doctor Julian Bashir on DS9 in the hopes that he would be able to aid them in getting pregnant. The treatments were successful - Samantha was (unknowingly) pregnant when she left DS9 aboard Voyager in 2371. Voyager was then stranded in the Delta Quadrant where Samantha subsequently gave birth to their child, Naomi Wildman in 2372.

Samantha had considered naming her child after Greskrendtregk, had the child been a son; the name is an honored one in his family (he was the fifth generation male of his family line to have that name).

In 2372 on the one-year anniversary of the disappearance of Voyager, Greskrendtregk, who went by the name "Gres" organized a get-together of families and close friends of the crew of Voyager. The get together was held on DS9. By the second anniversary in 2373, Gres had taken a sixth month leave of absence from Starfleet and was living on Ktar where the second anniversary get-together was held. A year later, Gres was back on DS9 where he hosted the third anniversary get-together.

In 2374, Gres, along with all of the families of the Voyager crew, heard the news that Voyager had survived and was stranded in the Delta Quadrant. Gres again planned an anniversary party, but it would be held on the anniversary of the day they found out their loved ones were still alive.

In 2378, Gres was reunited with his wife Samantha and met his daughter Naomi for the first time when Voyager returned to Earth.

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.