Skip to page content
Catalogue · 27 Sep 2026
Glasgow Surname ProjectPaternal-line research
August 2026 snapshot
The Glasgow paternal lineResearch edition · August 2026 evidence

Before the name.
Behind the family.

A North Sea family. A medieval British fork. A Scottish surname that spread through Ulster and across the Atlantic.

The DNA becomes useful history when we connect the branches to people, places and periods. Here is the project’s leading reconstruction—and the clues that give it shape.

Read this as a historical reconstruction. The genetic branches provide the structure; the migration routes and named medieval connections are the project’s interpretation. Sources and detailed reasoning sit beside each chapter.

How to read the DNA ↓
The key to the diagrams

A DNA label is an inherited signpost.

A Y-DNA branch is a line of fathers and sons. A SNP is a change at a particular DNA position that can mark part of that line. Men further down the tree retain the older signs and share additional ones.

FT4811Older shared family
FTA30932One descendant branch

A Churnside/Brown tester carries the older FT4811 ancestry and the later FTA30932 branch. Glasgow follows a different path from the same older family.

Four terms used below

Haplogroup: a named branch of the paternal tree, such as R-FT20271. The long label is an identifier, not a ranking.

TMRCA: the estimated date of the most recent common ancestor of the sampled lines. Think “when this family branches”, rather than a date printed on a travel record.

STR distance: differences in repeated DNA patterns. These are useful for finding close candidates. A Y-111 result compares a particular marker panel.

Kit: an individual test. Its earliest reported ancestor is the historical person at the end of that tester’s paternal paper trail.

01
North Sea → medieval Britain

Why place the arrival
around the Norman era?

c.1066–1150
Leading arrival model

The useful clue is a change in the family’s geography: older northern cousins, then a recognisably British set of branches.

Further back, the line belongs to the North Sea world represented by Z17 and S14827. Around S14827, the project identifies Swedish, Danish and Norwegian sister lines. Further down, FT4811 brings together the paternal ancestors of the tested Glasgow, Churnside, Brown and Wright lines. A separate project page reports a Duffield line at FT32941, but the current supplied dataset contains no identified Duffield kit or pedigree with which to verify that placement.

That is more informative than simply calling the line “Scandinavian”. The northern cousins give it an older setting; the British-linked branches give us a later one. The question becomes how that part of the family moved between them.

The project’s leading answer is a family reaching Britain in the late eleventh or early twelfth century, possibly through Normandy. FT4811’s estimated ancestor falls around 1044 CE; the next branches sit naturally within a story of medieval settlement, regional movement and the adoption of different surnames.

The Norman-era model joins those clues through a historical mechanism: men and households moving with the networks that connected Normandy, the English Midlands and the Scottish borderlands. It supplies a period and a route to investigate even while the migrant’s name is missing.

The decisive fork

Churnside and Brown are part of the bigger family.

Choose a branch to see what it adds.
The shared paternal familyR-FT4811Common ancestor estimated c.1044 CE

The point of the fork: Glasgow is one outcome of an older paternal family. Comparing the other outcomes helps reconstruct its history before anybody used the Glasgow name.

Branch order, northern sister lines and medieval route: S9 Inspect the dates →
02
A tested branch beside a documentary record trail

Can the medieval records
explain the Glasgow branch?

c.1100–1500
The surname-forming question

The genetic and documentary evidence now form two parallel tracks that have not yet been joined.

FT32941 is ancestral to FT25406, which contains the tested Glasgow and Glasgo lines. The project’s older Duffield page reports John Duffield (Duffield-471) at FT32941, but the result identifier, raw placement evidence and tester-to-root pedigree are absent from this supplied snapshot. The Duffield association is therefore a lead to verify, not a settled label for the branch.

Duffield Castle really was a de Ferrers centre around the Anglo-Norman period. That establishes a plausible historical setting only. It does not put Roger de Duffeld, John of Huntingdon or an FT32941 ancestor in the de Ferrers household.

The named records sharpen the problem. Roger de Duffeld’s inspected occurrence is a 1194 Yorkshire Pipe Roll debt, not a 1190 poll tax or a Derbyshire charter. Master John of Huntingdon served Bishop Jocelin’s Glasgow household, but a charter names him alongside Roger de Glasgu. The Glasgow locative was therefore already in personal use while John remained de Huntedun; no source shows him changing names.

At the later end, John Glasgw in Stirling in 1475–1479/80, John de Glasgow alias Smith in 1506, and the Saltmarket John recorded from 1527 are separate working identities. Chronology permits connections, but no inspected act joins their property, relatives or aliases.

The principal bridge candidates, refreshed

