Who was Nathaniel Snow?

Nathaniel Snow (1735–1821) was born in Eastham, Barnstable, MA and died in Ellington. 2 researchers on YourRoots have this ancestor in their family trees.

How many people are researching Nathaniel?

Right now, 2 researchers on YourRoots have Nathaniel in their trees. The ancestor migration map traces 7 generations of this lineage.

What records do they have for Nathaniel?

Records vary by researcher and can include census, vital, parish, cemetery, and family sources.

How do I compare family trees?

Use Compare Tree on an available researcher profile to compare overlapping people and records.

Nathaniel Snow 1735–1821

Public Tree Person

What is a Public Tree Person?

A Public Tree Person is an ancestor documented independently by multiple YourRoots tree owners. When several researchers' family histories converge on the same person, we publish a shared page that combines what they've documented.

Why this is a Public Tree Person

Full name consistent across 2 independent trees

Birth year and location consistent across 2 trees

Death year and location consistent across 2 trees

Compare a Public Tree Person with your own tree using Compare Tree.

B Reliability

Reliability Score: B

Medium — based on the source tree

Grade scale

A 3 criteria (Strong)
B 2 criteria (Medium)
C 1 criteria (Basic)

Verification checklist

Record available
Descendant's record available
Star tree owner

2 researchers on YourRoots have Nathaniel Snow in their family trees — each with their own records and documentation. Trace the migration path across 7 generations. If this ancestor is in your tree too, you can compare what you've found and fill in the gaps together.

Last updated: July 22, 2026 · Reliability: B — verified across 2 independent trees, with linked records

Born 8 Dec 1735 · Eastham, Barnstable, MA

Died 23 Dec 1821 · Ellington

Father Elisha Snow

Mother Abigail Doane

Spouse Rebeca Doane

Siblings Aaron Snow, Ebenezer Snow, Edward Snow, Elisha Snow Jr, Eunice Snow, Hannah Snow, James Snow, Osbourn Snow, Samuel Snow, Thomas Snow

Records

Connecticut, U.S., Town Death Records, … Geneanet Community Trees Index S968164303 S968164492 S968341788

Compare Tree

Researchers connected through Nathaniel Snow 1735–1821

and 1 more tree owner connected with Nathaniel Snow 1735–1821

Immediate Family

Parents

Elisha Snow

Abigail Doane

Spouse(s)

Rebeca Doane

Children

No children recorded

Biography

The story of Nathaniel Snow began in 1735 in Eastham, Barnstable, MA. Nathaniel Snow married rebeca doane. Nathaniel Snow passed away in 1821 in Ellington.

Sources

1

Death Records Connecticut, U.S., Town Death Records, pre-1870 (Barbour Collection)
2

Record Geneanet Community Trees Index
3

Record S968164303
4

Record S968164492
5

Record S968341788

Life Timeline

1735

Birth of Nathaniel Snow in Eastham, Barnstable, MA

Birth

1821

Death of Nathaniel Snow in Ellington

Death

Oldest Ancestor Line from Nathaniel Snow

This ancestor line traces from Upper Clatford, Hampshire, England (1550) to Eastham, Barnstable, MA (1735) across 7 generations.

Direct Lineage

generations

Frequently Asked Questions

: Nathaniel Snow (1735–1821) was born in Eastham, Barnstable, MA and died in Ellington. 2 researchers on YourRoots have this ancestor in their family trees, each with their own records. This page combines what they've independently documented and assigns a Reliability Score (B) based on cross-tree validation.
: Right now, 2 researchers on YourRoots have Nathaniel in their trees. They're working independently, so connecting with them is a good way to cross-check your records and find things you might have missed. You can also explore the ancestor migration map that traces 7 generations of this lineage geographically.
: It varies by researcher — some have census records, others have marriage certificates, parish registers, or family Bible entries. Scroll up to see exactly what each person has cited.
: Use the "Compare Tree" button on any researcher's profile above. You can compare your tree side by side with theirs, see where your records overlap or differ, and collaborate to fill gaps.