Christoph KRUMBHOLTZ
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Christoph KRUMBHOLTZ |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | after 9. March 1579 | Joachimsthal
Find persons in this place |
|
baptism | 12.07.1537
Find persons in this place |
||
birth | 12. July 1537 | ||
Ratsverw. und Bergmeister | Joachimsthal
Find persons in this place |
||
marriage | 14. January 1560 |
Parents
Sebastin KRUMBHOLTZ |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
14. January 1560
Geyer |
Judith RÖHLING |
|
Sources
1 | Ein Beitrag zur erzgebirgischen Familienkunde S. 217
Abbreviation: Ein Beitrag zur erzgebirgischen Familienkunde S. 217
|
2 | https://www.familysearch.org/ark:/61903/3:1:3Q9M-CS2N-WHKT?i=6&cat=2789818
Abbreviation: https://www.familysearch.org/ark:/61903/3:1:3Q9M-CS2N-WHKT?i=6&cat=2789818
|
3 | Röhling.Pdf
Abbreviation: Röhling.pdf
|
4 | Roth 1179
Abbreviation: Roth 1179
|
5 | Roth 1182
Abbreviation: Roth 1182
|
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 KRUMBHOLTZ | * 1537 Thurm + 1579 Joachimsthal | 66574 | Thomas Von Ryssel | 2024-08-04 | |
Christoph KRUMBHOLTZ | * 1537 Thurm + 1579 Joachimsthal | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
Christoph KRUMBHOLTZ | * 1537 Thurm + 1579 Joachimsthal | 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?? |