Individual Page


Family
Marriage: Children:
  1. John Noble: Birth: 06 MAR 1662 in Springfield, Hampden, Massachusetts, United States. Death: 17 AUG 1714 in New Milford, Litchfield, Connecticut, United States

  2. Hannah Noble: Birth: 24 FEB 1664. Death: 1741

  3. Thomas Noble: Birth: 14 JAN 1666 in Springfield, Massachusetts. Death: 29 JUL 1750 in Westfield, Massachusetts

  4. Mathew Noble: Birth: 1668 in Sheffield. Death: 04 MAR 1744 in Sheffield, Berkshire, Massachusetts, USA

  5. Mark Noble: Birth: AUG 1670 in Westfield, Hampden, Massachusetts, USA. Death: 16 APR 1741 in Westfield, Hampden, Massachusetts, USA

  6. Elizabeth Noble: Birth: 09 FEB 1673. Death: 10 AUG 1751

  7. James Noble: Birth: 01 OCT 1677. Death: 22 APR 1712

  8. Mary Noble: Birth: 25 JUN 1680. Death: 1759

  9. Margaret Noble: Birth: 29 JUN 1680. Death: 1749

  10. Rebecca Noble: Birth: 04 JAN 1683 in Westfield, Hampden, Massachusetts, USA. Death: 1759 in Westfield, Hampden, Massachusetts, USA

  11. Luke Noble: Birth: 15 JUL 1765. Death: 21 MAR 1744 in Westfield, Hampden, Massachusetts, USA


Sources
1. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
2. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
3. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
4. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
5. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
6. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
7. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
8. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
9. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
10. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com



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.