Dirk Janssen CORDES
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Dirk Janssen CORDES |
[2]
|
||
religion | LU |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 21. February 1809 | Neuefehn
Find persons in this place |
[3]
|
baptism | 6. January 1749 | Neuefehn
Find persons in this place |
[4]
|
residence | Niedersachsen, Deutschland
Find persons in this place |
[5]
|
|
burial | 28. February 1809 | Neuefehn
Find persons in this place |
|
birth | 5. January 1749 | Neuefehn
Find persons in this place |
|
marriage | 28. April 1773 | Timmel
Find persons in this place |
Parents
Jan Jacobs CORDES | Ahlke DIRKS |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
28. April 1773
Timmel |
Frauke HINRICHS |
|
Sources
1 | Ancestry Family Trees, Ancestry Family Tree
Publication: Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members.
|
2 | Germany, Lutheran Baptisms, Marriages, and Burials, 1500-1971
Author: Ancestry.com
Publication: Ancestry.com Operations, Inc.
|
3 | |
4 | |
5 | East Frisia, Germany, Fire Insurance Registration, 1768-1937
Author: Ancestry.com
Publication: Ancestry.com Operations, Inc.
|
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 |
---|---|---|---|---|---|
Dirk Janssen CORDES | * 1749 Neuefehn + 1809 Neuefehn | 44185 | RudolfOnken2013 | Rudolf Onken | 2013-12-23 |
files
Title | Onken/Trauernicht in Großefehn |
Description | |
Id | 65883 |
Upload date | 2024-02-08 11:26:04.0 |
Submitter |
![]() |
rudolfonken184@gmail.com | |
??show-persons-in-database_en_US?? |