Individual Page


Family
Marriage: Children:
  1. John William Larkin: Birth: 23 Aug 1612 in Cardington, Bedfordshire, England. Death: 01 Mar 1623 in Cardington, Bedfordshire, England

  2. William Larkin: Birth: 23 Aug 1612 in Cardington, Bedfordshire, England. Death: 1686

  3. John Larkin: Birth: January 1614 in Bedford, Bedfordshire, England. Death: 4 Feb 1702 in Annapolis, Anne Arundel, Maryland, Colonial America

  4. Edward Larkin: Birth: 1615 in Berkhampsted, Suffolk, England (Kent, England). Death: 02 Jun 1652 in Charlestown, Middlesex, Massachusetts, Colonial America

  5. Edward Larkins: Birth: 2 Jun 1615 in Berkhampsted, Suffolk, England (Kent, England). Death: 2 Jun 1652 in Charlestown, Suffolk, Massachusetts, Colonial America

  6. Edward (Wheelmaker) Larkin: Birth: 2 Jun 1615 in Kent County, England. Death: 26 Jun 1687 in Westerly, Washington, Rhode Island, United States

  7. Alice Larkin: Birth: 1617 in Cardington, Bedfordshire, England. Death: 1623

  8. Clement Larkin: Birth: 1622 in Cardington, Bedfordshire, England. Death: 23 Mar 1622 in Cardington, Bedfordshire, England

  9. Thomas Larkin: Birth: 1623 in Cardington, Bedfordshire, England. Death: 01 Mar 1623 in Cardington, Bedfordshire, England

  10. Ursula Larkin: Birth: 1625 in Cardington, Bedfordshire, England. Death: 1700

  11. William Larkins: Birth: 1626 in Cardington, Bedfordshire, England. Death: 1686

  12. Alice Larkin: Birth: 1628 in Cardington, Bedfordshire, England.


Sources
1. Title:   Ancestry Family Trees
Page:   Ancestry Family Tree
Publication:   Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members.
2. Title:   Millennium File
Author:   Heritage Consulting
Publication:   Ancestry.com Operations Inc
3. Title:   England, Select Marriages, 1538–1973
Author:   Ancestry.com
Publication:   Ancestry.com Operations, Inc.



RootsWeb.com is NOT responsible for the content of the GEDCOMs uploaded through the WorldConnect Program. The creator of each GEDCOM is solely responsible for its content.