Johannes SCHMIDT
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Johannes SCHMIDT |
|
||
occupation | Tagelöhner |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
residence | from 1852 to 1858 | Bermershausen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
residence | from 1861 to 1868 | Feudingen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
birth | 25. August 1831 | Rüppershausen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
marriage | 23. March 1851 | Feudingen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
Parents
Jakob SCHMIDT | Luise HASSLER |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
23. March 1851
Feudingen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland |
Elisabeth SPIES |
|
Notes for this person
Familienname: Schmidt
Vorname (kurz): Johs
Name (kurz): Johs Schmidt
Status: ve.
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 |
---|---|---|---|---|---|
Johannes SCHMIDT | * 1831 Rüppershausen, 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 |
![]() |
mj-genealogy@gmx.de | |
??show-persons-in-database_en_US?? |