Jochem HEGEN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Jochem HEGEN |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 4. November 1600 | Mittweida
Find persons in this place |
|
birth | about 1530 | Schema
Find persons in this place |
|
marriage | about 1553 | ||
marriage | 27. April 1578 |
Parents
Hans HEGEN | Margreta NN |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
about 1553
|
Margret POLMER |
|
27. April 1578
|
Lindacher MARGARETA |
|
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 |
---|---|---|---|---|---|
Jochem HEGEN | * 1530 Schema + 1600 Mittweida, Erzg. | 50977 | Georgi Klein | Georg Klein | 2016-06-23 |
Jochem HEGEN | * 1530 Schema + 1600 Mittweida, Erzg. | 50979 | Georgi Klein | Georg Klein | 2016-06-23 |
Jochem HEGEN | * 1530 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland + 1600 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland | 56180 | Georg Klein | 2019-01-12 | |
Jochem HEGEN | * 1530 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland + 1600 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland | 56179 | Georg Klein | 2019-01-12 | |
Jochem HEGEN | * 1530 Schema + 1600 Mittweida, Erzg. | 50978 | Georgi Klein | Georg Klein | 2016-06-23 |
Jochem HEGEN | * 1530 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland + 1600 Sehmatal-Sehma, Erzgebirgskreis, Sachsen, Deutschland | 56181 | Georg Klein | 2019-01-12 |
files
Title | Fam Klein-Georgi |
Description | |
Id | 36364 |
Upload date | 2014-12-16 16:24:27.0 |
Submitter |
![]() |
gcklein@t-online.de | |
??show-persons-in-database_en_US?? |