Who was Sarah MEEKER?

Sarah MEEKER (1735–1792) was born in Springfield, Union, New Jersey, United States and died in Springfield, Union, New Jersey, United States. 2 researchers on YourRoots have this ancestor in their family trees.

How many people are researching Sarah?

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

What records do they have for Sarah?

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.

Sarah MEEKER 1735–1792

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 Sarah MEEKER in their family trees — each with their own records and documentation. Trace the migration path across 24 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

Born 1 Jan 1735 · Springfield, Union, New Jersey, United States

Died 1 Jan 1792 · Springfield, Union, New Jersey, United States

Father Timothy Meeker

Mother Desire Cory

Siblings Abigail Meeker, Amos Meeker, Capt Joseph Pierson Meeker, Cory Meeker, David Meeker, Desire Meeker, Hannah Meeker, Isaac Meeker, John Meeker, Jonas Meeker, Jonathan Meeker, Mary Polly Meeker, Phebe Meeker, Timothy Meeker, William Meeker

Compare Tree

Researchers connected through Sarah MEEKER 1735–1792

and 1 more tree owner connected with Sarah MEEKER 1735–1792

Immediate Family

Parents

Timothy Meeker

Desire Cory

Spouse(s)

No spouse recorded

Children

No children recorded

Biography

The story of Sarah MEEKER began in 1735 in Springfield, Union, New Jersey, United States. Sarah MEEKER passed away in 1792 in Springfield, Union, New Jersey, United States.

Sources

Life Timeline

1735

Birth of Sarah MEEKER in Springfield, Union, New Jersey, United States

Birth

1792

Death of Sarah MEEKER in Springfield, Union, New Jersey, United States

Death

Oldest Ancestor Line from Sarah MEEKER

This ancestor line traces from Orkney Islands, Orkney, , Scotland (1011) to Springfield, Union, New Jersey, United States (1735) across 24 generations.

Direct Lineage

generations

Frequently Asked Questions

: Sarah MEEKER (1735–1792) was born in Springfield, Union, New Jersey, United States and died in Springfield, Union, New Jersey, United States. 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 Sarah 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 24 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.