Charles Gannsen Research  /  DNA Evidence

DNA Evidence

What genetic testing adds to a documentary investigation — a FamilyTreeDNA Big Y-700 on Charles's direct paternal line and autosomal estimates from two vendors (AncestryDNA and MyHeritage) on a descendant — and, just as important, the limits of what each can show.

The book’s account, as printed: What DNA Can and Cannot Say (full text). This page keeps the research log behind it, with every dated finding.

Genealogy and genetics answer different questions. The records reconstruct who Charles was; DNA tests whether the biological line agrees. This page reports both tests in full, including the matches they did not produce, so a reader can weigh the genetic evidence against the documentary conclusions on the claims dashboard.

Bottom line. The DNA to date is consistent with Charles's documented German origin but does not confirm either the parish (Hesse / Trendelburg) or the surname (the book makes the case, 28 Oct 2026, that he was possibly Karl Ludwig Hofedietz of Deisel, whom a Konze family possibly raised; not proven, and DNA may settle it). The Y-DNA places his strict paternal line in a young (~1450 CE) subclade whose nearest relatives are — so far without exception — Ashkenazi-Jewish lineages — pointing to a possible Ashkenazi-Jewish origin in the deep male line. On the strength of only two-to-three tested members this is held as a working line of inquiry, not a conclusion; it concerns deep ancestry that sits beneath, and does not contradict, the documented Hessian-Evangelical family. The autosomal estimates — from two independent vendors, AncestryDNA and MyHeritage, in agreement — are heavily Germanic but, taken from a descendant, average every ancestral line and cannot single out Charles's. No match yet ties the line to a documented Konze family, though a German-resident paternal cluster at 3rd-cousin depth (MyHeritage, June 2026) is under active correspondence — not yet assigned between Charles's line and Auguste Kreichelt's. The origin and surname conclusions therefore remain Working — see the confidence taxonomy — and the single highest-yield next step is to recruit a documented male-line Konze or Gans descendant to Y-test. The Ashkenazi-dominated match set is a real pattern, but a deep one (common ancestor of the closest matches c. 1450 CE). It was once read as fitting a Jewish-derived Gans line better than a long-Christian Konze line. That local route has since been tested and is not supported: no Jewish Gans household lived at Trendelburg or Deisel in 1823 or in 1858, and none is buried in the Trendelburg Jewish cemetery (1746–1927) (see below; a Seeligmann Ganß — a protected Jew at Trendelburg since 1720, read in the image of the 1731 list, and very probably the man written “Seelmann Gandt” on the 1740 list; no Jew of the canton bore the name Gans in 1812 — is on the 1740 Trendelburg list of protected Jews). The Y-result therefore does not choose between the two surnames. Since 28 Oct 2026 the book makes the case that he was possibly Karl Ludwig Hofedietz of Deisel, whom a Konze family possibly raised; a Hofedietz male-line Y test would test that case on the father’s side.
Latest check · 18 October 2026

All three match lists were read again on 18 October 2026. Nothing new bears on Charles.

Searched on all three sites: Konze, Kontze, Konzen, Kunze, Gans, Gansen and Gannsen, and births at Trendelburg and Deisel in the matches' trees. The Gans matches are small (about 8–21 cM) and lead to Dutch, Scandinavian, British or Rhineland families, none to Kreis Hofgeismar. The book's DNA chapter reports the results as of this date and points here for later ones.

Y-DNA — the direct paternal line

FamilyTreeDNA · Big Y-700

Terminal subclade: I-Y38863  ·  Haplogroup: I2, the I-M223 branch.

I-M170 › I-M223 › I-P78 › I-S9302 › … › I-Y6401 › I-Y6406 › I-Y11261 › I-Y50708 › I-Y38863

The Y chromosome passes essentially unchanged from father to son, so it tracks one line — Charles's patriline — back through the centuries, independent of every other ancestor. A Big Y-700 reads that line at high resolution and places it on the human paternal tree by its terminal SNP.

YFull · independent analysis