Three real records—and the exact gaps between them.

Documented people · not a pedigree
Yorkshire · Michaelmas 1194

Roger de Duffeld

Documented: owed half a mark after failing to produce a person for whom he had acted as pledge or surety. North and South Duffield in Yorkshire are possible sources of the locative. No Derbyshire, de Ferrers, Glasgow or Y-DNA link is stated.

Open Roger’s research page ↗
Glasgow · fl.1179–1208

Master John of Huntingdon

Documented: Bishop Jocelin’s clerk and later official. He appears in the same episcopal-property network as Roger de Glasgu. No act calls him de Duffeld, relates him to Roger, or makes a later de Glasgu bearer his descendant.

Open John’s research page ↗
Glasgow · 1506; possible later cluster

John de Glasgow alias Smith

Documented: jointly acquired a four-shilling High Street annual rent with Sir Allan Smith. The act does not call John a smith or Allan’s relative. Identity with the 1527–1553 Saltmarket holder remains unsupported; Eufame Craig as that older John’s widow and William as their son are property-based reconstructions, not relationship clauses.

Open John’s research page ↗
Named-record ledger: every proposed bridge in chronological order

This ledger separates a dated occurrence from the relationship the origin theory would need. Two explicit medieval relationships—Robert to Alexander in the Dublin guild material and John to Malcolm in 1394—remain isolated family units; neither joins the full chain.

DatePerson or clusterLatest documentary findingWhat remains unproved
c.1080de Ferrers at Duffield CastleThe castle and de Ferrers setting are independently documented.No genetic sample or record connects the sampled paternal line to the household.
c.1175–1199Roger de Glasgu ↗Witnessed Bishop Jocelin’s grant of a Glasgow burgh toft and Clyde fishing right; John of Huntingdon appears in the same act.The joint witness context is association, not kinship or succession.
1179–1208Master John of Huntingdon ↗Clerk and later official in the Glasgow episcopal household.No Duffeld alias, father, son, or name-change act.
1194Roger de Duffeld ↗Yorkshire Pipe Roll: half-mark debt in a pledge/surety proceeding.No Derbyshire residence, estate office, de Ferrers tie or Scottish link.
1238/39Alexander, son of Robert de Glascu ↗The Dublin guild roll explicitly states Robert → Alexander. A printed Free Citizens roll adds no secure identifier.Robert may be the earlier guild entrant, but no cross-reference, property or occupation proves it; Alexander is not the later escheator.
1259John de Glasgu ↗Chaplain of Bishop Gamelin in a St Andrews act.Not called Master, Gamelin’s brother, or John of Huntingdon’s descendant.
1283Alexander, messenger’s son ↗ / Alexander, constable’s son ↗One was son of the late messenger of Glasgow; the other son of the former constable and an adjoining landholder.The men must remain separate; neither father’s phrase securely proves inherited Glasgow surname.
1289/90Alexander, royal escheator ↗A damaged receipt and Exchequer context place an Alexander in royal administration south of the Forth.His surname reading and identity with either 1283 Alexander or Dublin’s Alexander remain unresolved.
c.1291Master Walter de Glasgu ↗Witnessed Melrose charter material; his title indicates advanced education.Too late to bridge John of Huntingdon directly to the 1259 John; no office or relatives named.
1299John of Glasgow, Holyrood ↗A member of the abbey community who swore fealty to Edward I.No parentage or office; not merged with the 1259 chaplain or the 1343 payee.
1315–1322William de Glasgow ↗Instituted Vicar of Corbridge in 1315 and witnessed a deed in 1322.No relationship to the Scottish bearers.
probably 14th centuryAdam de Glasgeu ↗Berwick burgess who granted Hiddeslaw land in Bondington to Melrose Abbey; the charter is undated.No son or successor; it should not be forced into c.1280 or made the escheator’s father.
1343John de Glasgu, royal-account payee ↗Received 7s 6d concerning the board or table of royal servants.No office is stated; no repeated associate joins him to Holyrood’s John, Master John or the 1394 father.
1377–before 1419Master John de Glasgow ↗A distinct later clerical career as chancellor of Dunkeld.Not the 1259 chaplain or Holyrood’s 1299 John; parentage unproved.
1394John de Glasgu ↗ and son Malcolm ↗An Exchequer entry explicitly identifies Malcolm as John’s son and applies de Glasgu to John.The pair is real, but the entry does not style Malcolm de Glasgu or join either man to the fifteenth-century burgess.
1395–1397William, physician de Glasgu ↗Two royal accounts probably identify one physician through repeated name, occupation and locative.Not proved to be the William priest in 1394; no family relationship is stated.
1447–1455John de Glasgu, Glasgow burgess ↗Same civic status, place and notary strongly support one man across both dates.No transfer or relationship reaches the Stirling or Saltmarket men.
1475–1479/80John Glasgw of Stirling ↗Witnessed two Stirling property acts.Possible predecessor of the Saltmarket John only; not John alias Smith as a documented fact.
1495Alan GlasgwNamed as the victim in a remission produced at the Jedburgh justice ayre.No residence, occupation, family or later Ulster descent is recorded.
1506–1553Alias-Smith and Saltmarket clusters ↗The 1506 alias is secure; its only explicit descent is Robert Watson → Agnes. A separate Saltmarket title passes from a John in 1527 to William by 1528/29; a late John bounds it in 1553.Alias-Smith = Saltmarket John is unsupported. Eufame Craig as the older John’s widow and William as their son are leading property reconstructions, not direct relationship clauses.

