Franz Aloys UPHUES
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Franz Aloys UPHUES |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 7. March 1944 | 46342 Velen-Ramsdorf, Kreis Borken, Nordrhein-Westfalen, Deutschland
Find persons in this place |
|
birth | 18. October 1860 | 46342 Velen-Ramsdorf, Kreis Borken, Nordrhein-Westfalen, Deutschland
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
|
|
Notes for this person
<p><p>Ramsdorf KB 11*</p></p><p>Stammbaum der Ramsdorfer Schmiede Uphues; In: Schulze Selting, Josef: Ramsdorf und seine Heimatgeschichte. 1969, Seite 80</p>
Sources
1 | Schäpers Web Site, Franz Aloys Uphues
Author: Klemens Schäpers
|
Über eine Person Discovery hinzugefügt <p>MyHeritage-Stammbaum</p><p>Familienseite: Schäpers Web Site</p>Stammbaum: 334098501-1 | |
2 | Beckmann Web Site, https://www.myheritage.de/person-1524548_109918824_109918824/franz-aloys-uphues
Author: Jochen Beckmann
|
Durch Bestätigung eines Smart Match hinzugefügt <p>MyHeritage-Stammbaum</p><p>Familienseite: Beckmann Web Site</p>Stammbaum: 561824891-2 |
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 |
---|---|---|---|---|---|
Franz Aloys UPHUES | * 1860 46342 Velen-Ramsdorf, Kreis Borken, Nordrhein-Westfalen, Deutschland + 1944 46342 Velen-Ramsdorf, Kreis Borken, Nordrhein-Westfalen, Deutschland | 56345 | Jochen Beckmann | 2019-02-10 |
files
Title | |
Description | |
Id | 56344 |
Upload date | 2019-02-10 22:05:12.0 |
Submitter |
![]() |
jochenbeckmann@gmx.de | |
??show-persons-in-database_en_US?? |