Henrich FISCHER
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Henrich FISCHER |
|
||
occupation | holl. Soldat (1784), ftl. Soldat (1794,1801); Kuhhirt (1789, 1791) |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 28. February 1801 | Diedenshausen, Bad Berleburg, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
residence | Diedenshausen, Bad Berleburg, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
||
birth | 28. January 1755 | Bad Berleburg, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
marriage | calculated November 1776 | ||
marriage | 2. November 1788 | Girkhausen, Bad Berleburg, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
Parents
Matthias FISCHER | Elisabeth MÜSSE |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
calculated November 1776
|
Elisabeth HACKENBRACHT |
|
2. November 1788
Girkhausen, Bad Berleburg, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland |
Wilhelmine DELCOURT |
|
Notes for this person
Familienname: Fischer
Weitere Namen: Johann Henrich
Vorname (kurz): JHenr
Name (kurz): Henr Fischer
Familienstand: JHenr Fischer, ftl. Musketier, Beisitzer in Hanses
Freier Text: P Blb 1783 MFischer (VB), 84 MFischer (holl. Soldat, VB)
Status: Beisitzer in Hanses (+)
Quellen: +: alt 46+4
Paten: JHenr Schnell, Schlosser, Blb; AKath & JGg Richstein, Rin
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.
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?? |