Maria Elisabeth TELSCHOW
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Maria Elisabeth TELSCHOW |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
emigration | 27. March 1881 | Hamburg via Liverpool => New York,USA
Find persons in this place |
[2]
|
death | 9. April 1942 | Chicago,Cook Co,IL
Find persons in this place |
[3]
|
birth | 17. April 1872 | Klenzenhof/Prignitz,Brdbg,Preussen
Find persons in this place |
[4]
|
census | (1910,1920) s. source
Find persons in this place |
||
Taufe | 20. May 1872 | Reckenthin
Find persons in this place |
[4]
|
Parents
Christian TELSCHOW | Alwine GRAGERT |
Notes for this person
FamilySearch International Genealogical Index Marie E. Telschow Female -------------------------------------------------------------------------------- Event(s): Birth: Christening: Death: Burial: -------------------------------------------------------------------------------- Marriages: Spouse: Charles Stubig Marriage: 18 MAR 1900 Chicago, Cook, Illinois
Sources
1 | Quitzow_1
Abbreviation: Quitzow_1
|
2 | Hamburger Schiffslisten 1881.
Abbreviation: Hamburger Schiffslisten 1881.
|
3 | Illinois Statewide Death Index, 1916-1950.
Abbreviation: Illinois Statewide Death Index, 1916-1950.
|
4 | KiBu Reckenthin, Taufregister 1872, Nr. 1.
Abbreviation: KiBu Reckenthin, Taufregister 1872, Nr. 1.
|
5 | 1910 US Census, IL, Cook Co, City of Chicago, Wd-12.
Abbreviation: 1910 US Census, IL, Cook Co, City of Chicago, Wd-12.
|
6 | 1920 US Census, IL, Cook Co, Chicago, Wd-12.
Abbreviation: 1920 US Census, IL, Cook Co, Chicago, Wd-12.
|
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 | Jankowski - 2014/11/1 |
Description | Jankowski - 2014/11/1 |
Id | 46583 |
Upload date | 2014-11-01 11:07:04.0 |
Submitter |
![]() |
cjanko78@aol.com | |
??show-persons-in-database_en_US?? |