The same Big-Y data was independently interpreted by YFull (the descendant’s sample; ID withheld), which places the line on the identical terminal subclade I-Y38863 (YTree v14.03, formed ~750 ybp, TMRCA ~700 ybp ≈ 1300 CE). On YFull this subclade has exactly three members: the sample of Charles's tested descendant, another tester’s sample — flagged Poland [PL-14] with YFull's “yid” Ashkenazi origin tag — and one further sample (tester sample IDs are not published here). So the two men sharing Charles's exact YFull branch are an Ashkenazi Pole and one further sample — the same Poland/east-European signal FamilyTreeDNA shows, reached on a separate tree. The full Y-STR panel (~780 markers, reviewed 6 June 2026) is an unremarkable I2-M223 modal haplotype (DYS393=13, DYS390=22, DYS19=16, DYS391=10, DYS385=16-17) with no rare or null markers — consistent with the placement and adding no conflicting signal.

What it shows

I-M223 is an old, broadly European paternal haplogroup. But the relevant signal is Charles's specific terminal subclade, I-Y38863, which on both the FamilyTreeDNA and YFull trees sits inside an Ashkenazi-Jewish, east-central-European cluster (Poland, Ukraine, Belarus, Romania, Russia, with some German presence) — not the northwest-European distribution of the parent haplogroup as a whole. So while the deep haplogroup is unremarkably European, the subclade that actually defines Charles's male line points toward a possible Ashkenazi origin — on the present two-to-three-tester evidence (developed in the next sections).

How recent is the shared ancestor?

This is the part that makes the Y-DNA genealogically useful rather than merely deep-historical, and two labs, analyzing the same single Big-Y file, agree on a medieval window (an independent re-interpretation of one kit, not a second sample). FamilyTreeDNA's Discover estimates place the I-Y38863 branch's formation near 1400 CE and its common ancestor near 1450 CE; YFull's independent tree (v14.03) dates the subclade's formation to ~750 years before present and its most recent common ancestor to ~700 ybp — roughly 1300 CE. Either way the shared ancestor is medieval — a few centuries before Charles's 1835 birth — so I-Y38863 is a comparatively young subclade: a Konze man who tested into it would share a paternal ancestor with Charles within a genealogically meaningful window, a far more probative test than a deep-haplogroup match.

On both trees the branch's members cluster in east-central Europe — Poland, Ukraine, Belarus, Romania, Russia, and Germany — the Ashkenazi heartland, not a specifically Hessian or German-Christian distribution. Several of the YFull samples on and just above this branch carry YFull's “yid” origin tag (its marker for Ashkenazi-Jewish submitters), which is what makes the next section's reading independent of FamilyTreeDNA.

What it does not show

The match cluster — an unexpected Ashkenazi paternal line

The most striking result is not in the haplotree but in who else sits on it. Reading the Y-STR match list (eight matches, tested to 111 markers or Big Y) by their position on the tree, a clear pattern emerges: Charles's closest paternal-line matches are predominantly Ashkenazi-Jewish lineages from the Ashkenazi heartland of east-central Europe.

Position relative to Charles's linePaternal origin(s)Character of the match(es)
Same terminal subclade (I-Y38863) — two Big Y matchesPoland, RussiaBoth Ashkenazi — the two closest matches by clade; their earliest-known paternal ancestors (b. ~1840 and 1866) are documented Ashkenazi families.
One branch up (I-FGC24153) — one Big Y matchLithuaniaAshkenazi — earliest-known ancestor (b. 1856) carries a Hebrew given name; the family's surname was later Anglicized. (FamilyTreeDNA’s refined tree places him on I-FGC24153, closer to Charles’s line than its parent clade I-BY2640.)
Parent clade (I-BY2640) — one Big Y match, about 29 SNPs from Charles’s lineBelarusAn east-European Jewish family (earliest-known paternal ancestor).
Nearby branches (I-S23612, I-M223) — five Y-STR matchesAustria, Germany, Sweden, + unspecifiedMostly recognisably Ashkenazi surnames (one earliest-known ancestor b. ~1640); a single Swedish line is the likely exception.