Quarantined claim: David de Glasgu remains an unverified report of a Lennox charter witness. No charter number, manuscript reference or checkable printed page has been recovered, so he is not counted as an attested bearer. The unsourced FamilySearch Master John → William pedigree is likewise excluded: it has no attached historical sources and its displayed dates make William’s child ten years older than William.

Ferrers, Ferrier and Farrier are three different questions

de Ferrers is the medieval aristocratic family associated with Duffield Castle. Farrier/Ferrier here means three modern Y-111 match lines: two report William Farrier and Susanna Abell’s 1796 Philadelphia marriage, while one reports Henry Ferrier, born about 1758 at Woodnesborough, Kent. Their distances from B580327 are 4, 4 and 5, but all remain at broad R-M269 in this dataset.

Name resemblance does not connect those match lines to the de Ferrers earls. A Big Y upgrade can determine whether a Farrier/Ferrier test belongs inside FT20271, on an older collateral branch, or outside this cluster; a documented pedigree must then explain when the surnames diverged.

Pipe Roll record S14 · Glasgow episcopal charter S15 · 1283 Alexanders S18 · escheator receipt S19 · 1506 catalogue S16 · Saltmarket register S17 · modern match snapshot S0
03
A Scottish family expands

The tree reaches
Ulster and the Atlantic.

c.1500–1800
Surname-era diversification

FT25406 and FT20271 give us two layers of Glasgow history: the wider surname family and a younger set of Scottish, Ulster and American branches.

The Henry Glasgo Big Y line shares FT25406 with the later cluster. The FT20271 lines share three further named changes. Their common ancestor is estimated around 1583, with the source’s broader range running from 1387 to 1728.

This is the genetic setting for the project’s Ulster-Scots reconstruction. It places a shared paternal family behind lines later found in Scotland, County Antrim, Derry and America. Scottish settlement in Ulster, movement across the North Channel and later Atlantic migration provide a coherent historical sequence for those locations.

The useful picture is a branching migration, rather than a single itinerary followed by every descendant. Some households remained in Ulster; some moved or returned to Scotland; others established American lines. Religion, work, land and kinship can all belong to the explanation, with individual records deciding which mattered for each family.

This also explains why the Henry Glasgo line matters even when it is farther away on the tree. It preserves an earlier division of the Glasgow family. Its American history can illuminate the surname’s wider dispersal, while the FT20271 lines tackle the more recent Scottish–Ulster connections.

Scottish rootsBurgh and family networksUlster connectionsSettlement and repeated movementAtlantic branchesDifferent families, different routes
FT25406 / FT20271 structure and reported roots: S0 · Historical interpretation: S9
04
From the long history to the actual tests

Where does Alexander’s
line fit within that family?

1700s → today
The near-family questions

Alexander’s line has a clear place in the wider tree. The immediate task is to resolve the family inside FT20271.

The reference test, B580327, comes from the line of Alexander Glasgow, born about 1811 in County Antrim. Its closest standard Y-111 match in the supplied set is the James J. Glasgow line, kit 1002232, at three steps.

The pairing is more interesting than a small distance alone. Both share DYS714=27, while the other five core tests carry 26. SAPP groups the pair around that same feature and supplies an approximate eighteenth-century search horizon. Together, these make a closer Alexander–James J family connection a useful working hypothesis.

That is a reason to investigate their Antrim and American family networks together: candidate parents, siblings, uncles, migration companions and repeated associates. The SNP files may refine their shared branch; the records can put names onto it.

The reported William c.1655 line is also important. It has the fewest differences on the extended Big Y STR comparison, 3 of 650. James J leads on the standard panel; William leads on this larger comparison. Reading both gives us two strong comparison targets rather than making one measure carry the whole relationship.

A family where the tests already explain the branching

