Katharina CHRISTOWITZ
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Katharina CHRISTOWITZ |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 16.06.1689 (B | Pahnstangen
Find persons in this place |
|
birth | January 1627 | Löhma (Dragensdorf)
Find persons in this place |
|
marriage | 30. January 1655 | Pahnstangen
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
30. January 1655
Pahnstangen |
Johannes KNOCHE |
|
Notes for this person
Im Taufregister Löhma klafft zwischen 1626 und 1649 eine Lücke.
In zweiter Ehe heiratete Johannes Knoche am 30. Januar 1656 Katharina Christowitz: "Hans Knoche, Schultheiß, und Katharina Christowitz [aus] Löhma, contra 6. Praeceptum peccantes (?) copuliert." [Taufen,Trauungen, Beerdigungen Pahnstangen S.69,bei Archion S.88]
"Den 16. Januar [1689] ist Katharina Knochin, Hans Knochen hinterlassene Wittib, nebst einer Leichpre- digt begraben worden, aet[atis] 62 Jahre 22 Wochen und 2 Tage." [Taufen,Trauungen, Beerdigungen Pahnstangen S.97, bei Archion S.126]
Sources
1 | MyHeritage |
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 |
---|---|---|---|---|---|
Katharina CHRISTOWITZ | * 1627 Löhma (Dragensdorf) + Pahnstangen | 67026 | daßlerahnen | Werner Daßler | 2024-12-01 |
Katharina CHRISTOWITZ | * 1627 Löhma (Dragensdorf) + Pahnstangen | 67743 | daßlerahnen | Werner Daßler | 2025-04-26 |
files
Title | daßlerahnen |
Description | |
Id | 67741 |
Upload date | 2025-04-26 22:09:23.0 |
Submitter |
![]() |
werdas52@t-online.de | |
??show-persons-in-database_en_US?? |