Philipp Christian STENGER
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Philipp Christian STENGER |
[2]
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 15. April 1826 | Rambach
Find persons in this place |
|
baptism | 29. January 1826 | Rambach
Find persons in this place |
[2]
|
burial | 17. April 1826 | Rambach
Find persons in this place |
|
birth | 19. January 1826 | Rambach
Find persons in this place |
Parents
Marie Rosina STENGER |
Sources
1 | Arcion, Taufregister Rambach, Bild 48 https://www.ancestry.de/discoveryui-content/view/5011069:61060?tid=&pid=&queryId=187ef0c352f57461e587c87320b6c1a2&_phsrc=ohf8033&_phstart=successSource |
2 | https://www.archion.de/de/viewer/?no_cache=1&type=churchRegister&uid=343951 Bild 42
Abbreviation: https://www.archion.de/de/viewer/?no_cache=1&type=churchRegister&uid=343951
|
3 | https://www.archion.de/de/viewer/?no_cache=1&type=churchRegister&uid=343951 Bild 194 |
4 | https://www.archion.de/de/viewer/?no_cache=1&type=churchRegister&uid=343951 |
5 | https://www.archion.de/de/viewer/?no_cache=1&type=churchRegister&uid=232585 Bild 48 |
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 |
---|---|---|---|---|---|
Philipp Christian STEGER | * 1826 Rambach + 1826 Rambach | 67258 | Jürgen Wildhardt | 2025-01-09 | |
Philipp Christian STEGER | * 1826 Rambach + 1826 Rambach | 67257 | JW | Jürgen Wildhardt | 2025-01-09 |
files
Title | JW |
Description | Schwerpunkte: Naurod, Sonnenberg, Rambach |
Id | 66487 |
Upload date | 2024-07-03 15:51:30.0 |
Submitter |
![]() |
juergen.wildhardt@t-online.de | |
??show-persons-in-database_en_US?? |