Hermann BILGEN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Hermann BILGEN |
|
||
title | Kirchenältester |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
baptism | 17. September 1648 | Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
residence | Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
||
burial | 12. February 1720 | Banfe, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
marriage | 5. April 1685 | Feudingen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
marriage | about 1710 |
Parents
Johannes BILGEN | Katharina KESSLER |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
5. April 1685
Feudingen, Bad Laasphe, Kreis Siegen-Wittgenstein, Nordrhein-Westfalen, Deutschland |
Gertrud BLECHER | |
about 1710
|
(w) NN2 |
|
Notes for this person
Familienname: Bilgen
Weitere Namen: Hans Hermann
Vorname (kurz): HHerm
Name (kurz): Herm Bilgen
Familienstand: HHerm Bilgen, der Elteste
Freier Text: P Fdg 1670 TDörr, 76 JFischbach, 88 KBecker, 91 ABlecher, 96 KBilgen (VB), 1702 ABilgen (VB), 04 GBrickel (in der Ecke)
Quellen: WA - M21, Blatt 101, Rekrutierungsverfahren 1681
SB 1771; AR 1683-1721, 1743+; UV rel. 1732-1739
Paten: Herm vorm Auerbach, Ban; NN Tv Jost Schöbel, Wlu [Den Namen Schöbel gibt es in Wallau/BID nicht.]
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?? |