The “paternal origin(s)” column reports the matches' vendor-listed earliest-known-ancestor countries; the “Ashkenazi” characterization in the right-hand column is the project's inference from those documented ancestors, their surnames, and given names — not an ethnicity label assigned by FamilyTreeDNA.

FamilyTreeDNA's Match Time Tree shows the same structure: both men who share Charles's exact terminal subclade (I-Y38863), and the closest match one branch up (I-FGC24153), are Ashkenazi Jewish — three independent lines, with documented earliest-known ancestors born in Poland, Russia and Lithuania in the mid-1800s, all converging on Charles's line around 1400–1450 CE. The fourth Big Y match, further up on I-BY2640, is also an east-European Jewish family, so all four Big Y matches on the line are east-European Ashkenazi. This is the most striking pattern in the genetic evidence, though it rests on only four testers.

Across the 96 Y-STR matches and the Family Finder list, no Konze, Gans or Kunze paternal line and no Hessian place was found (match list re-read 10 Oct 2026). The Ashkenazi-cluster reading below does not favor Gans, because no Jewish Gans family lived at Trendelburg or Deisel (1823 and 1858 lists, research note, 10 Oct 2026); the book makes the case that he was possibly Karl Ludwig Hofedietz of Deisel, whom a Konze family possibly raised (the book’s case, 28 Oct 2026; not proven). MyHeritage offers no Theory of Family Relativity and no record match for Charles. The decisive test is still a Big Y on a documented Konze man and on a Gans man from the Trendelburg area.

What it most likely means

Charles's strict paternal line — his father's father's father, and so on — descends from a lineage that is, on the present evidence, Ashkenazi-Jewish in origin. Three independent Ashkenazi lines coalescing with Charles's around 1400–1450 CE are most simply read as a common paternal ancestor of that period who was himself part of this Jewish lineage — though with only two-to-three testers this is a working inference, not a demonstrated fact. That reading of the deep male line does not, at least, rest on a single company's analysis: YFull's independent tree reaches the same result, placing the line in the same I-Y38863 subclade, with the same medieval coalescence, among samples it flags as Ashkenazi — though this is an independent re-analysis of the same Big-Y file, not a second tested sample. What remains genuinely open is when and how that line entered the Christian, Hessian, Konze-surnamed milieu in which Charles was born and baptized — by an early assimilation centuries before his birth, or by a later undocumented-paternity event closer to it.

What it does not mean

Why it matters to this investigation

The finding intersects two unresolved threads, and is logged as a new line of inquiry on Open Questions:

Both remain hypotheses. The Y-DNA neither confirms nor refutes them; it adds a concrete, independent constraint that future record work can be tested against.

This is not a new direction for the project — the Y-DNA independently supports an old one. From August 2025, the investigation pursued a Hessian-Jewish paternal-origin inquiry with the Trendelburg researcher, working from documented local Jewish families: the 1740 Trendelburg “Protected Jews” (Seeligmann Ganß — a protected Jew at Trendelburg since 1720, read in the image of the 1731 list, and very probably the man written “Seelmann Gandt” on the 1740 list; no Jew of the canton bore the name Gans in 1812 — and neighbors), the Meimbressen Gans / Segelbaum family, the Christian Gans of Lippoldsberg, and the Stern / Kleeburg line of Hofgeismar. That inquiry was set aside in May 2026 because its basis was a weak surname-resemblance argument (Gans → Gannsen) and because the specific candidates were eliminated or never tied to Charles by a record. The Y-DNA result arrives at the same destination by a completely different road — biology rather than name-similarity — and so independently supports the direction while leaving those specific eliminations standing. It is consistent with the Working conclusion that the name may come from either convergent pool, Gans or Konze (since 5 Jul 2026), and it neither confirms nor excludes the Gans family; it does make the documented Jewish presence in Charles's own locality worth a fresh, evidence-led look. The reactivated thread is tracked at Open Questions · deep paternal origin.

