Rosina PÖCKEL
Characteristics
| Type | Value | Date | Place | Sources |
|---|---|---|---|---|
| name | Rosina PÖCKEL |
|
Events
| Type | Date | Place | Sources |
|---|---|---|---|
| death | 11. January 1656 | Leipzig
Find persons in this place |
|
| baptism | 17. April 1603 | Schneeberg
Find persons in this place |
|
| burial | 15. January 1656 | Leipzig
Find persons in this place |
|
| birth | 16. April 1603 | Schneeberg
Find persons in this place |
|
| marriage | 11. May 1624 | Leipzig
Find persons in this place |
|
| marriage | 27. July 1641 | Leipzig
Find persons in this place |
Parents
| Enoch JUC PÖCKEL | Maria SIEGEL |
??spouses-and-children_en_US??
| Marriage | ??spouse_en_US?? | Children |
|---|---|---|
|
11. May 1624
Leipzig |
Heinrich RYSSEL VON |
|
|
27. July 1641
Leipzig |
Matthaeus NITZSCHE |
|
Sources
| 1 | LP Braunschweig 4919
Abbreviation: LP Braunschweig 4919
|
| 2 | Roth 1191
Abbreviation: Roth 1191
|
| 3 | muehlberg
Abbreviation: www.uta-muehlberg.de
|
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 |
|---|---|---|---|---|---|
| Rosina PÖCKEL | * 1603 Schneeberg + 1656 Leipzig | 66574 | Thomas Von Ryssel | 2024-08-04 | |
| Rosina PÖCKEL | * 1603 Schneeberg + 1656 Leipzig | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
| Rosina PÖCKEL | * 1603 Schneeberg + 1656 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 |
Thomas Von Ryssel
visit the user's profile page
|
| vonrysselthomas@gmail.com | |
| ??show-persons-in-database_en_US?? | |