Fandom

Familypedia

Georg Ludwig von Nassau-Dillenburg (1618-1656)

225,182pages on
this wiki
Add New Page
Talk0 Share

Biography

Georg Ludwig von Nassau-Dillenburg was born 4 March 1618 in Beilstein, Hesse, Germany to Ludwig Heinrich von Nassau-Dillenburg (1594-1662) and Katharina zu Sayn-Wittgenstein (1588-1651) and died 19 May 1656 in Dillenburg, Hesse, Germany of unspecified causes. He married Anna Auguste von Braunschweig-Wolfenbüttel (1612-1673) 8 April 1638 in Coppenbrügge, Lower Saxony, Germany. Notable ancestors include Henry II of England (1133-1189), William I of England (1027-1087), Charlemagne (747-814), Hugh Capet (c940-996), Alfred the Great (849-899), Rurik (c832-879). Ancestors are from Germany, the Netherlands, France, the United Kingdom, Belgium, Belarus, Russia, Ukraine, Poland, Austria, Lithuania, Bohemia, Slovakia, Slovenia, Spain, Portugal, Italy, Switzerland, the Czech Republic, Hungary, England, Turkey.




Children


Offspring of Georg Ludwig von Nassau-Dillenburg and Anna Auguste von Braunschweig-Wolfenbüttel (1612-1673)
Name Birth Death Joined with
Elisabeth Katharine von Nassau-Dillenburg (1639-1641)
Sofie Eleonore von Nassau-Dillenburg (1640-1712)
Heinrich von Nassau-Dillenburg (1641-1701) 28 August 1641 Dillenburg, Hesse, Germany 18 April 1701 Schloß Ludwigsbrunn Dorothea Elisabeth von Schlesien-Liegnitz (1646-1691)

Charlotte Elisabeth von Nassau-Dillenburg (1643-1686)
Son von Nassau-Dillenburg (1645-1645)
Anna Katharine von Nassau-Dillenburg (1652-1670)
Luise Elisabeth von Nassau-Dillenburg (1652-1670)


Common ancestors of Georg Ludwig von Nassau-Dillenburg (1618-1656) and Anna Auguste von Braunschweig-Wolfenbüttel (1612-1673)

  1. Magnus II. zu Mecklenburg (1441-1503)
  2. Sophie von Pommern (1468-1504)



Footnotes (including sources)

‡ General

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.