Becke DRIELING
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Becke DRIELING |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 14. November 1742 | Lilienthal, Hannover, Germany
Find persons in this place |
|
birth | 15. July 1741 | Lilienthal, Hannover, Germany
Find persons in this place |
Parents
Christoffer DRIELING | Gesche |
Sources
1 | FamilySearch Stammbaum, https://www.myheritage.de/research/collection-40001/familysearch-stammbaum?itemId=545048833&action=showRecord
Publication: MyHeritage
|
Becke Drieling<br>Geschlecht: weiblich<br>Geburt: 15. Jul. 1741 - Lilienthal,Hannover,Germany<br>Tod: 14. Nov. 1742 - Lilienthal,Hannover,Germany<br>Eltern: Christoffer Drieling, Gesche Drieling<br>Geschwister: Johann Hinrich Drieling, Harm Drieling, Christoffer Drieling, Anna Margaretha Drieling, Boulcke Drieling, Geffken Drieling, Drieling, Lewe Agnese Boese (geb. Drieling), Thomas Drieling Der FamilySearch Stammbaum wird duch MyHeritage unter Lizenz von FamilySearch International, der weltgrössten Genealogie Organisation, veröffentlicht. FamilySearch ist eine nonprofit Organisation gesponsert von der Kirche Jesu Christi der Heiligen der Letzten Tage (Mormonen Kirche). |
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 |
---|---|---|---|---|---|
Becke DRIELING | * 1741 Lilienthal, Hannover, Germany + 1742 Lilienthal, Hannover, Germany | 59056 | Heike Volk | 2020-09-01 |
files
Title | Bogenschuetz Vorfahren |
Description | |
Id | 44294 |
Upload date | 2020-06-28 17:33:19.0 |
Submitter |
![]() |
heike.e.volk@gmail.com | |
??show-persons-in-database_en_US?? |