No Jewish Gans family lived at Trendelburg or Deisel. Read in the image (research note, 8 Oct 2026): the October 1823 list of Jewish households in Kreis Hofgeismar (HStAM 18 Nr. 2631) has six households at Trendelburg (Gutmann, Grüntler?, Rosenblatt, Levi Dannenberg, Goldschmidt, Plaut?) and three at Deisel (Nathan Dannenberg, Joseph Ohmsberg, the widow of Levy Katzenstein) — no Gans. The grave list of the Trendelburg Jewish cemetery, which served Deisel and Trendelburg (HHStAW 365/797, 1746–1927), has no Gans either. With the Jewish birth registers of the surrounding communities negative for 1833–41, the idea that Charles was born into a Jewish Gans family at Trendelburg or Deisel has no support. This does not touch the Y-DNA result itself (an Ashkenazi-linked paternal line can lie many generations back), and it does not weaken the Gans surname hypothesis, which rests mainly on his own G-initial signatures; it closes only one route to it.

The 1858 household list confirms it. Read in the image (research note, 10 Oct 2026): the list of every self-supporting Jewish household in Kreis Hofgeismar, drawn up at Hofgeismar on 9 October 1858 (HStAM 18 Nr. 2631, images 156–170; 169 households, 808 persons), has six households at Deisel (Brandenstein, Rosenmeier, Rosenthal, Ohmsberg, Meierhof, Wertheim) and four at Trendelburg (Rosenblatt, Dannenberg, Bloch, Giesberg) — no Gans. The only Gans in the Kreis was Nathan Wolf Gans of Grebenstein. The Staatsarchiv Marburg’s finding aid lists no Trendelburg or Deisel Synagogenbuch after 1812, which explains why no 1824–45 Jewish register has been found for either place. The Jewish route to the Gans surname is not supported and is exhausted online; only two offline files remain (Meimbressen before 1846; HStAM 180 Hofgeismar Nr. 666). The Y-DNA pattern itself stands: an Ashkenazi-linked paternal line can lie many generations back. Charles’s own life was Protestant throughout (St. Marcus marriage 1866, the children’s baptisms, his burial).

Re-checked 7 June 2026 (public FTDNA Discover data): the subclade roster is unchanged — still three tested men (earliest-known paternal origins Germany, Poland, Russian Federation; TMRCA ~1450 CE, 95% CI 1102–1673). Their public group-project memberships add quiet corroboration: of the three, two belong to the Avotaynu Jewish Census project, with single memberships across the German-Jewish (GerSIG), Sephardi-Ashkenazi-Connections, JewishGen-Scandinavia, and Jewish-DNA projects, one in a Jewish surname project, and one each in the Germany and Poland geographic projects — i.e., the subclade's other members publicly research their lines as Ashkenazi lines.

The new match of July 2026. A FamilyTreeDNA alert of 2 July 2026 flagged “two new Y-DNA matches”; filtering the match list by date isolates one new tester, added 1 July 2026 and counted at two marker levels (genetic distance 1 at 25 markers, 4 at 37 markers). It is a distant paternal-line match: it drops below the match threshold at 67 and 111 markers (despite the tester having tested to 111), and is not a Big Y match. Its haplogroup is reported only as I-P222, FamilyTreeDNA's current backbone label for the whole I-M223 branch (the company now assigns unrefined, STR-only predictions to I-P222 rather than I-M223), so it sits far upstream of Charles's terminal I-Y38863 and cannot be resolved into or against his subclade. Its structured fields are empty, but the tester’s free-text profile (read 18 July 2026) says he is searching for his own male-line surname: his third-great-grandfather was born out of wedlock in Hannover in 1795 and took his mother's surname, the true paternal surname possibly having been Neumann. Three observations, all held at low weight. First, the pattern — illegitimate birth, mother's surname adopted, paternal surname uncertain — mirrors one already documented in the Gans line (the 1844 Hellmuth/Gans case), but it was the ordinary practice of the period across German states, not a fingerprint of any one family. Second, Hannover borders this project's Weser-corridor parishes, yet “Hannover 1795” names neither a parish nor a year inside Charles's birth window. Third, as a guard against a false lead: this Neumann is a surname in Hannover and is not the Naumann of the Hümme records, which is a place name — different spelling, different grammatical role, no demonstrated connection. The genetic weight is low: genetic distance 1 at 25 markers but 4 at 37, with the tester dropping out of the list at 67 and 111, is the signature of a distant relationship. The match neither strengthens nor weakens any conclusion.

