Johann Heinrich FALCKE
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Johann Heinrich FALCKE |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 1. March 1843 | Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg
Find persons in this place |
|
burial | 4. March 1843 | Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg
Find persons in this place |
|
birth | 1770 | Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg
Find persons in this place |
|
marriage | 21. July 1805 | Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
21. July 1805
Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg |
Maria Dorothea Carolina BROCKMANN |
|
Notes for this person
gest. 1. März, Schwäche. alt im 73Jahre, begr. 4. März, arm.
Wittwer, Schneider Heinrich Falcke war verheirathet mit Caroline Brauckmann.
Wallensen
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 |
---|---|---|---|---|---|
Johann Heinrich FALCKE | * 1770 Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg + 1843 Wallensen, Wallensen Ksp, Amt Lauenstein Coppenbruegge, Hannover Fstm Calenberg | 54637 | BrockmannFamilien | Ingo Brockmann | 2024-12-29 |
files
Title | Brockmann |
Description | Brockmann Familien |
Id | 67273 |
Upload date | 2025-05-02 21:56:48.0 |
Submitter |
![]() |
ingobrockmann@yahoo.de | |
??show-persons-in-database_en_US?? |