Christian KLEIN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Christian KLEIN |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 6. April 1840 | ||
residence | 1796 | Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
residence | 1840 | Allendorf, Stadt Haiger, Lahn-Dill-Kreis
Find persons in this place |
|
birth | 2. September 1768 | Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
marriage | 1. July 1796 | Feudingen, Kreis Wittgenstein
Find persons in this place |
|
marriage | 12. February 1805 |
Parents
Peter KLEIN | Luise GRUND |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
1. July 1796
Feudingen, Kreis Wittgenstein |
Elisabeth BODE |
|
12. February 1805
k |
Elisabeth SCHIRMULI |
|
Notes for this person
Familienname: Klein
Weitere Namen: Johann Christ
Vorname (kurz): JChrn
Name (kurz): Chrn Klein
Freier Text: P Fdg 1795 JSchuppener
Paten: JChrn Roth; Johs Sv HJakob Grund; Kath Tv Johs [?= Henr] Danzenbächer +; alle Ban
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 |
---|---|---|---|---|---|
Christian KLEIN | * 1768 Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland + 1840 | 60870 | Projekt “Rothenpieler” | Michael | 2025-01-01 |
files
Title | Online-OFB "Wittgensteiner Land" |
Description | Backup von https://online-ofb.de/wittgenstein |
Id | 60894 |
Upload date | 2022-05-15 19:34:29.0 |
Submitter |
![]() |
mj-genealogy@gmx.de | |
??show-persons-in-database_en_US?? |