Robert’s three sons show how DNA and records work together.

The project traces four Big Y tests through William, John M. and James M., sons of Robert Glasgow (1749–1839). Changing the highlighted evidence below shows the same family at three levels.

Robert Glasgow1749–1839 · common family ancestor
WilliamOne tested line959947
John M.One tested line200475
James M.Tests through two sons999763 · 478604
Uses the project’s reported paternal pedigrees and kit assignments.Open the full family evidence →
Why more DNA markers help—and what FT6135 could add

John M.’s kit 200475 and James M.’s kit 999763 are identical on the displayed Y-111 panel. Their named SNP results still distinguish James’s FTE32242 branch. That is a useful demonstration of complementary resolution: STRs recover the close family, while a SNP picks out one part of it.

FT6135 is another family-level lead. The comparison lists display it in William’s and John M.’s tested lines. The two James M. entries currently have an unknown state in this dataset. A direct check could turn that clue into a broader family marker or reveal a more specific pattern. Explore those outcomes →

Pairwise distances, marker states, SAPP output and reported family audit: S0
05
Make the picture more specific

The next result should
fill in part of the story.

There are several useful ways forward. Each answers a different question; the best choice depends on which part of the family history we are trying to resolve.

Alexander’s near family

Compare the closest line properly.

Kit 1002232’s full results could refine the James J. connection. A second independently branched Alexander descendant would identify which private changes were already present by Alexander’s generation.

Follow this research path →
The Ulster family

Place the older Antrim branches.

Testing the Robert c.1710 and James William c.1731 Kilwaughter lines would connect known local family history to the genetic structure. Either could reveal a new branch or an older split.

Follow this research path →
The medieval origins

Verify the cousin branches, then use their geography.

Earlier Churnside, Wright and Brown paternal roots can sharpen the route into Britain. The separately reported Duffield placement first needs an identified kit and a sourced tester-to-root pedigree. Documentary people remain separate until a record joins them.

Follow this research path →
A useful test—with a necessary name distinction

What are the Farrier and Ferrier matches telling us?

Two tests report the same William Farrier–Susanna Abell root and sit at GD 4; a third reports Henry Ferrier of Woodnesborough, Kent, at GD 5. They have no terminal SNP placement or supplied kit numbers. A Big Y result could locate the connection, but none is presently linked to the medieval de Ferrers family merely because the names resemble one another.

See all three matches in context →
Testing targets and match distances: S0
The whole picture

The missing names are the research.
The wider family is already taking shape.

The tested branches establish a wider paternal family. Which medieval surnames and recorded people belong to it remains the documentary and testing problem; the later branches tell us where to search next.

Historical interpretation / the reasoning behind the routeBack to the story →

Why this route?
How the clues add up.

The North Sea ancestry and later British branches are the broad genetic picture. An Anglo-Norman route is one project reconstruction for the interval between them. The current documentary audit has not identified the migrant, a de Ferrers connection or a medieval Duffield genetic line, so the model is tested here rather than presented as a pedigree.

Leading project reconstruction · not proved

North Sea ancestry → possible Normandy stage → Britain → Scottish branches

An arrival or establishment around 1066–1150 is the project’s working scenario. It combines a northern family background and medieval British branch dates with proposed regional mechanisms. The dated records currently show separate people and places, not a continuous descent.

1
The broad geographic change

Older northern relatives; younger British-linked branches.

S14827 connects the path towards Glasgow with Swedish, Danish and Norwegian sister lines. FT4811 is the later hub for the sampled Glasgow, Churnside, Brown and Wright lines. A separate project page reports a Duffield result below it, but that placement cannot be verified from the current dataset.

What this adds: we are investigating the movement of one particular paternal branch within the North Sea world, rather than treating all U106 ancestry as one migration.

2
The period of British diversification

The medieval ancestor makes the Norman era relevant.

The supplied FT4811 estimate centres on 1044 CE, with a reported 95% range of 697–1313. FTA30932 is given a c.1120 label, while FT32941 lies on the genetic path towards the tested Glasgow lines. Those dates make the eleventh- and twelfth-century world a productive search period, without assigning any recorded medieval person to a branch.

What this adds: a useful period to join genetic ancestry to historical movement. A lineage already present in Britain could also branch at this time; its earliest verified geographic anchors are what would help choose between those histories.

3
A proposed mechanism of movement

Retinue and patronage are hypotheses to test.

Duffield Castle’s de Ferrers setting, the proposed Vipont/Langton context near Chirnside, and Scottish clerical and burgh networks could explain regional movement. But Roger de Duffeld’s known record is in Yorkshire in 1194, Master John of Huntingdon retained that name in Glasgow, and neither is linked to Roger de Glasgu by kinship.