Match individuals are not named here, per the project's living-relatives policy; the pattern is described from surnames, recorded earliest-known ancestors, and paternal countries of origin in the FamilyTreeDNA match list (retrieved 30 May 2026; Discover re-checked 7 June 2026; match list re-checked 2 July 2026). Kit identifiers can be supplied to bona-fide researchers on request.

Autosomal DNA — the whole-ancestry estimate

AncestryDNA & MyHeritage · descendant test

Autosomal DNA recombines each generation and reflects all of a person's ancestry, not one line. The test here is from a descendant of Charles, so Charles is only one of many ancestors contributing to the estimate — and a smaller share with each generation of distance. The kit has been run through two independent vendor reference panels — AncestryDNA and MyHeritage — which segment Europe differently but agree on the essentials.

The Germanic component (AncestryDNA)

Among the descendant's fifteen reported regions, the Germanic cluster dominates the Western-European portion:

RegionShare
Southern Germanic Europe33%
Northwestern Germany16%
The Netherlands5%
Germanic / Western-European subtotal~54%

The remainder is largely British-Isles and Celtic ancestry (Northern Wales & NW England, Central Scotland & Northern Ireland, the Hebrides, Connacht, Donegal, Isle of Man, Leinster, and Southeastern England) entering from other lines in the tree, plus several smaller regions.

The same kit through a second panel (MyHeritage v2.5)

MyHeritage's independent reference panel (Ethnicity Estimate v2.5, retrieved 7 June 2026) returns ten regions for the same descendant — all of them European:

RegionShare
Germanic36.4%
English18.5%
Scottish and Welsh17.0%
Dutch12.0%
Irish3.8%
French3.7%
Danish3.4%
East European2.9%
North Italian1.2%
Breton1.1%
Germanic / Dutch subtotal~48.4%

The two vendors draw their region boundaries differently — MyHeritage's single “Germanic” region spans roughly what Ancestry splits into “Southern Germanic Europe” and “Northwestern Germany” — but they converge on the same picture: a dominant Germanic / Dutch block of roughly half the genome (~48% MyHeritage, ~54% Ancestry), a large British-Isles / Celtic remainder (English, Scottish and Welsh, Irish, and Breton total ≈40% at MyHeritage), and small trace regions. Notably, neither vendor reports a European-Jewish region — the same below-threshold silence discussed under the match list below. Agreement between two independently built reference panels strengthens confidence in the broad admixture picture, but it does not relax either of the limits that follow.

What it shows — and its two limits

A Germanic block of roughly half the genome — reported by both vendors — is consistent with Charles's documented German origin and with the broader family reconstruction. But two limits keep it from confirming anything specific:

The FTDNA match list — what ~14,300 autosomal matches add

Beyond the ethnicity estimate, FamilyTreeDNA's Family Finder returns about 14,300 autosomal matches for the tested descendant. Their structure is itself informative:

The apparent tension with the ethnicity estimates — neither of which flagged a European-Jewish region — is not a real contradiction: small Ashkenazi segments can fall below an estimate's reporting threshold, especially once diluted across the generations down to a descendant. Read together, the two suggest an Ashkenazi paternal contribution that is real but limited and/or deep.

The MyHeritage match list — a German-resident paternal cluster (June 2026)

