Our Family's Journey Through Time
Matches 1 to 43 of 43 for First Name starts with NATH
# | Last Name, Given Name(s) | Person ID | Born/Christened | Location | Tree |
---|---|---|---|---|---|
1 |
Ely, Nathan | I0634 | b. 9 Jan 1739 | West Springfield, Hampden, Massachusetts | MyTree |
2 |
Ely, Nathaniel | I292181397005 | b. 1670-01-18 | Springfield, Hampden, Massachusetts, United States | Ancestry |
3 |
Ely, Nathaniel Rev | I292181397012 | b. 28 Sep 1572 | Tenterden, Kent, England | Ancestry |
4 |
Ely, Nathaniel Rev | I2322 | b. 28 Sep 1572 | Tenterden, Kent, England | MyHeritage |
5 |
Ely, Nathaniel | I0638 | b. 28 Sep 1572 | Tenterden, Kent, , England | MyTree |
6 |
Ely, Nathaniel | I0636 | b. 1605 | Tenterden, Kent, , England | MyTree |
7 |
Ely, Nathaniel | I292181396994 | b. 1609 | Tenterden, Kent, England | Ancestry |
8 |
Ely, Nathaniel | I2304 | b. 1609 | Tenterden, Kent, England | MyHeritage |
9 |
Ely, Nathaniel | I2315 | b. 18 Jan 1670 | Springfield, Hampden, Massachusetts, United States | MyHeritage |
10 |
Ely, Nathaniel | I0637 | b. 18 Jan 1670 | Springfield, Hampden, Massachusetts, United States | MyTree |
11 |
Ely, Nathaniel | I292181396995 | b. 25 Apr 1674 | Springfield, Hampden Co MA | Ancestry |
12 |
Ely, Nathaniel | I2305 | b. 25 Apr 1674 | Springfield, Hampden Co MA | MyHeritage |
13 |
ELY, Nathaniel | I292181396985 | b. 27 Oct 1694 | West Springfield, Hampden, Massachusetts, United States | Ancestry |
14 |
Ely, Nathaniel | I2295 | b. 27 Oct 1694 | West Springfield, Hampden, Massachusetts, United States | MyHeritage |
15 |
Ely, Nathaniel | I0635 | b. 22 Sep 1706 | West Springfield, Hampden, Massachusetts | MyTree |
16 |
Higley, Nathaniel | I3383 | b. 12 Nov 1699 | Simsbury, Hartford County, Connecticut Colony | MyHeritage |
17 |
Hubbard, Nathaniel | I292181394920 | b. 10 Dec 1652 | Middleton, Middlesex Connecticut, USA | Ancestry |
18 |
Hubbard, Nathaniel | I363 | b. 10 Dec 1652 | Middleton, Middlesex Connecticut, USA | MyHeritage |
19 |
Hubbard, Nathaniel | I0982 | b. 10 Dec 1652 | Middleton, Middlesex Connecticut, USA | MyTree |
20 |
Hubbard, Nathaniel | I292181394927 | b. 14 Sep 1690 | Middleton, Middlesex Connecticut, USA | Ancestry |
21 |
Hubbard, Nathaniel | I370 | b. 14 Sep 1690 | Middleton, Middlesex Connecticut, USA | MyHeritage |
22 |
Hubbard, Nathaniel | I0981 | b. 14 Sep 1690 | Middleton, Middlesex Connecticut, USA | MyTree |
23 |
Jones, Nath | I1028 | MyTree | ||
24 |
Ladd, Nathan | I1235 | b. 26 May 1795 | MyTree | |
25 |
Law, Nathaniel | I292184292266 | Ancestry | ||
26 |
Lay, NATHANIEL | I292181395035 | b. 1 Apr 1764 | WESTBROOK, CT | Ancestry |
27 |
Lay, NATHANIEL | I480 | b. 1 Apr 1764 | WESTBROOK, CT | MyHeritage |
28 |
Lay, NATHANIEL | I1349 | b. 1 Apr 1764 | WESTBROOK, CT | MyTree |
29 |
Lewis, Nathal | I1414 | b. 1838 | Delaware Township, , Delaware, Ohio | MyTree |
30 |
Lewis, Nathan | I1415 | MyTree | ||
31 |
Loomis, Nathaniel Sr | I500063 | b. 29 Jan 1626 | Braintree, Essex, England | MyHeritage |
32 |
Loomis, Nathaniel | I500066 | b. 20 Mar 1657 | Windsor, Connecticut Colony | MyHeritage |
33 |
Loomis, Nathaniel | I292181395071 | b. 27 Jan 1690 | Hartford, Hartford County, Connecticut, USA | Ancestry |
34 |
Loomis, Nathaniel | I500053 | b. 27 Jan 1691 | Windsor, Hartford, Connecticut, United States | MyHeritage |
35 |
Loomis, Nathaniel II | I292181396578 | b. 1731 | Columbia, Tolland, Connecticut, USA | Ancestry |
36 |
Merrill, Nathaniel | I1710 | MyTree | ||
37 |
Peck, Nathan | I1940 | MyTree | ||
38 |
Shannon, Nathan Clark | I3769 | b. 7 Jan 1888 | Mill Creek, Coshocton, Ohio, United States | MyHeritage |
39 |
Shannon, Nathan R | I3764 | b. 18 Feb 1851 | Keene Township, Coshocton, Ohio, United States | MyHeritage |
40 |
Stoughton, Nathaniel | I3476 | b. 23 Jun 1702 | Windsor, Hartford, Connecticut, British Colonial America | MyHeritage |
41 |
Sutton, Nathan C | I2849 | b. Oct 1850 | MyHeritage | |
42 |
Townsend, Nathaniel | I3183 | b. 16 Dec 1760 | Coventry, Tolland, Connecticut, United States | MyHeritage |
43 |
Wade, Nathan | I2421 | MyHeritage |
We make every effort to document our research. If you have something you would like to add, please contact us.