What this adds: a structured model with documentary predictions. It becomes persuasive only if sourced collateral pedigrees or explicit records connect the genetic branches and named people; name resemblance and compatible chronology are insufficient.

The family being explained

The medieval fork in full.

Genetic relationships from the supplied timeline S9
The key analytical distinction:

Several separate surname branches can strengthen the case for an older, pre-surname family. Their earliest sourced locations are then more informative than a modern surname map. Churnside’s Berwickshire lead, Brown’s American root and Wright’s nineteenth-century London anchor contribute different amounts of geographic information.

Alternative routes through the same wider history

What changes when we change the arrival model?

Select a route. The comparison keeps the same genetic family and asks how its later geography might have developed. These are qualitative reconstructions, not calculated migration probabilities.

What about the earlier “Continental Saxon” route through Normandy?

The source timeline suggests that the ancestors may have reached the Norman coast before the Viking period, becoming part of the continental Saxon population around the Bessin. In that version, later Norman identity grows out of a family already living in the region.

This is a deeper layer of the same route hypothesis. Its appeal is that it provides a longer North Sea–Normandy connection. The S14827 ancestor date supplies the older family context; establishing a specifically Saxon, Norse or mixed Norman stage would come from finer branch geography and historical links. Keeping those stages distinct lets the broad Norman-era model remain useful while the earlier route develops.

Read the time depth

What each date contributes to the story.

Dates retained from the supplied timeline

Start with the shape: an older northern split, medieval surname branches, then a Glasgow-specific and early-modern family. The centres organise the narrative; the ranges show how broadly to search around them.

The narrow amber band below marks the 1066–1150 historical scenario. It is overlaid for comparison with the ancestor estimates, rather than calculated from them.

Reported ancestor range Arrival model · 1066–1150
Before Britain

S14827 · c.379 CE

Useful as the older northern family context. Descendants have many generations in which to move before the later British branches become visible.

The medieval family

FT4811 · c.1044 CE

Puts the shared ancestry of several later surname groups near the period around which the project builds its British settlement model.

The Scottish surname

FT25406 · c.1431 CE

Focuses the search on the older Glasgow/Glasgo family, including the medieval-to-early-modern Scottish documentary bridge.

How the source’s dates and ranges are handled

The timeline repeats the same 1044 CE centre and 697–1313 range for FT4811 and FT32941. Their order comes from the tree structure; the repeated estimate supplies no measurable interval between them. FTC49014’s c.500 and FTA30932’s c.1120 are timeline labels without supplied uncertainty ranges, so the graphic shows points for those two.

FT20271’s 1583 estimate is a shared-ancestor estimate for the sampled lines. Individual families could move to Ulster or America at different later dates. Reported date ranges and the c.1066–1150 route window are kept in separate data fields in the downloadable model.

The longer background

Follow a stage in greater detail.

A practical way forward

Improve the edges of the reconstruction.

Verify the reported Duffield placement, trace every sampled cousin line to earlier sourced places, and test the named medieval records without merging their identities. Several consistent findings can strengthen or redirect the route before the migrant himself is identified.

Open the origins research plan →
03 / Pairwise workbench

How do these
two family lines connect?

Choose two individual tests. See their shared paternal context, the measured differences and what that comparison adds to the family history.

Start with
Reported marker states for this pairA selected subset, not a fresh calculation from all 111 alleles

Only marker states explicitly described in the uploaded page are shown. “Not supplied” is not an allele value. The DYS451 / DYS511 label conflict is excluded from this comparison. S0

Directional variant counts are available only for reference-kit pairs. They describe reported state differences, not dated mutation events. The extended STR mismatch count is a different measurement from standard-panel allele-step GD. S2

Family structure / older branches to tested descendantsBlock Tree snapshot · 12 Aug 2026

One family.
Several levels of branching.

Read from the older shared ancestor down towards the individual tests. Each fork narrows the family; the reported pedigree view then puts the later generations alongside their results.

What this split says about the line’s arrival in Britain →
Assigned SNP node in supplied tree Individual tested tipNo branch lengths or calendar scale implied
Reported upstream path R-FT4811→R-FT32941 / FTA35069
Parent block · 4 named SNPs

R-FT25406

FT25406 · FT16394 · FT18145 · FT26594

Discover ↗
No named child assigned
Henry Glasgo lineUnnumbered Big YAssigned FT25406
Kit 325862 is a different test with the same reported root. Its terminal SNP remains unresolved.
Named child block
3 named SNPs · 7 core samples

R-FT20271

FT20271 · FGC5690 · FT16542