The same descendant's kit returns 6,896 matches at MyHeritage (6,991 on a re-check of 18 July 2026; the ninety-five added in the interval run 9–21 cM, carry no target surname, and include a single Germany-resident tester at 9.2 cM — all below the 30 cM threshold this project monitors), whose tester base is far more continental-European than FTDNA's or Ancestry's. Crucially, both of the tester's parents and a sibling have also tested there, so every match can be assigned to the paternal or maternal side by shared-match triangulation — a discriminating power the FTDNA list lacks. Reviewed 7 June 2026:

The kit was attached to the project's family tree on MyHeritage on 7 June 2026, activating automated tree-matching (Smart Matches™ live immediately — the import returned 3,187 individuals and 2,635 Smart Matches, which are tree-to-tree matches and not DNA matches; Theories of Family Relativity™ pending the next recalculation). Resolved 18 July 2026: six weeks and one recalculation later, filtering the full match list for Theories of Family Relativity™ returns none at all — zero theories across all 6,991 matches, not merely none for the German cluster. This is the expected result rather than a disappointing one, and it is worth stating plainly: a Theory is built by tracing a documented path through other users' trees to a shared ancestor, and the shared ancestor this project needs sits one rung above Charles — in exactly the undocumented gap the investigation exists to close. Tree-matching cannot bridge a link that no tree records. Granular workings — side assignments, segment figures, the surname-sweep table, and the AutoClusters parse — are in the research notes (research note, 7 Jun 2026); living matches are not named here per the privacy policy.

Re-check across Ancestry & MyHeritage, 28 June 2026

A cross-platform pass to test whether the trees or the autosomal matches can name Charles's parents — they still cannot, but the German paternal cluster was sharpened slightly.

Net: as of 28 June 2026 the documentary trees and the autosomal match lists still do not name Charles's parents or siblings; the MyHeritage German paternal cluster remains the single best living lead, now leaning marginally toward a Hessian rather than an Oberharz origin, and turns on the members' reply or on Y-testing a documented Trendelburg–Deisel Konze male. Workings: research note, 28 Jun 2026.

A Kontze surname hit, tested and ruled out (19 July 2026)

Weekly monitoring of the MyHeritage kit produced its first-ever hit on the ancestral-surname search for Kontze — which, on investigation, turned out not to bear on Charles. It is recorded here because a negative that has been checked is worth more than one that has not.

Net: the 19 July surname hit is a checked negative, not a lead. It changes nothing about the cluster or the conclusions, and the highest-yield next step remains Y-testing a documented Trendelburg–Deisel Konze male. Workings and the parallel documentary note are in the monitoring log (19 July 2026).

What the DNA changes — and what it doesn't

Nothing in the genetic results promotes a claim to Confirmed, and nothing refutes one. The Y-DNA and autosomal evidence both corroborate a German / Germanic origin in general while remaining silent on the two questions the project most wants answered: was the parish Trendelburg, and was the surname Gans or Konze? Those conclusions continue to rest on the documentary record (the surname trail and the “Freundburg” / “Deisse” origin decodings) and are held Working accordingly. See the claims dashboard for how this feeds the load-bearing claims, the methodology · genetic evidence section for the source-rating treatment, and open questions · DNA for the live thread.

The highest-yield next step

Because the Y-DNA line is the one piece of evidence that could directly test the surname conclusion, the most valuable single action is targeted recruitment:

If you descend from the Trendelburg–Deisel Konze / Kontzen family, or from any of these lines, the project would welcome contact — see Contribute.

Genetic results summarized on this page: FamilyTreeDNA Big Y-700 (haplogroup I2-M223; terminal subclade I-Y38863), AncestryDNA and MyHeritage (Ethnicity Estimate v2.5) autosomal estimates, the FTDNA (retrieved 30 May 2026; match list re-checked 2 July and 18 July 2026) and MyHeritage (retrieved 7 June 2026; re-checked 18 & 19 July 2026) match lists, and the FTDNA all-segments export (7 June 2026). Page first published . Living DNA matches are not named on the public site per the privacy policy; kit identifiers can be supplied to bona-fide researchers on request.