Christian Ehrenreich JUC BERLICH
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Christian Ehrenreich JUC BERLICH |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 2. October 1659 | Leipzig
Find persons in this place |
|
birth | 18. November 1629 | Leipzig
Find persons in this place |
|
Ratsherr | |||
marriage | 30. October 1655 | Leipzig
Find persons in this place |
Parents
Burchard JCtus BERLICH | Maria ANSHELM |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
30. October 1655
Leipzig |
Catherina HEINTZE |
|
Notes for this person
ohne Kinder
Sources
1 | https://familysearch.org/pal:/MM9.3.1/TH-1951-24489-25503-27?cc=1952871&wc=14011011
Abbreviation: https://familysearch.org/pal:/MM9.3.1/TH-1951-24489-25503-27?cc=1952871&wc=14011011
|
2 | Nachkommen des Lucas Cranachas d.Ä. Teil I
Abbreviation: Nachkommen des Lucas Cranachas d.Ä. Teil I von Gero von Wilke
|
3 | Roth 9681
Abbreviation: Roth 9681
|
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 Ehrenreich JUC BERLICH | * 1629 Leipzig + 1659 Leipzig | 66574 | Thomas Von Ryssel | 2024-08-04 | |
Gottfried Ehrenreich JUC BERLICH | * 1629 Leipzig + 1659 Leipzig | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
Gottfried Ehrenreich JUC BERLICH | * 1629 Leipzig + 1659 Leipzig | 60258 | Familie von Rysel | Thomas Von Ryssel | 2021-01-31 |
files
Title | Johann 2024 |
Description | Familie von Ryssel |
Id | 66573 |
Upload date | 2024-08-04 11:47:57.0 |
Submitter |
![]() |
vonrysselthomas@gmail.com | |
??show-persons-in-database_en_US?? |