Christoph Johann Hinrich BROCKMANN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Christoph Johann Hinrich BROCKMANN |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 19. December 1828 | Boerry 62, Ober Nieder Boerry Ksp, Grohnde Amt Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
burial | Boerry 62, Ober Nieder Boerry Ksp, Hameln Emmerthal Grohnde Amt, Hannover Fstm Calenberg
Find persons in this place |
||
birth | 31. December 1755 | Boerry 62, Ober Nieder Boerry Ksp, Grohnde Amt Hameln, Hannover Fstm Calenberg
Find persons in this place |
|
marriage | 22. November 1787 | ||
marriage | 27. November 1800 | Oberboerry Ksp , Hameln-Pyrmont Weser, Hannover
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
22. November 1787
|
Louise Sophie MEYER |
|
27. November 1800
Oberboerry Ksp , Hameln-Pyrmont Weser, Hannover |
Dorothee Louise LUECKE |
|
Notes for this person
#11881
Beruf:
Beibauer 62 und Schneidermeister in Börry~~Corporal im Hämelschen Land Regiment
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 |
---|---|---|---|---|---|
Christoph Johann Hinrich BROCKMANN | * 1755 Boerry 62, Ober Nieder Boerry Ksp, Grohnde Amt Hameln, Hannover Fstm Calenberg + 1828 Boerry 62, Ober Nieder Boerry Ksp, Grohnde Amt Hameln, Hannover Fstm Calenberg | 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?? |