Sophie Marie Dorette HADELER
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Sophie Marie Dorette HADELER |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 29. October 1992 | Stolzenau, Stolzenau civ no 160, Stolzenau, Hannover Grfsch Hoya
Find persons in this place |
|
birth | 25. May 1902 | Steyerberg, Steyerberg Riessen Ksp, Nienburg Amt, Hannover Fstm Verden
Find persons in this place |
|
marriage | 14. May 1928 | Anemolter, Schinna civ no 4 Ksp, Stolzenau Amt, Hannover Grfsch Hoya
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
14. May 1928
Anemolter, Schinna civ no 4 Ksp, Stolzenau Amt, Hannover Grfsch Hoya |
Heinrich Friedrich Wilhelm BROCKMANN |
|
Notes for this person
Name: Sophie Marie Dorette Hadeler
Gender: weiblich (Female)
Birth Date: 25 Mai 1902 (25 May 1902)
Birth Place: Steyerberg, Niedersachsen (Lower Saxony), Deutschland (Germany)
Civil Registration Office: Steyerberg
Father: Diedrich Heinrich Albert Hadeler
Mother: Annna Marie Dorette Hadeler
Certificate Number: 18
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 |
---|---|---|---|---|---|
Sophie Marie Dorette HADELER | * 1902 Steyerberg, Steyerberg Riessen Ksp, Nienburg Amt, Hannover Fstm Verden + 1992 Stolzenau, Stolzenau civ no 160, Stolzenau, Hannover Grfsch Hoya | 54637 | BrockmannFamilien | Ingo Brockmann | 2024-12-29 |
files
Title | Brockmann |
Description | Brockmann Familien |
Id | 67273 |
Upload date | 2025-04-27 23:30:32.0 |
Submitter |
![]() |
ingobrockmann@yahoo.de | |
??show-persons-in-database_en_US?? |