Gottfried Dr.Theol. OLEARIUS
Characteristics
| Type | Value | Date | Place | Sources |
|---|---|---|---|---|
| name | Gottfried Dr.Theol. OLEARIUS |
|
Events
| Type | Date | Place | Sources |
|---|---|---|---|
| death | 20. February 1685 | ||
| birth | 1. January 1604 | ||
| Superint. und Pfarrer St. Ulrich | |||
| marriage | 11. November 1634 | Halle a.d.S
Find persons in this place |
|
| marriage | 16. January 1638 |
??spouses-and-children_en_US??
| Marriage | ??spouse_en_US?? | Children |
|---|---|---|
|
11. November 1634
Halle a.d.S |
Anna WOGAU |
|
|
16. January 1638
Halle |
Elisabeth SCHÄFFER |
|
Sources
| 1 | https://de.wikipedia.org/wiki/Gottfried_Olearius_(Theologe,_1604)
Abbreviation: https://de.wikipedia.org/wiki/Gottfried_Olearius_(Theologe,_1604)
|
| 2 | LP Braunschweig 4663
Abbreviation: LP Braunschweig 4663
|
| 3 | Roth 7123
Abbreviation: Roth 7123
|
| 4 | Theil 1 Bd 2 Dietmann.pdf S. 89
Abbreviation: Theil 1 Bd 2 Dietmann.pdf S. 89
|
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 |
|---|---|---|---|---|---|
| Gottfried Dr.Theol. OLEARIUS | * 1604 Halle + 1685 Halle | 66574 | Thomas Von Ryssel | 2024-08-04 | |
| Gottfried Dr.Theol. OLEARIUS | * 1604 Halle + 1685 Halle | 53087 | Johann 05.2017 | Thomas Von Ryssel | 2017-05-07 |
| Gottfried Dr.Theol. OLEARIUS | * 1604 Halle + 1685 Halle | 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?? | |