Hermann HUTTEN
Characteristics
| Type | Value | Date | Place | Sources |
|---|---|---|---|---|
| name | Hermann HUTTEN |
|
||
| occupation | Tuchhändler | Jülich und Leipzig
Find persons in this place |
|
Events
| Type | Date | Place | Sources |
|---|---|---|---|
| death | 6. February 1629 | Leipzig
Find persons in this place |
|
| burial | 9. February 1629 | Leipzig
Find persons in this place |
|
| birth | 9. March 1563 | Morßdorf7Jülich
Find persons in this place |
|
| marriage | 1593 | Leipzig
Find persons in this place |
|
| marriage | 1606 | Leipzig
Find persons in this place |
??spouses-and-children_en_US??
| Marriage | ??spouse_en_US?? | Children |
|---|---|---|
|
1593
Leipzig |
Regina KNÄSPE |
|
|
1606
Leipzig |
Anna CALMBERG |
|
Notes for this person
wahrscheinliche Schwetsr Catherina s. Roth 154
Sources
| 1 | Leichenpredigten Görlitz Sig. 331 und 349
Abbreviation: Leichenpredigten Görlitz Sig. 331 und 349
|
| 2 | LP Braunschweig 859 (323 a)
Abbreviation: LP Braunschweig 859
|
Unique identifier(s)
GEDCOM provides the ability to assign a globally unique identifier to individuals. This allows you to find and link them across family trees. This is also the safest way to create a permanent link that will survive any updates to the file.
Identical Persons
GEDBAS contains copies of this person (probably submitted by other researchers). This list is based on the UID feature of GEDCOM.
| Name | Details | files | Title | ??submitter_en_US?? | Upload date |
|---|---|---|---|---|---|
| Hermann HUTTEN | + 1629 | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
| Hermann HUTTEN | * 1563 Morßdorf7Jülich + 1629 Leipzig | 66574 | Thomas Von Ryssel | 2024-08-04 | |
| Hermann HUTTEN | * 1563 Morßdorf7Jülich + 1629 Leipzig | 60258 | Familie von Rysel | Thomas Von Ryssel | 2021-01-31 |
files
| Title | Johann 2024 |
| Description | Familie von Ryssel |
| Id | 66573 |
| Upload date | 2024-08-04 11:47:57.0 |
| Submitter |
Thomas Von Ryssel
visit the user's profile page
|
| vonrysselthomas@gmail.com | |
| ??show-persons-in-database_en_US?? | |