FANDOM


Kap-Dwa

Kap Dwa is an ancient, mummified two headed Patagonian giant that originally originated in the jungles of Argentina, South America. The creature's legend begins in 1673, where the giant of over 12 feet with two heads, was captured by Spanish sailors and set captive on their ship. The Spaniards lashed him to the mainmast, but he broke free (being a giant) and during the ensuing battle suffered a fatal injury; they skewered him through the chest with a pike.

What happened to him next isn’t exactly clear, but his naturally mummified remains were eventually brought to England in the 19th century. He then entered the Edwardian Horror Circuit and over the years was passed from showman to showman, eventually ending up at Weston’s Birnbeck Pier in 1914. After spending the next 45 years on display in North Somerset, England, old Kap Dwa was purchased by one “Lord” Thomas Howard in 1959, and following a few more hand-offs he ultimately ended up in Baltimore, MD, of all places. He now rests in the bizarre collection of oddities that is Bob’s Side Show at The Antique Man Ltd in Baltimore, owned by Robert Gerber and his wife. The mummified remains of Kap-Dwa is believed to be a fabricated hoax, although it is still a mystery.

Similar Sightings

Sebalt de Weert (May 2, 1567 – May 30 or June 1603) was a Dutch captain associated with the exploration of the coasts of South America and the Falkland Islands south of Argentina. De Weert and several crew claimed to have seen members of a “race of giants” while there. De Weert described a particular incident when he was with his men in boats rowing to an island in the Magellan Strait. The Dutch claimed to have seen seven odd-looking boats approaching with were full of naked giants. These giants supposedly had long hair and reddish-brown skin and were aggressive towards the crew.

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.