Dorothee Marie Wilhelmine DEHNE
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Dorothee Marie Wilhelmine DEHNE |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 30. August 1872 | Hajen 48 Koetner, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
burial | 2. September 1872 | Hajen 48 Koetner, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
birth | 26. January 1802 | Hajen 48 Koetner, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
VZHannover1855 | 3. December 1855 | Hajen no 48, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
marriage | 11. May 1834 | Hajen, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg
Find persons in this place |
Parents
Friedrich Johann DEHNE |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
11. May 1834
Hajen, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg |
Friedrich Wilhelm Dietrich BROCKMANN |
|
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 |
---|---|---|---|---|---|
Dorothee Marie Wilhelmine DEHNE | * 1802 Hajen 48 Koetner, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg + 1872 Hajen 48 Koetner, Hajen Ksp, Grohnde Ohsen Hameln, Hannover Fstm Calenberg | 54637 | BrockmannFamilien | Ingo Brockmann | 2024-12-29 |
files
Title | Brockmann |
Description | Brockmann Familien |
Id | 67273 |
Upload date | 2025-06-01 22:21:43.0 |
Submitter |
![]() |
ingobrockmann@yahoo.de | |
??show-persons-in-database_en_US?? |