Friedrich SCHÄFER
Characteristics
| Type | Value | Date | Place | Sources |
|---|---|---|---|---|
| name | Friedrich SCHÄFER |
|
||
| occupation | Wagner |
|
Events
| Type | Date | Place | Sources |
|---|---|---|---|
| residence | Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
||
| birth | 6. January 1822 | Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
| marriage | 26. September 1847 | Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
Parents
| Kraft SCHÄFER | Charlotte STEIN |
??spouses-and-children_en_US??
| Marriage | ??spouse_en_US?? | Children |
|---|---|---|
|
26. September 1847
Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland |
Christine FISCHER |
|
Notes for this person
Familienname: Schäfer
Weitere Namen: Friedrich August Henrich
Vorname (kurz): FrdrAH
Name (kurz): Frdr Schäfer
Quellen: Laa, Stadtarchiv, B 670, Stammrolle 1824, lfd. Nr. 332 = 577
Laa, Stadtarchiv, B 671, Volkszählung 1840, lfd. Nr. 94/3
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 |
|---|---|---|---|---|---|
| Friedrich SCHÄFER | * 1822 Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland | 60870 | Projekt “Rothenpieler” | Michael | 2025-01-01 |
files
| Title | Online-OFB "Wittgensteiner Land" |
| Description | Backup von https://online-ofb.de/wittgenstein |
| Id | 60894 |
| Upload date | 2022-05-15 19:34:29.0 |
| Submitter |
Michael
visit the user's profile page
|
| mj-genealogy@gmx.de | |
| ??show-persons-in-database_en_US?? | |