By the time you reach “third cousin once removed,” most people have given up trying to work out what the label means. It’s the frontier where casual family-tree conversation ends and genealogical hair-splitting begins. But the label follows a precise formula, and understanding it opens up the general rule that produces every cousin relationship — Nth cousin K-times removed, for any values of N and K.
This guide walks the formula, the DNA range associated with third-cousin-once-removed relationships, why identifying such distant cousins matters for Tamil family history, and the specific tools that can compute the relationship automatically so you don’t have to.
The label decoded
A third cousin once removed is:
- The child of your third cousin, OR
- Your parent’s third cousin, OR
- Any person one generation apart from you who shares your same great-great-great-grandparents (4 generations back)
Two conditions in the label:
- “Third cousin” — you share great-great-great-grandparents (three “greats” for third cousin; N greats for Nth cousin).
- “Once removed” — you are one generation apart in descent from the shared ancestors.
The general kinship formula
For any two people related through a common ancestor, the relationship is described by two numbers:
- N (cousin number): the closer of the two “generations back to shared ancestor” counts, minus one.
- K (removed count): the difference between the two “generations back to shared ancestor” counts.
Formally: person A is (N)th cousin (K)-times removed from person B if:
- The closer of them is (N+1) generations from the shared ancestor
- The other is (N+1+K) generations from the shared ancestor
Third cousin once removed: N=3, K=1. Both share ancestors, one goes 4 generations back (great-great-great-grandparents = closer link), the other goes 5 generations back (great-great-great-great-grandparents = further link).
Worked example on a Tamil family tree
Take a great-great-great-grandfather Muthusamy. He had two sons, Perumal and Kannan.
- Perumal’s line: Perumal → his son Ramasamy → his son Krishnan → his son Selvan → you
- Kannan’s line: Kannan → his son Rajah → his son Deepan → his son Anand → Anand’s son Vinod
Distance from Muthusamy:
- You: 4 generations back (father Selvan, grandfather Krishnan, great-grandfather Ramasamy, great-great-grandfather Perumal — actually wait, let me recount. You → Selvan (1) → Krishnan (2) → Ramasamy (3) → Perumal (4) → Muthusamy (5). So 5 generations from you to Muthusamy.
- Vinod: Vinod → Anand (1) → Deepan (2) → Rajah (3) → Kannan (4) → Muthusamy (5). 5 generations.
Both 5 generations, so N = 5-1 = 4. K = 0. You and Vinod are fourth cousins (not third cousin once removed).
For a third cousin once removed relationship, one of you needs to be 4 generations from the shared ancestor and the other 5.
Let me redo: Muthusamy → Perumal → Ramasamy → Krishnan → your parent Selvan → you (5 gen). Kannan’s line: Kannan → Rajah → Deepan → Anand → Vinod (5 gen). So you and Vinod are 4th cousins.
To have a “third cousin once removed” relationship: shorten one of the lines by one generation. Say Vinod’s line ends at Deepan (father Rajah, grandfather Kannan) — so Deepan is 4 generations from Muthusamy. You are still 5 generations. Then you and Deepan are third cousin once removed.
DNA sharing at this range
Third cousins share ~0.78% DNA on average (about 55 centiMorgans). Third cousin once removed drops further to about 40 centiMorgans on average. Both ranges have wide variance — some third-cousin pairs share ~200 cM, others share close to 0.
Practical implication: DNA tests can detect third cousins once removed but the confidence is low. A ~40 cM match could indicate:
- Third cousin once removed
- Fourth cousin
- Half second cousin twice removed
- Various other distant-cousin combinations
DNA at this range confirms “you two are somehow related” but usually can’t tell you HOW without cross-referencing family trees. For Tamil families where communities are historically endogamous (same caste or same village marrying across generations), a small shared-DNA match may also reflect distant multiple relationships rather than a single traceable ancestor.
Why bother with cousins this distant?
Third cousins once removed are on the edge of what most family history projects can realistically document. Practical reasons to reach that far:
- Village continuity: for Tamil families with continuous ties to one ancestral village, third cousins once removed are typically also from that village or its immediate diaspora. Documenting them completes the picture of the extended family’s village presence.
- Shared migration cohort: for diaspora families, third cousins once removed often descend from the same 3-4-great-grandparent generation who emigrated together. Documenting them completes the picture of the migration.
- DNA network mapping: DNA testing often surfaces third cousins once removed as matches; understanding the relationship lets you place them on the family tree.
- Community land / temple history: kula deivam temples were often shared across extended family branches. Third cousins once removed may be co-inheritors of the same temple’s family register.
- Legacy preservation: distant cousins may hold family artifacts (old photographs, letters, land documents) that other branches don’t have. Reaching out extends the collective family archive.
Tools that compute the relationship
Manually working out third-cousin-once-removed is possible but error-prone. Software that computes the relationship automatically once you place people on the tree:
- Gramps — “Relationship Calculator” tool. Enter two people, get the label.
- RootsMagic — “Kinship” reports across the whole tree.
- Family Historian — automatic labels on descendants view when hovering.
- Ancestry.com — auto-labels DNA matches with predicted relationships.
- MyHeritage — same auto-labelling for DNA matches with the “Theory of Family Relativity” feature that traces the connection through public trees.
- The Wikipedia “Cousin chart” — a static reference table that lets you look up any relationship manually.
For a one-off “what am I to this specific person” question, the Wikipedia chart is fastest. For ongoing tree management, install one of the software tools and let it compute all relationships automatically.
Common third-cousin-once-removed mistakes
The specific confusions that arise at this level:
- Confusing with fourth cousin. Fourth cousins share great-great-great-great-grandparents (4 “greats”). Third cousin once removed shares great-great-great-grandparents (3 “greats”) — different generation of shared ancestor.
- Miscounting generations. Off-by-one errors in generation counting are easy. Software is more reliable than manual counting past third-cousin range.
- Assuming symmetry means same generation. Third cousin once removed is symmetric (A is B’s 3rd cousin once removed AND vice versa), but they are NOT in the same generation — one is a generation above the other.
- Treating a distant DNA match as necessarily third-cousin-once-removed. A ~40 cM match could be many relationships; DNA alone doesn’t specify.
- Ignoring endogamy. In historically-endogamous Tamil communities, distant DNA matches may reflect multiple small connections rather than a single traceable third-cousin-once-removed link.
When the relationship label doesn’t matter
For most family history projects, once cousins get past second-cousin-once-removed range, the specific label matters less than the general concept: “we share ancestors 4-5 generations back through a specific branch.” What matters more is the underlying story — how are you connected, when did the family lines diverge, and what happened to each line since.
For Tamil families, this often maps to a specific narrative: “our great-great-grandfather had two sons; one stayed in the village, one emigrated to Natal in the 1880s. This distant cousin is descended from the son who emigrated; I’m descended from the son who stayed.” That narrative is more useful than the label “third cousin once removed” — but the label is a shorthand that lets genealogy software organise the relationship consistently.
The formula for third cousin once removed generalises. Master the counting rule and you can decode every cousin label — fourth cousin twice removed, half fifth cousin thrice removed, whatever the tree throws at you. That fluency, more than any specific relationship, is what genealogy vocabulary is trying to give you.