Discover ↗
5 tips without a named child
Named child
2 samples

R-FTE32242

“Basal” does not mean unchanged. These modern tips still carry private variants. Here it means no named downstream branch is assigned in the supplied snapshot—not a full set of documented negative genotypes.
A medieval collateral branch

R-FTA30932 → shared FT4811 root

Churnside and Brown lie on the other side of the FT4811 fork from the FT32941 → Glasgow path. Their kinship adds a wider historical comparison; it does not place them within FT20271. S9

Read the medieval context →
Not placed by this tree

Marker-only results

325862, B835762, 254947, N18544, 333002 and 794462 remain outside terminal SNP placement. Reported pedigrees and STR resemblance are not substitutes for a result.

Inspect the placement hypotheses →
Reported branch agesHistorical working estimates, not refreshed Discover results
FT254061431 CEReported 95% interval: 1199–1608
FT202711583 CEReported 95% interval: 1387–1728

Reproduced from the supplied project timeline claims. These are common-ancestor estimates, not the birth dates of every SNP in an equivalent block. Live values could not be independently refreshed for this revision. S0

Recent branch assignments and pedigree claims: supplied Y-DNA page. Medieval fork: supplied timeline S9. S0 Interpretation of Block Tree displays: S2

Research tools / STR comparisons

The patterns that
bring the families together.

The seven core tests reveal a close Alexander–James J pairing and a tight Robert-1749 family. Use the matrix to compare any two lines, then inspect the marker changes that make the pattern.

Seven-kit Y-111 matrix

Supplied allele-step distances
Fewer stepsMore steps0 means identical on this STR panel; SNPs can resolve branches within such a match.
Source matrix with full root labelsThe same 21 distances in the earlier audit format
New calculation from supplied matrix

One minimum-spanning arrangement

1 / 8
Unrooted minimum spanning treeAn arrangement of modern tested kits that minimises total STR edge weight. It is not a descent tree.

No arrows, ancestral people or dates are attached to these edges. All eight solutions include Alexander–James J at GD 3 and William–Alexander at GD 5; the equal-cost alternatives occur at the identical Glasgow-12 haplotypes. MST stability is not genealogical proof. S8

How robust is the drawn network?Alternative arrangements and the matrix audit
8equally short spanning trees
15total edge weight in each
4 / 35quartets fail exact tree additivity

For distances measured along a single additive tree, the two largest of these three quartet sums must be equal. Take William c.1655 (W), Alexander (A), James J (J) and John M. (R):

d(W,A) + d(J,R)5 + 5 = 10
d(W,J) + d(A,R)6 + 6 = 12
d(W,R) + d(A,J)7 + 3 = 10

The largest two values are 12 and 10, not equal. This is enough to reject an exact additive fit to the supplied endpoint distances. It does not reject a real paternal genealogy or prove a specific back-mutation. It shows why an STR layout needs an explicit model rather than being read literally as a lineage.

Four of the 35 seven-kit quartets fail; all four involve W, A, J and one of the four family kits, so these are not four independent biological contradictions. The matrix is symmetric and passes all triangle-inequality checks. S7S8

Inspect the signal

Which marker patterns matter?

Branch-weighted marker readingObserved state, defensible interpretation and placement
Unresolved source label: the narrative says DYS511=11 for B696189; the SAPP reconstruction says DYS451 10→11. These are different marker names. Neither has been silently corrected or used to reconstruct a raw haplotype.
Distance calculations and safeguardsWhat was retained, calculated and not recomputed

Retained: the supplied matrix and reported reference comparisons. The page describes 102 displayed Y-111 loci representing 111 allele values. The complete allele rows were not attached, so that description and the original GD algorithm were not independently reproduced.

Calculated here: symmetry, triangle inequalities, all 35 quartet tests and the eight minimum spanning trees on the seven labelled modern kits.

Do not mix: stepwise STR differences; numbers of mismatching extended STRs; SAPP’s adjusted path distance; GroupingApp RDist; or SNP state counts. DYS389II contains DYS389I, and null/multi-copy states need the relevant calculation rules.

Private averages are not validation: the source proposes tip counts 5, 1, 5, 1 and 4 for five basal FT20271 kits (mean 3.2, displayed as 3), and 1 and 2 for the FTE32242 pair (displayed average 1). Rounded aggregate compatibility cannot independently verify those exact assignments or the directional variant audit.

S0S1S2S4

Research tools / inherited SNP markersSite calls as reported in the supplied page

Which changes mark
which part of the family?

FT20271 identifies the shared branch, FTE32242 picks out James M.’s line, and FT6135 is a promising family-level lead. The question is how each change is inherited across the tested descendants.

