Thomas ECHINGHAM
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Thomas ECHINGHAM |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 20. January 1483 | , Sussex, , England
Find persons in this place |
|
birth | 1425 | , Sussex, , England
Find persons in this place |
|
marriage | 1448 | , Kent, , England
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
1448
, Kent, , England |
Margaret WEST VERH.ECHINGHAM |
Sources
1 | Ancestry Family Trees, Ancestry Family Trees
Publication: Online publication - Provo, UT, USA: The Generations Network. Original data: Family Tree files submitted by Ancestry members.
|
http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=11889675&pid=-368100050 | |
2 | Ancestry Family Trees, Ancestry Family Trees
Publication: Online publication - Provo, UT, USA: The Generations Network. Original data: Family Tree files submitted by Ancestry members.
|
http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=11889675&pid=-368100050 | |
3 | Ancestry Family Trees, Ancestry Family Trees
Publication: Online publication - Provo, UT, USA: The Generations Network. Original data: Family Tree files submitted by Ancestry members.
|
http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=11889675&pid=-368100050 | |
4 | Ancestry Family Trees, Ancestry Family Trees
Publication: Online publication - Provo, UT, USA: The Generations Network. Original data: Family Tree files submitted by Ancestry members.
|
http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=11889675&pid=-368100050 |
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 | |
Description | |
Id | 33456 |
Upload date | 2010-05-03 15:10:56.0 |
Submitter |
![]() |
horstbreitbart@t-online.de | |
??show-persons-in-database_en_US?? |