Heinrich Freiherr FRIESEN VON
Characteristics
| Type | Value | Date | Place | Sources |
|---|---|---|---|---|
| name | Heinrich Freiherr FRIESEN VON |
|
||
| property | Schönfeld ,Butzkau |
|
Events
| Type | Date | Place | Sources |
|---|---|---|---|
| death | 20. June 1659 | Dresden
Find persons in this place |
|
| burial | 11. July 1659 | ||
| birth | 24. April 1578 | Kauern
Find persons in this place |
|
| marriage | 3. September 1601 | Schweinsburg
Find persons in this place |
Parents
| Carl FRIESEN VON | Rahel ENDE VOM |
??spouses-and-children_en_US??
| Marriage | ??spouse_en_US?? | Children |
|---|---|---|
|
3. September 1601
Schweinsburg |
Catherina a.d.H. Schweinsburg EINSIEDEL VON |
|
Sources
| 1 | https://www.geni.com/people/Heinrich-Freiherr-von-Friesen-d-%C3%84/6000000022380424161
Abbreviation: https://www.geni.com/people/Heinrich-Freiherr-von-Friesen-d-%C3%84/6000000022380424161
|
| 2 | Lindnerische Ahnentafelsammlung Nr. 119a
Abbreviation: Lindnerische Ahnentafelsammlung Nr. 119a
|
| 3 | LP Braunschweig 1642
Abbreviation: LP Braunschweig 1642
|
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 |
|---|---|---|---|---|---|
| Heinrich Freiherr FRIESEN VON | * 1578 Kauern + 1659 Dresden | 60258 | Familie von Rysel | Thomas Von Ryssel | 2021-01-31 |
| Heinrich Freiherr FRIESEN VON | * 1578 Kauern + 1659 Dresden | 66574 | Thomas Von Ryssel | 2024-08-04 |
files
| Title | Johann 2024 |
| Description | Familie von Ryssel |
| Id | 66573 |
| Upload date | 2024-08-04 11:47:57.0 |
| Submitter |
Thomas Von Ryssel
visit the user's profile page
|
| vonrysselthomas@gmail.com | |
| ??show-persons-in-database_en_US?? | |