T / derived

A positive call at the specified allele.

C / reference

An explicit non-carrier call for C→T.

? / unknown

Not displayed, not supplied or a no-call.

FT6135 · C→T

Not placed on the family tree
Tested lineAvailable stateActual evidence available here
B580327 · AlexanderC / reported referenceSource reports GT 0/0, DP 40, PASS. The VCF itself is not attached.
959947 · William branchT / displayed derivedDescribed in the source’s comparison audit; no match-kit raw call supplied here.
200475 · John M. branchT / displayed derivedAs above; the final pedigree continuation is also labelled probable.
999763 · James M. / William Allen? / not displayedNo explicit C or T call supplied. This is not an observed negative.
478604 · James M. / Samuel Lyle? / not displayedNo explicit C or T call supplied. This is not an observed negative.
Next discriminating result

What would the two James M. kits show?

This changes the interpretation—not the stored data.

FT6135 decision tableThe direct result required and the boundary of each conclusion
Reference-line comparison

Reported directional state differences

Not a genetic clock

Counts are carried over from the source audit. They include multiallelic and off-tree states, and some pairs include additional named-site differences. They are not all equivalent, tree-counted, independent SNP mutations.

Full directional comparison auditExact pair-level counts and historical reading
Reference VCF claims and five named private variantsTechnical audit, provenance and the multiallelic-site distinction
Not re-verified from raw files. The page reports a 27 Oct 2022 B580327 raw file, with 11 Aug 2026 exports. Reference assembly is not stated in the supplied HTML. Coordinates below must not be used for new raw comparisons until the build is recorded.

Five exported tip variants and the additional C→G call

The source reports five exported private variants, plus the additional multiallelic-site C→G call; all six were reported PASS, with depth 25–78. None of the displayed matches is reported to share these states. That is not a direct all-kit genotype audit.

The claim “15/15 match-side positions covered” has been retained as a source claim, not elevated to proof of 15 negative genotypes. A quality BED interval shows coverage eligibility, not by itself the reference base. Rechecking needs the actual genotype/callability evidence, the assembly and coordinate convention.

The source also reports 829 populated reference DYS/FTY fields. A reference export alone cannot reveal a match’s extended marker differences. S0S3S6

YFull cross-checkReported review: 31 August 2026 · not a new public-tree refresh
Reported outcome

Compatible calls. Different tree resolution.

The source reports YFull v14.05.00 placing the VCF sample as a singleton under FT3761, with FGC5690 positive but treated as private. FTDNA groups FGC5690 with FT20271 and FT16542.

No new close relative reported

21 “private” calls are not 21 recent mutations.

The list reportedly includes upstream calls. A coarser comparison tree can call a state private even when another service has already placed it on a shared branch.

YFull’s interpretation is a separate calling/annotation process on the same underlying sample, not an independent biological replication. The logged-in report was not provided here. S0

Research tools / SAPP reconstructionSupplied SAPP V4.27 run · 12 Aug 2026

Turn marker patterns
into research hypotheses.

SAPP arranges the observed STR patterns into a possible family structure. Its useful contribution is a set of explicit groupings and approximate periods to investigate alongside the named SNP branches and family records.

Two groupings worth pursuing. Node 17 connects Alexander and James J through DYS714=27. Node 16 links the Kilwaughter candidates with the numbered Henry-root test through DYS607=16 and CDYa=36. Both give the next comparison a specific target.
Readable reconstruction of source output

SAPP node structure

Expand a node to inspect its path

Dates below retain the original displayed rounding. SAPP documentation describes the brackets as 67% ranges, using 28-year generations and dates rounded to 50 years—not the 95% ranges quoted for the SNP timeline. These definitions were checked; the source run itself was not rerun. S4

SAPP group auditReconstructed changes, contribution and limits by group
Model sensitivity made explicit

Why Alexander–William can be 5 or 7

The endpoints at DYS576 are 18 and 17: one step. SAPP instead selects ancestral 16 and separate paths to 18 and 17: three steps. That adds two to the pair’s raw 5, producing adjusted 7.

Raw GD 7 to 959947 is a different comparison: the Robert-1749 → William branch, not B696189’s reported William c.1655 line.

Calibration control

The Glasgow-12 date is too recent.

The displayed Node 14 estimate is c.1850 despite the supplied pedigree joining those lines at Robert, born 1749. Zero-generation nodes further down have no credible historical ordering among identical STR profiles.

Use c.1750 for Node 17 as a model search hint, not a tight birth window. Rerun with reliable SNP and pedigree constraints before leaning on the dates.

Testing targets

Where might marker-only lines fit?

