Johann GÜNTZE
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Johann GÜNTZE |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 25. August 1630 | Leipzig
Find persons in this place |
|
naturalization | 31. October 1613 | Leipzig
Find persons in this place |
|
burial | 27. August 1630 | Leipzig
Find persons in this place |
|
birth | 1. May 1593 | Leipzig
Find persons in this place |
|
Handelsmann | Leipzig
Find persons in this place |
||
marriage | 30. October 1614 | ||
marriage | 24. November 1629 |
Parents
Hans GÜNTZE | Rebecca HÖLTZER |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
30. October 1614
|
Christina LANTZENBERGER |
|
24. November 1629
|
Elisabeth FABER |
|
Sources
1 | https://collections.thulb.uni-jena.de/rsc/viewer/HisBest_derivate_00013039/leicbeb_360952267_0001.tif
Abbreviation: https://collections.thulb.uni-jena.de/rsc/viewer/HisBest_derivate_00013039/leicbeb_360952267_0001.tif
|
2 | LP Braunschweig 2078
Abbreviation: LP Braunschweig 2078
|
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 GÜNTZE | * 1593 Leipzig + 1630 Leipzig | 60258 | Familie von Rysel | Thomas Von Ryssel | 2021-01-31 |
Johann GÜNTZE | * 1593 Leipzig + 1630 Leipzig | 66574 | Thomas Von Ryssel | 2024-08-04 | |
Johann GUNTZE | + 1630 Leipzig | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
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?? |