Who was James Haynes?

James Haynes (1660–1732) was born in Sudbury, Middlesex, Massachusetts, USA and died in Sudbury, Middlesex, Massachusetts, USA. 7 researchers on YourRoots have this ancestor in their family trees.

How many people are researching James?

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

What records do they have for James?

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.

James Haynes 1660–1732

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 7 independent trees

Birth year and location consistent across 7 trees

Death year and location consistent across 7 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

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

Last updated: August 25, 2026 · Reliability: B — verified across 7 independent trees

Born 17 May 1660 · Sudbury, Middlesex, Massachusetts, USA

Died 15 Oct 1732 · Sudbury, Middlesex, Massachusetts, USA

Father John Haynes (1649–1710)

Mother Dorothy Noyes

Siblings Capt David Haynes, Daniel Haynes, Dorothy Haynes Freeman, Elizabeth Freeman, Elizabeth Haynes, John Haynes Jr, Joseph Haynes, Mary Haynes, Mary Rachel Haynes, Peter Haynes Sgt, Ruth Haynes

Records

Geneanet Community Trees Index Ancestry Family Tree

Compare Tree

Researchers connected through James Haynes 1660–1732

and 5 more tree owners connected with James Haynes 1660–1732

Immediate Family

Parents

John Haynes

1649–1710

Dorothy Noyes

Spouse(s)

No spouse recorded

Children

No children recorded

Biography

The story of James Haynes began in 1660 in Sudbury, Middlesex, Massachusetts, USA. James Haynes passed away in 1732 in Sudbury, Middlesex, Massachusetts, USA.

Sources

1

Record Geneanet Community Trees Index
2

Record Ancestry Family Tree

Life Timeline

1660

Birth of James Haynes in Sudbury, Middlesex, Massachusetts, USA

Birth

1732

Death of James Haynes in Sudbury, Middlesex, Massachusetts, USA

Death

Oldest Ancestor Line from James Haynes

This ancestor line traces from Penton, Southampton, Hampshire, England (1550) to Sudbury, Middlesex, Ma (1660) across 4 generations.

Direct Lineage

generations

Frequently Asked Questions

: James Haynes (1660–1732) was born in Sudbury, Middlesex, Massachusetts, USA and died in Sudbury, Middlesex, Massachusetts, USA. 7 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, 7 researchers on YourRoots have James 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 4 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.