Duke Zoltan (of Hungary)1
M, #1051037, b. about 896, d. 949
Father* | Prince Arpad (of the Magyars)1 b. bt 811 - 880?, d. 907 |
Relationship | 35th great-grandfather of Robert Michael Damon |
Reference | RFC051-37 |
Duke Zoltan (of Hungary) was born about 896.1 He was the son of Prince Arpad (of the Magyars).1 Duke Zoltan (of Hungary) married (?), daughter of Prince Mariot (Maroth) (of the Bikar Khazars).1 Duke Zoltan (of Hungary) died in 949.1
He became Duke Hungary.2 Zoltan's father Prince Arpad (of the Magyars) died in 907.1 Duke Zoltan (of Hungary) became the father of Prince Taksony (of Hungary) in 931.1 Duke Zoltan (of Hungary) was the Magyar leader in the invasion of western and sourther Europe, was defeated by the Saxons near Merseburg, Germany, in 933.1 Zoltan's son Prince Taksony (of Hungary) was married to (?) in 947.1
He became Duke Hungary.2 Zoltan's father Prince Arpad (of the Magyars) died in 907.1 Duke Zoltan (of Hungary) became the father of Prince Taksony (of Hungary) in 931.1 Duke Zoltan (of Hungary) was the Magyar leader in the invasion of western and sourther Europe, was defeated by the Saxons near Merseburg, Germany, in 933.1 Zoltan's son Prince Taksony (of Hungary) was married to (?) in 947.1
Child of Duke Zoltan (of Hungary) and (?), daughter of Prince Mariot (Maroth) (of the Bikar Khazars), |
|
Child |
|
Charts | Pedigree of Robert Damon (Big) Royalty for Commoners Royalty for Commoners (Indented) |
Last Edited | 9 Aug 2020 |
Citations
- [S7] Roderick W. Stuart, Royalty for Commoners, Fourth Edition, The Complete Known Lineage of John of Gaunt, Son of Edward III, King of England, and Queen Philippa (Baltimore, MD: Genealogical Publishing Co. Inc, 2002). Repository: Richard Smith Damon Arlington, Middlesex County, Massachusetts, in. Hereinafter cited as Royalty for Commoners, 4th Edition.
- [S31] Roderick W. Stuart, Royalty for Commoners, Third Edition (Baltimore, MD: Genealogical Publishing Co., Inc., 1998). Repository: Winchester Library Winchester, Middlesex County, Massachusetts, in. Hereinafter cited as RFC **** Check RFC4 ****.