Ludwig Johann Heinrich Wilhelm BROCKMANN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Ludwig Johann Heinrich Wilhelm BROCKMANN |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz
Find persons in this place |
||
birth | 14. October 1907 | Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz
Find persons in this place |
|
marriage | 15. December 1932 | Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
15. December 1932
Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz |
Erna Sophie KNUEPLING |
|
Notes for this person
äutigam
Name: Brockmann Stand: Geb. oder Alter: 14.10.1907 Geb. oder Herkunftsort: Aschen
Vorname: Ludwig Johann Heinrich Wilhelm
Heirat
Heirat am: 15.12.1932 in Aschen Registernummer : 9 / 1932
Braut
Name: Knüpling Geburtsname: Geb. oder Alter: 17.09.1912 Geb. oder Herkunftsort: Jacobidrebber
Vorname: Erna Sophie
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 |
---|---|---|---|---|---|
Ludwig Johann Heinrich Wilhelm BROCKMANN | * 1907 Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz + Aschen, Mariendrebber Ksp, Diepholz Amt, Hannover Grfsch Diepholz | 54637 | BrockmannFamilien | Ingo Brockmann | 2024-12-29 |
files
Title | Brockmann |
Description | Brockmann Familien |
Id | 67273 |
Upload date | 2025-05-04 22:24:13.0 |
Submitter |
![]() |
ingobrockmann@yahoo.de | |
??show-persons-in-database_en_US?? |