No terminal SNP assignments inferred
Ranked marker-only comparison auditNearest anchor, next-best comparison and evidence boundary
GroupingApp cross-check and limitsPreserved subgroup claims, without treating them as SNP clades

The source reports broad Group 3 / Related Subgroup 1 for the principal Glasgow kits, Glasgow-12 as Tight Subgroup 2, and B835762 with 325862 as Tight Subgroup 1. SAPP expands the last pairing to Node 16 with 254947, based on DYS607=16 and CDYa=36.

The source reports B593262 in broad Group 3 while assigned FTA30932. The additional timeline now supplies the deeper join at FT4811: this is collateral paternal kinship, not necessarily an unrelated convergence. It still illustrates why a broad STR group is not the recent FT20271 clade. B593262 is not silently equated with an unnumbered match. Historical context →

GDist is the source-reported grouping-app genetic distance. RDist is described as a panel-normalised grouping score, not generations. Neither that export nor the complete SAPP input is attached here.

In the placement table, an absent motif means “does not carry this observed pattern”, not exclusion from FT20271: STR recurrence and reversions prevent that leap. A Y-37 distance is also not directly rankable against a Y-111 distance.

S0S1S5

People / roots and individual tests

Find the people.
Follow their tested lines.

Browse the earliest reported ancestors linked to this dataset, or switch to all 17 matches to Alexander’s reference test. Families with several tests retain each result separately.

Kit numbers are retained public-project identifiers from the source. Unnumbered results use local descriptive IDs, not invented FTDNA kit numbers. No living tester names, contact details or new private data are added. S0

Research / choose the questionChoose the part of the family history to resolve

Ask for evidence
that can change the answer.

Existing files can answer some questions before another test is bought. For new tests, choose the line that separates competing hypotheses.

Evidence by research line

What each unresolved line still needs

Previous fixed ordering — supersededRetained only to show how the current goal-based plan changed
Not the current priority ranking. Choose a research goal above for the active order. This older list is preserved as provenance only.
The minimum useful requestFiles and consent, not another screenshot alone

Ask the owner for matching-date Big Y Matches, Named Variants, Private Variants, VCF, quality BED and DYS/STR CSV, plus a current Block Tree view and a documented tester-to-root male-line pedigree. Record the reference assembly, download dates and consent to the specific comparison.

These may be sufficient for a first pass. Difficult, homologous or multiallelic sites may still need read-level BAM/CRAM review; a missing variant entry or BED overlap is not a replacement for a genotype.

No request is sent by this page. Copying only puts text on your clipboard.

Sources / evidence and reproducibility

The evidence
behind the reconstruction.

The supplied Y-DNA page provides the kit-level results; the supplied timeline provides the historical reconstruction. Measurements are retained, calculations are reproducible, and the route explanations are editorial synthesis of those sources.

Supplied data

Two supplied research pages

The Y-DNA explorer supplies measurements and reported audits. The timeline supplies the deeper branches, dates and historical hypotheses.

Newly calculated

Matrix consistency and ambiguity

21 pairs checked; eight minimum spanning trees; four non-additive quartet tests. Counts and UI data are generated from one model.

Retained references

Methods and historical settings

Provider guidance and historical references retained from the earlier build. This edition rewrites the explanation; it does not claim a new raw-DNA or documentary audit.

Reference raw file27 Oct 2022
Match / variant exports11 Aug 2026
Block Tree / SAPP12 Aug 2026
Reported YFull review31 Aug 2026
This revision6 Sep 2026

Source register

Changes that affect interpretation

Analysis audit

External project references retainedDiscovery links, not fresh verification of every record
Not available for this revision: the underlying VCF/BED and STR rows, original GroupingApp exports, SAPP input/output files, logged-in YFull report and full tester-to-root pedigree evidence. Live clade dates and topology were not independently refreshed; the added medieval relationships and dates come from the supplied timeline. The uploaded page’s descriptions are therefore treated as a dated source, not newly verified findings.
GENETIC BRANCHES · DOCUMENTED FAMILIES · HISTORICAL INTERPRETATION

Three ways of reading the same line.

The genetic tree gives the branch structure. Records identify the people. Historical interpretation connects those two scales into a testable story.

From a deeper shared ancestry
to recognisable Glasgow families.

The supplied model places the Glasgow-associated branches within the FT4811 family. FT32941 and FTA30932 are sibling branches: one is not an intermediate step towards the other. Later branches bring the story closer to the named paternal lines.

Select a branch below to see its reported date, documentary anchors and the historical interpretation together.

Loading the linked genetic and documentary model…
All linked paternal lines

Your research notebook.

Select 2 people to compare their evidence.