Across the shared Y-111 panel.
Y-DNA workbench
See which paternal roots actually share mutations.
This explorer starts with the earliest paternal ancestor reported for each public project kit, connects that person to WikiTree only where a usable profile match exists, and separates confirmed SNP branches from shorter STR comparisons.
9reported paternal roots
17B580327 matches at Y-111
9Big Y matches
4named Big Y branches represented
Display
Paternal anchors
Earliest reported people
Each person appears once here even when descendant tests fall on different terminal branches. Candidate mappings remain clearly labelled.
Paternal anchors
Earliest reported people
Each person appears once here even when descendant tests fall on different terminal branches. Candidate mappings remain clearly labelled.
Pairwise comparison
How far apart are two roots?
Choose any two lines. STR distance and confirmed SNP relationships are reported separately.Alexander B580327 vs John M. 200475
Pairwise comparison
How far apart are two roots?
Choose any two lines. STR distance and confirmed SNP relationships are reported separately.Alexander B580327 vs John M. 200475
Both Big Y results currently terminate at R-FT20271.
Pairs involving B580327 can now be divided into reference-line and match-line changes from the supplied raw bundle.
Paternal branch map
Which kits sit on each confirmed SNP branch?
Read downward. Every kit is printed inside the SNP branch where it currently belongs; STR comparisons are kept outside the tree.
Paternal branch map
Which kits sit on each confirmed SNP branch?
Read downward. Every kit is printed inside the SNP branch where it currently belongs; STR comparisons are kept outside the tree.
Confirmed Big Y SNP branchTMRCA working estimateLinked names open WikiTree
R-FT4811→R-FT32941 / FTA35069→R-FT25406 block
Confirmed parent block · four equivalent SNPs
R-FT25406
FT25406, FT16394, FT18145 and FT26594 define this node. The tree below splits into a tested line that remains basal at FT25406 and the derived FT20271 branch.
parent block: R-FT32941 / FTA350691431 CEMost likely TMRCA
1199–160895% confidence range
8Modern samples shown
confirmed split below R-FT25406
Branch A · remains at R-FT25406
Stops here · does not carry FT20271
Henry Glasgo line
Henry Glasgo (Glasgo-21), 1774–1849, is the earliest reported ancestor for this basal Big Y result and a grandson of Jeremiah Glasgo (Glasgo-23).
Basal Big Y resultGlasgo-21 ↗
Unnumbered Big Y · GD 9 from B580327 at Y-111 · Big Y STR difference 4/656 · private-variant average 4.Second Henry-root testGlasgo-21 ↗
Kit 325862 · Y-111 only · GD 9 from B580327 · terminal FT25406 placement not yet confirmed by Big Y.
Branch B · carries R-FT20271
Confirmed child block · three equivalent SNPs
R-FT20271
FT20271, FGC5690 and FT16542 define this node. Five tested lines remain basal here; two more carry the confirmed child SNP FTE32242.
FT20271 · FGC5690 · FT165421583 CEMost likely TMRCA
1387–172895% confidence range
5 + 2Basal + child samples
tested paternal lines descending from R-FT20271
Three lines with no proved paper-tree connection
Each is an independent tip at FT20271. Their position beside one another does not imply that one descends from another.
STR pairing clue · shared DYS714=27 · GD 3 at Y-111Comparison grouping only—not a confirmed SNP or descent branch
Alexander c.1811Glasgow-951 ↗
B580327 · basal FT20271 · County Antrim → Scotland.James J c.1809/10 lineGlasgow-2738 ↗
1002232 · basal FT20271 · documented tester line reaches James; his attachment to Robert Glasgow-2769 remains uncertain.Reported William c.1655 lineGlasgow-591 ↗
B696189 · basal FT20271 · tested lineage confirmed; assignment to this historical root remains a reported pedigree.One family, tested through three sons
This subtree combines confirmed SNP results and audited paternal pedigrees. Kit 959947 now has a public 1950 census bridge; kit 200475 remains a clearly labelled probable private continuation.
Robert Glasgow, 1749–1839 · Glasgow-12 ↗
Inferred R-FT20271 carrier: all three Big Y descendant tests carry FT20271.
son · documented kit 959947 line
William Glasgow (Glasgow-563), 1778–1853
Likely chain: Glasgow-1829 → Glasgow-556 → Glasgow-1851 → Glasgow-1877.
KIT 959947 · BIG YRobert-1749 → son William · documented
Basal R-FT20271 · GD 7 · 5/660 from Alexander. A 1950 census household supplies the final public father–son bridge; the living name remains private here.
son · remains basal FT20271
John M. Glasgow (Glasgow-1965)
His descendant kit does not carry FTE32242.
KIT 200475 · BIG YJohn M. line
Basal R-FT20271 · GD 6 · 7/622 from Alexander.
R-FTE32242 arose on this paternal edge
James M. Glasgow (Glasgow-193), 1799–1875
Inferred R-FTE32242 carrier: positive descendants come through two different sons.
KIT 999763 · BIG YWilliam Allen Glasgow (Glasgow-2182) ↗
Confirmed R-FTE32242 · GD 6 · 4/666.KIT 478604 · BIG YSamuel Lyle Glasgow (Glasgow-192) ↗
Confirmed R-FTE32242 · GD 7 · 4/659.Because both son-lines are positive while John M.'s line is basal, FTE32242 is best placed between Robert and James—not beside Alexander's line.
Glasgow-12 family evidence · 4 tested descendantsSTR signature and branch-inheritance audit
Likely Glasgow-12 STR signature
DYS19=15 · DYS456=16 · DYS712=19 occurs in all four tested descendants of Robert Glasgow-12, spanning his William, John M. and James M. branches. None of the three other basal FT20271 lines carries the complete motif.
| Kit | Reported root | Confirmed SNP placement |
|---|---|---|
959947 | documented Robert Glasgow-12 line via William Glasgow-563 | Basal R-FT20271 |
200475 | Robert Glasgow 1749–1839 · Glasgow-12 | Basal R-FT20271 |
999763 | James M. Glasgow · Glasgow-193, through Glasgow-2182 | Child R-FTE32242 |
478604 | James M. Glasgow · Glasgow-193, through Glasgow-192 | Child R-FTE32242 |
This agreement with three independently traced son-lines makes the motif useful evidence for the Glasgow-12 family. It is still not a named SNP branch: DYS712 mutates rapidly, and STRs can recur or revert.
Branch-inheritance test at Robert Glasgow-12
This tests whether each genetic state follows the three documented sons. Kit 959947's final father–son step is visible in the 1950 census; “Probable” applies to kit 200475 because its final private continuation has not been independently exposed.
| Robert's son | Tested line | Paper audit | FT20271 | FT6135 | FTE32242 | Result |
|---|---|---|---|---|---|---|
| William Glasgow-563 | 959947 | Documented 1829 → 556 → 1851 → 1877 → 1950 household → private kit | Derived | Displayed derived | Ancestral/basal | Independent documented basal son-line. |
| John M. Glasgow-1965 | 200475 | Probable 1958 → 1954 → private | Derived | Displayed derived | Ancestral/basal | Independent basal line; public censuses support the early chain. |
| James M. Glasgow-193 | 999763 + 478604 | Two son-lines William Allen-2182 and Samuel Lyle-192 | Derived | Not displayed | Derived in both | Places FTE32242 on the Robert → James M. edge. |
What survives the test: FT20271 belongs at or above Robert, and FTE32242 belongs on James M.'s branch. FT6135 fails a clean three-son inheritance test. Until direct status/coverage is available for all four Big Y kits, it must remain unplaced.
| Direct result needed from both James M. kits | Consequence | Interpretation |
|---|---|---|
| Derived T calls | Place FT6135 at or above Robert Glasgow-12. | The current omission was a display/export limitation. |
| Ancestral C calls | Do not place FT6135 on Robert's branch. | The William and John M. results would require recurrence, reversion, or a tester/pedigree mapping review. |
| No-call / inadequate coverage | Keep FT6135 unresolved. | The missing display would not contradict inheritance, but would not establish it either. |
Marker-tested lines outside the confirmed SNP tree
These are not assigned to FT25406, FT20271 or FTE32242 without a terminal Big Y result.
All-vs-all reconstruction
Seven-kit FT20271 STR network
The minimum-length Y-111 network is shown first; the dense Glasgow-12 end is then expanded using the audited paper pedigrees and confirmed FTE32242 split.
All-vs-all reconstruction
Seven-kit FT20271 STR network
The minimum-length Y-111 network is shown first; the dense Glasgow-12 end is then expanded using the audited paper pedigrees and confirmed FTE32242 split.
Minimum-spanning STR edgeInferred paper-tree ancestorConfirmed child SNP
Reported William c.1655 line · Glasgow-591Kit B696189 · basal FT20271 · historical root not independently proved
DYS389ii=30 · DYS511=11 · DYS557=17GD 5closest standard-panel edge
Alexander 1811 · Glasgow-951Kit B580327 · basal FT20271
DYS576=18 · DYS714=27GD 3closest Y-111 pair
James J c.1809/10 line · Glasgow-2738Kit 1002232 · tested pedigree reaches James; proposed father Robert-2769 is unproved
DYS714=27 · DYS561=17GD 5 to reconstructed family haplotype
Reconstructed Robert Glasgow-12 haplotypeBranch-weighted inference from descendants through three sons; not a separately tested sample.
DYS19=15 · DYS456=16 · DYS712=19GD 1DYS650 19→20
Robert-1749 → son William branch · Glasgow-563Kit 959947 · documented paternal continuation
DYS650=20GD 0matches reconstructed Y-111 state
John M. branch · Glasgow-1965Kit 200475 · probable private continuation · basal FT20271
no Y-111 departure detectedR-FTE32242confirmed on the James M. edge
James M. branch · Glasgow-193The child SNP is confirmed through two different sons.
Kit 999763 · Glasgow-2182 lineGD 0 from the reconstructed standard-panel state.
Kit 478604 · Glasgow-192 lineGD 1:
CDY 35-37→36-37Best new result: the three-marker motif is much more informative as a Glasgow-12 family signature than as a generic “B cluster.” It survives across three sons and across the later FTE32242 split. Conversely, Alexander and the 1002232/James J line remain only a two-line STR pairing because they share no exposed child SNP.
| Kit / root | B696189 reported William c.1655 root | B580327 Alexander | 1002232 James J line | 200475 John M. | 959947 Robert-1749 → William | 999763 FTE | 478604 FTE |
|---|---|---|---|---|---|---|---|
| B696189 · reported William line | — | 5 | 6 | 7 | 8 | 7 | 8 |
| B580327 · Alexander | 5 | — | 3 | 6 | 7 | 6 | 7 |
| 1002232 · James J line | 6 | 3 | — | 5 | 6 | 5 | 6 |
| 200475 · John M. | 7 | 6 | 5 | — | 1 | 0 | 1 |
| 959947 · Robert-1749 → William | 8 | 7 | 6 | 1 | — | 1 | 2 |
| 999763 · FTE line A | 7 | 6 | 5 | 0 | 1 | — | 1 |
| 478604 · FTE line B | 8 | 7 | 6 | 1 | 2 | 1 | — |
Why “Alexander–William” can appear as 5 or 7: two distinctions are involved. B580327–B696189 (the reported William c.1655 root) is raw GDist 5 in both the GroupingApp export and SAPP's original-distance table, but SAPP raises that same pair to an adjusted GD 7 after inferring separate changes from ancestral DYS576=16 to 17 in B696189 and to 18 in B580327. Independently, B580327–959947 (the documented Robert-1749 → son William branch) has raw GD 7 in this matrix. SAPP's adjusted 7 is a topology-dependent convergence estimate; 959947's 7 concerns a different kit.
Scroll sideways to see every kit. Select two kit labels to compare them.
Select two kit labels to compare them.
Marker placement and calculation method
| Marker state | Branch-weighted reading | Best placement |
|---|---|---|
DYS19=15 · DYS456=16 · DYS712=19 | All four Glasgow-12 descendants; absent from B696189, B580327 and 1002232. | Likely on or above Robert Glasgow-12; strongest STR signature in the set. |
DYS714=27 | Only B580327 and 1002232; the other independent lines carry 26. | Supports the Alexander–James J tested-line pairing, but root direction is unresolved. |
DYS389ii=30 · DYS511=11 · DYS557=17 | Unique to B696189; all six other kits carry 31, 10 and 16. | Three likely departures on the reported William-line tip. |
DYS576 | 16 in 1002232 and the reconstructed Glasgow-12 family; 17 in B696189; 18 in Alexander. | Alexander's 18 is likely derived; deeper root state remains uncertain between 16 and 17. |
DYS561=17 | Unique to 1002232; all six other kits carry 16. | Likely 1002232-line departure after the Alexander pairing split. |
DYS650=20 | Unique to 959947; the other Glasgow-12 son-lines carry 19. | Terminal William-branch change below Glasgow-563. |
CDY=36-37 | Unique to 478604; its FTE32242 cousin and both basal Glasgow-12 lines carry 35-37. | Terminal change within the Glasgow-192 descendant line. |
Method: the matrix reports a transparent allele-step sum from the public Glasgow Project Y-STR table and two administrator-supplied Y-111 rows; multi-copy values are paired in sorted order. It should not be assumed to reproduce every company's GD algorithm, because FTDNA applies special rules to some multi-copy markers. The new B580327 relational export independently reproduces every available B580327 value shown here as its GDist. Its RDist is a separate panel-normalized grouping score, not genetic distance or generations. For ancestral-state inference, the four closely related Glasgow-12 kits were collapsed to one reconstructed family branch so they could not outvote the three independent basal lines. Confirmed SNPs and audited descendancy override an STR-only grouping.
1 · avg 4Basal FT25406 samples · private-variant average
5 · avg 3Basal FT20271 samples · private-variant average
2 · avg 1FTE32242 samples · private-variant average
Block Tree reconciliation and private-variant notes
Block Tree reconciliation: the displayed averages fit the pairwise lists after recurrent, multiallelic and off-tree calls are excluded. The five basal FT20271 tips appear to contribute roughly 5, 1, 5, 1 and 4 countable private variants (mean 3.2, displayed as 3); the two FTE32242 tips contribute roughly 1 and 2 (displayed average 1). This independently supports the variant-direction analysis.
Private-variant result: none of the listed Big Y matches shares B580327's five exported private variants. The raw VCF adds a sixth lineage-specific call at 26534797 C→G (PASS, depth 25), but the Block Tree does not count it in the private average. The non-matching screen labels that position FT124483, whose named mutation is C→A; it is a multi-allelic site, not evidence that all other kits share a new FT124483 branch.
How to read this: FT25406 → FT20271 → FTE32242 is confirmed SNP order. FT6135 strengthens one pairing but remains off-tree. Shared STR states appear only in the separate evidence table because they do not create branches; parallel changes and back-mutations remain possible. TMRCA values are working estimates reproduced from the project timeline and may change as FTDNA adds samples.
STR-only phylogeny
What does the SAPP reconstruction add?
SAPP independently recovers two useful marker signatures and proposes a third testable cluster. Its dates and internal ordering remain hypotheses because this run supplied neither SNP nor genealogy constraints.
STR-only phylogeny
What does the SAPP reconstruction add?
SAPP independently recovers two useful marker signatures and proposes a third testable cluster. Its dates and internal ordering remain hypotheses because this run supplied neither SNP nor genealogy constraints.
Evidence boundary. SAPP V4.27 constructed this tree from 11 STR haplotypes using genetic distance, shared off-modal signatures and inferred mutation paths. The input contained no
/SNPDATA or /GENDATA. Confirmed Big Y order—FT25406 → FT20271 → FTE32242—and audited paternal pedigrees therefore override any conflicting STR-only branch or date.c.1500Group MRCA · 17 generations · displayed range 1250–1700
c.1750Node 17 · B580327 + 1002232 · displayed range 1700–1750
c.1600Node 16 · 254947 + 325862 + B835762 · displayed range 1450–1750
SAPP's reconstructed node structure
This is a readable reconstruction of the supplied SAPP PNG. Blue cards are inferred STR nodes; yellow cards are tested haplotypes. Branches show SAPP's selected mutation path, not proved father–son relationships.
Group MRCA17 generations [9–24]
c.1500 [1250–1700]
c.1500 [1250–1700]
- DYS389i 13→14 · DYS442 12→13
DYF406S1 10→11N18544 · John-1767 lineY-67 · reported R-U106No matching group - DYS389ii-i 18→17 · DYS576 16→17
DYS451 10→11 · DYS557 16→17B696189 · William lineY-111 · confirmed R-FT20271Grade C+ - DYS607 15→16 · CDYa 35→36Node 1612 generations [6–18]
c.1600 [1450–1750]B+ · 93.6%- DYS460 11→12 · CDYb 37→38
DYS534 15→14 · DYS485 15→14
DYS635 23→24254947 · Robert c.1710Y-111 · reported R-U106Grade B - DYS464c 17→16 · DYS413a 23→22
DYS533 12→13 · DYS510 17→16325862 · Henry lineY-111 · reported R-U106Grade C+ - no additional change selectedB835762 · James William lineY-37 · reported R-U106Grade C+
- DYS460 11→12 · CDYb 37→38
- DYS714 26→27Node 178 generations [7–9]
c.1750 [1700–1750]B+ · 90.5%- DYS561 16→171002232 · James J lineY-111 · confirmed R-FT20271Grade B+
- DYS576 16→18B580327 · Alexander lineY-111 · confirmed R-FT20271Grade B+
- DYS561 16→17
- DYS19 14→15 · DYS456 17→16Node 14 · Glasgow-12 cluster3 generations [2–4]
c.1850 [1850–1900]Date conflicts with pedigree- DYS576 16→17333002 · Robert-1749 familyY-37 · reported R-U106Grade C+
- DYS712 20→19Node 130 generations [0–0]
c.1950Ordering non-evidential- no additional change999763 · Robert-1749 familyY-111 · confirmed R-FTE32242Grade B
- no additional changeNode 120 generations [0–0]
c.1950Identical STR state- no additional change794462 · Robert-1749 familyY-111 · reported R-Z18Grade B
- no additional change200475 · Robert-1749 familyY-111 · confirmed R-FT20271Grade B
- no additional change
- no additional change
- DYS576 16→17
Group MRCA17 generations [9–24]
c.1500 [1250–1700]
c.1500 [1250–1700]
DYS389i 13→14 · DYS442 12→13
DYF406S1 10→11
DYF406S1 10→11
N18544 · John-1767 lineY-67 · reported R-U106No matching group
DYS389ii-i 18→17 · DYS576 16→17
DYS451 10→11 · DYS557 16→17
DYS451 10→11 · DYS557 16→17
B696189 · William lineY-111 · confirmed R-FT20271Grade C+
DYS607 15→16 · CDYa 35→36
Node 1612 generations [6–18]
c.1600 [1450–1750]B+ · 93.6%
c.1600 [1450–1750]B+ · 93.6%
DYS460 11→12 · CDYb 37→38
DYS534 15→14 · DYS485 15→14
DYS635 23→24
DYS534 15→14 · DYS485 15→14
DYS635 23→24
254947 · Robert c.1710Y-111 · reported R-U106Grade B
DYS464c 17→16 · DYS413a 23→22
DYS533 12→13 · DYS510 17→16
DYS533 12→13 · DYS510 17→16
325862 · Henry lineY-111 · reported R-U106Grade C+
no additional change selected
B835762 · James William lineY-37 · reported R-U106Grade C+
DYS714 26→27
Node 178 generations [7–9]
c.1750 [1700–1750]B+ · 90.5%
c.1750 [1700–1750]B+ · 90.5%
DYS561 16→17
1002232 · James J lineY-111 · confirmed R-FT20271Grade B+
DYS576 16→18
B580327 · Alexander lineY-111 · confirmed R-FT20271Grade B+
DYS19 14→15 · DYS456 17→16
Node 14 · Glasgow-12 cluster3 generations [2–4]
c.1850 [1850–1900]Date conflicts with pedigree
c.1850 [1850–1900]Date conflicts with pedigree
DYS712 20→19
Node 130 generations [0–0]
c.1950Ordering non-evidential
c.1950Ordering non-evidential
DYS576 16→17
333002 · Robert-1749 familyY-37 · reported R-U106Grade C+
no additional change
999763 · Robert-1749 familyY-111 · confirmed R-FTE32242Grade B
no additional change
Node 120 generations [0–0]
c.1950Identical STR state
c.1950Identical STR state
no additional change
794462 · Robert-1749 familyY-111 · reported R-Z18Grade B
no additional change
200475 · Robert-1749 familyY-111 · confirmed R-FT20271Grade B
Blue: inferred SAPP nodeYellow: tested haplotypeDashed: ungrouped, weak or conflictingGreen underline: independently confirmed Big Y branch
Adjusted-GD path: SAPP gives B696189 DYS576 16→17 while B580327 independently takes 16→18. That inferred parallelism helps raise their raw GD 5 to adjusted GD 7.
| SAPP result | Reconstructed changes | What it contributes | Limit |
|---|---|---|---|
Node 17B580327 · 1002232 | DYS714 26→27 before their split; then DYS576 16→18 on Alexander's line and DYS561 16→17 on the 1002232 line. | Independently recovers the strongest Alexander–James J tested-line pairing and supplies an approximate c.1750 research horizon for their unknown common paternal ancestor. | The connection is Grade B+ with other options possible. No shared child SNP or paper ancestor has been found. |
Nodes 14–13333002 · 794462 · 200475 · 999763 | DYS19 14→15 and DYS456 17→16; the Y-111 descendants also carry DYS712 20→19. | Independently reconstructs the three-marker Glasgow-12 family signature already supported across the audited son-lines. | The displayed c.1850 Node 14 date is about a century later than documented Robert Glasgow's 1749 birth. Zero-generation nodes among identical Y-111 kits make their internal order non-evidential. |
Node 16254947 · 325862 · B835762 | DYS607 15→16 and CDYa 35→36 before their proposed split. | Creates a specific hypothesis that the Kilwaughter Robert and James William lines may join the Henry-root side of the project. | Its lower internal branches are partly low-confidence, CDY mutates rapidly and none of these numbered kits has a confirming terminal SNP. Big Y testing must decide it. |
| N18544 | DYS389i 13→14 · DYS442 12→13 · DYF406S1 10→11 | Records a distinct STR path for the reported John-1767 line. | SAPP places it directly from the group root with “No Grade: no matching found with other kits”; its small raw-distance lead toward 1002232 is not a recovered subclade. |
What causes SAPP's adjusted GD 7 for B580327–B696189? The observed endpoints differ by one repeat at DYS576, but SAPP selects ancestral 16 and models two separate paths: 16→17 for B696189 and 16→18 for B580327. That marker therefore contributes three inferred path mutations instead of one observed endpoint step, raising total GD from 5 to 7. The same inferred parallelism raises comparisons involving 333002. This is a useful convergence model, not a directly observed mutation history.
TMRCA calibration warning: the group estimate around 1500 broadly overlaps the present FT25406 and FT20271 age ranges, but the known Glasgow-12 control shows that an uncalibrated STR date can be materially too recent. The c.1750 and c.1600 nodes are search windows, not birth dates or relationship proof. A stronger rerun would add the confirmed SNP states and a genealogy group for the independently documented Glasgow-12 descendants.
Provisional placement
Where do the marker-only lines fit?
Each marker-only result was scored against four reconstructed anchors on the shared panel. This ranks research targets; it does not place any kit on an SNP branch.
Provisional placement
Where do the marker-only lines fit?
Each marker-only result was scored against four reconstructed anchors on the shared panel. This ranks research targets; it does not place any kit on an SNP branch.
GroupingApp and SAPP cross-check. All principal Glasgow kits fall in broad Group 3 / Related Subgroup 1. The GroupingApp recovers the known Robert-1749 cluster as Tight Subgroup 2 and pairs B835762 with 325862 in Tight Subgroup 1. SAPP separately proposes a broader Node 16 containing 254947, 325862 and B835762 through
DYS607=16 · CDYa=36, while failing to recover N18544 inside a specific subcluster. B593262 remains the warning: broad STR Group 3 despite a confirmed, different terminal branch, R-FTA30932. Grouping ranks leads; SNP placement decides branches.Recovered Glasgow-12 controls
794462 · GD 0/111Exact match to reconstructed Glasgow-12 state333002 · GD 1/37Only DYS576 differs from that stateControl check passed. Known paper-tree lines recover the expected family, although the partial panel cannot identify FTE32242.
Closest FT25406-side pairing
B835762 · James William · GD 1/37 from 325862GroupingApp Tight Subgroup 1; SAPP adds both to proposed three-line Node 16Node 16 also includes 254947 through DYS607=16 and CDYa=36. This sharpens the testing hypothesis but does not establish FT25406 membership.
Nearest distance, no recovered node
N18544 · John 1767 · GD 4/67Nearest anchor: 1002232; SAPP reports no matching groupThe panel does not reach DYS714, and SAPP leaves N18544 directly off the group root. Treat this as unplaced rather than an A1-side branch.
SAPP testing hypothesis
254947 · Robert c.1710 · proposed Node 16Shares DYS607=16 and CDYa=36 with 325862 and B835762Its wider Y-111 distances remain large and it carries neither diagnostic FT20271-side motif. Big Y is required.
| Rank | Kit and WikiTree root | Nearest reconstructed anchor | Next best | What the markers actually support |
|---|---|---|---|---|
| Very strong | 794462 · Glasgow-12 line · Y-111 | Glasgow-12 · GD 0/111 | 1002232 · GD 5/111 | Full recovery of the expected family placement, but R-Z18 is not a terminal Big Y result. |
| Strong control | 333002 · Glasgow-12 line · Y-37 | Glasgow-12 · GD 1/37 | three anchors · GD 3/37 | The partial panel independently recovers the known family; it cannot identify FTE32242. |
| Provisional | B835762 · Glasgow-1144 · Y-37 | 325862 · GD 1/37 | 1002232 / 254947 · GD 2/37 | GroupingApp puts B835762 and 325862 in Tight Subgroup 1; SAPP includes both with 254947 in Node 16 through DYS607=16 · CDYa=36. Big Y is required to test whether that signature represents FT25406 kinship or convergence. |
| Open | N18544 · Glasgow-822 · Y-67 | 1002232 · GD 4/67 | Alexander · GD 5/67 | Raw distance makes 1002232 its nearest anchor, but SAPP finds no matching subcluster and places N18544 directly from the group root. DYS712 and DYS714 are not on this panel. |
| Provisional | 254947 · Glasgow-1143 · Y-111 | 1002232 · GD 9/111 | Alexander / Glasgow-12 · GD 10/111 | The one-step nearest-anchor margin remains weak, but SAPP's Node 16 adds a distinct DYS607=16 · CDYa=36 hypothesis with 325862 and B835762. DYS714=26 and DYS19=14 · DYS456=17 · DYS712=20 still exclude both FT20271-side diagnostic patterns. |
Method boundary: a smaller distance on Y-37 is not automatically stronger than a larger distance on Y-111. This page's allele-step calculation pairs multi-copy values in sorted order; the grouping export's GDist and RDist use the app's own methods. STR recurrence and back-mutation mean “nearest” and subgroup labels are pairing leads, not genealogical relationships or confirmed SNP membership.
Raw-bundle analysis
Which side of each Big Y match changed?
The B580327 Named Variants, Private Variants, VCF and BED files let the pairwise non-matching lists be divided by direction. Counts are mutation-state differences, not generations.
Raw-bundle analysis
Which side of each Big Y match changed?
The B580327 Named Variants, Private Variants, VCF and BED files let the pairwise non-matching lists be divided by direction. Counts are mutation-state differences, not generations.
6B580327-line states shared by none of the displayed matches: 12648194 A→G, 14337402 T→C, 14339231 G→C, 15066888 A→T, 15973436 A→C and 26534797 C→G
6/6 PASSDepth 25–78 across the five private calls and the multiallelic site
15/15 coveredMatch-only raw positions lie inside the B580327 quality BED and have no derived call there
| Named SNP | Defining allele | B580327 direct VCF call | Evidence status | What it proves |
|---|---|---|---|---|
| FT20271position 9,182,554 | C→T | Derived TGT 1/1 · 57 alternate reads · DP 60 · PASS · covered by BED | VCF confirmed | Directly confirms B580327 on R-FT20271. |
| FT6135position 19,389,846 | C→T | Ancestral CGT 0/0 · 34 C, 1 T, 1 A reads · DP 40 · PASS · covered by BED | VCF confirmed | B580327 does not carry FT6135; the minor alternate reads did not change the high-confidence ancestral genotype. |
| FT124483position 26,534,797 | C→A | Not carriedseparate C→G call · GT 1/1 · 24 G reads · DP 25 · PASS · covered by BED | Multiallelic site | B580327 has a different mutation at the same coordinate; it is not FT124483 C→A. |
Vocabulary boundary: “VCF confirmed” above means a direct genotype plus quality coverage. “Displayed derived” elsewhere means the state appears in FTDNA's comparison output but the other kit's raw VCF/BED has not been inspected. “Not displayed” is not the same as ancestral; it may be ancestral, no-call, filtered, or omitted.
Evidence status and the next discriminating test
| Line / kit | Genetic evidence | Pedigree status | Best next evidence |
|---|---|---|---|
| Alexander Glasgow-951B580327 | FT20271 and key calls directly checked in VCF/BED. | Tested descendant line linked; Alexander's own terminal private states cannot yet be separated from later generations. | Big Y from a second independently documented son-line of Alexander. |
| James J Glasgow-2738 line1002232 | Big Y terminal FT20271; closest Y-111 pairing with B580327. | The documented tester line reaches James; Wilson-1982 is excluded and Robert-2769 remains an uncertain father. | A record naming James's father or a second documented male-line test from a candidate father's family. |
| Reported William c.1655 lineB696189 | Big Y terminal FT20271; 3/650 Big Y STR differences from B580327. | Tested paternal lineage is real; assignment to Glasgow-591 remains a reported historical pedigree. | Audit the tester-to-root chain and inspect B696189's VCF/BED. |
| Robert Glasgow-12 family959947 · 200475 · 999763 · 478604 | FT20271 inherited across three son-lines; FTE32242 confirmed under James M. | 959947 documented; 200475 probable; two James M. son-lines independently support FTE32242. | Direct FT6135 genotypes and coverage from all four kits. |
| Marker-only Glasgow candidates254947 · B835762 · N18544 · 794462 | Y-37 to Y-111 STR placement only; terminal SNP unknown. | Reported roots range from candidate to documented. | Big Y upgrade, prioritising 254947 or one close Farrier/Ferrier line. |
| Reported paternal root | Current branch | B580327 side | Match side | Best reading |
|---|---|---|---|---|
| James J Glasgow-2738 linekit 1002232 · paper trail currently stops at James | R-FT20271 | 7six lineage states + A19619 | 111816547 · one tree-counted tip variant | Closest STR match at GD 3, but no newly shared SNP below FT20271 is exposed. |
| Reported William c.1655 linekit B696189 | R-FT20271 | 6 | 5five covered, tree-counted tip variants | A fairly balanced pairwise SNP split; still insufficient by itself to order the line or prove the historical root. |
| Documented William Glasgow branchkit 959947 · Glasgow-12 descendant | R-FT20271 | 7six lineage states + BY26910 | 5four likely tip variants + off-tree FT6135 | FT6135 is shared with the John M. branch, but is absent from the available James M. branch lists; it cannot yet be assigned to Robert. |
| Robert Glasgow, 1749–1839kit 200475 · Glasgow-12 line | R-FT20271 | 6 | 2one tip variant + off-tree FT6135 | Basal descendant line of Glasgow-12; candidate FT6135 pairing with 959947. |
| James M. Glasgow, 1799–1875kit 999763 · through son Glasgow-2182 | R-FTE32242 | 6 | 2shared FTE32242 + one tip variant | One of two son-lines confirming the branch under Glasgow-193; Z21723 appears later on this tester's line. |
| James M. Glasgow, 1799–1875kit 478604 · through son Glasgow-192 | R-FTE32242 | 6 | 3shared FTE32242 + two tip variants | Second son-line independently confirms FTE32242 under Glasgow-193. |
| Henry Glasgo 1774basal Big Y result · Glasgo-21 | R-FT25406 | 9includes the three-SNP FT20271 block | 5four tree-counted tip variants + one excluded call | A useful upstream control, not a competitor for placement inside FT20271. |
Pedigree audit changes the interpretation: 959947 is a documented descendant of Robert Glasgow-12 through William Glasgow-563, while 200475 probably descends through John M. Glasgow-1965. Their shared FT6135 state could be ancestral to Robert, but the available FTE32242 descendants through James M. Glasgow-193 do not display it. FT6135 is therefore an unresolved family-level clue, not a named branch marker.
Important counter-example: 200475 and 999763 are identical across the displayed Y-111 panel (GD 0), yet the Block Tree places 999763 on confirmed child R-FTE32242 while 200475 remains basal R-FT20271. Even a perfect 111-marker match can therefore conceal a real SNP split.
Two different “closest” results: 1002232 is Alexander's closest FT20271 match on the standard Y-111 panel at GD 3, while B696189 has the fewest mismatches on the larger Big Y STR comparison at 3 of 650. Neither receives a shared downstream SNP with Alexander on the Block Tree, so the data do not justify choosing either as the nearer paper-tree cousin.
Two questions must stay separate for 1002232: the documented tester line reaches James J Glasgow-2738. Wilson Crossier Glasgow and Mary McCracken are excluded as his parents by their seven-child estate group; Robert Glasgow-2769 remains only an uncertain working father. B580327 and 1002232 share DYS714=27, GD 3 at Y-111 and 4 differences across 662 comparable Big Y STRs, but no exposed SNP below FT20271. The genetic pairing does not choose James's father.
DYS export: B580327's file contains values for all 829 exported STR/FTY fields. It is a complete reference profile, but it cannot create another pairwise distance by itself. The existing Big Y comparison already uses the 622–666 markers callable in common with each Big Y match; a second tester's DYS export would be needed to inspect exactly which extended markers differ.
The B580327 raw file is dated 27 October 2022, while the match and named/private exports were downloaded 11 August 2026. All 15 numeric match-side positions were checked against the older raw file and remain covered ancestral calls; named sites are interpreted from the current export and pairwise screen. No living tester identity or raw sequence is published here.
Complete match screen
Every Y-111 match to Alexander's kit
All 17 matches are ranked by their reported genetic distance from B580327. Historical paternal-root labels are retained; living tester names are deliberately omitted.
Complete match screen
Every Y-111 match to Alexander's kit
All 17 matches are ranked by their reported genetic distance from B580327. Historical paternal-root labels are retained; living tester names are deliberately omitted.
| Y-111 GD | Reported earliest paternal ancestor | Test / terminal label | Big Y STR difference | Current interpretation |
|---|---|---|---|---|
| 3 | James J Glasgow-2738 lineDocumented tester line; James's father unproved | Big Y · R-FT20271 | 4 of 662 | Closest confirmed FT20271 match; likely STR pairing with Alexander, not a proved paper-tree branch. |
| 4 | Wm Farrier and Susanna Abell linePhiladelphia marriage reported in 1796 · match A | Y-111 · R-M269 | Not available | Very close STR lead, but no terminal SNP placement. |
| 4 | Wm Farrier and Susanna Abell linePhiladelphia marriage reported in 1796 · match B | Y-111 · R-M269 | Not available | Independent tester from the same reported Farrier pedigree; Big Y is needed. |
| 5 | Reported William c.1655 lineScotland · historical root not independently proved | Big Y · R-FT20271 | 3 of 650 | Adjacent FT20271 singleton in the current STR topology. |
| 5 | Henry Ferrier, born c.1758Woodnesborough, Kent | Y-111 · R-M269 | Not available | Third close Farrier/Ferrier lead; terminal SNP is unknown. |
| 5 | Glasgow lineNo earliest paternal ancestor reported | Y-111 · R-M269 | Not available | Useful surname match, but presently has no genealogical anchor. |
| 6 | James M. Glasgow, 1799–1875through son Glasgow-2182 · confirmed FTE32242 test A | Big Y · R-FTE32242 | 4 of 666 | First of two son-lines placing the SNP under Glasgow-193. |
| 6 | Robert Glasgow, 1749–1839Glasgow-12 · basal descendant test 200475 | Big Y · R-FT20271 | 7 of 622 | Same reported root as the FTE32242 tests, but this descendant line remains basal FT20271. |
| 6 | Robert Glasgow, 1749–1839Northern Ireland · marker-only test | Y-111 · R-Z18 | Not available | Same reported pedigree as FTE32242 testers; terminal placement remains unconfirmed. |
| 7 | James M. Glasgow, 1799–1875through son Glasgow-192 · confirmed FTE32242 test B | Big Y · R-FTE32242 | 4 of 659 | Second son-line independently confirms the child SNP under Glasgow-193. |
| 7 | Documented William Glasgow branchRobert Glasgow-12 descendant · final link verified in the 1950 census | Big Y · R-FT20271 | 5 of 660 | Shares FT6135 with Robert's John M. branch, but the call conflicts with its absence in the James M. lines. |
| 8 | Alexander Churnside, 1838–1873Jamaica | Big Y · R-FTA30932 | 11 of 632 | A different named Big Y branch: deeper paternal kin, not part of FT20271. |
| 9 | Henry Glasgo, 1774–1849Glasgo-21 · Jeremiah's grandson | Big Y · R-FT25406 | 4 of 656 | Confirmed upstream branch; not a terminal FT20271 result. |
| 9 | Henry Glasgo, 1774–1849Glasgo-21 · second reported descendant test | Y-111 · R-M269 | Not available | Second test associated with the Henry Glasgo pedigree; needs Big Y. |
| 9 | Phillips lineNo earliest paternal ancestor reported | Y-111 · R-M269 | Not available | Unplaced non-surname STR match. |
| 10 | Dixon Brown, 1758–1828Virginia to Kentucky | Big Y · R-FTA30932 | 11 of 665 | Same non-FT20271 branch as the Churnside test. |
| 10 | Robert Glasgow, c.1710–after 1772Northern Ireland · spouse Rachel Wilson | Y-111 · R-M269 | Not available | Highest-value documented East Antrim line for a Big Y upgrade. |
GD 3Closest confirmed FT20271 match
GD 4–5Three unplaced Farrier/Ferrier matches
8 of 17Have no terminal Big Y placement
Key interpretation: the three Farrier/Ferrier lines are too close at Y-111 to ignore, but their broad R-M269 labels do not establish that they carry FT20271. They could represent a surname change, a much older shared paternal ancestor, or ordinary STR convergence. A Big Y upgrade from one of those lines would discriminate between those possibilities.
Action plan
Next Steps
Concrete requests ranked by their likely value to the Glasgow surname problem. “Full bundle” means the kit owner's own downloadable files, not another public-result screenshot.
| Order | Concrete request | What it could achieve | Decision boundary |
|---|---|---|---|
Upgrade kit 254947 from Y-111 to Big Y-700.Reported root: Robert Glasgow, c.1710–after 1772, Kilwaughter/Larne. | This is the best identified old Northern Irish Glasgow line awaiting SNP placement. FT20271-positive would connect it to Alexander's child branch; FT25406-positive but FT20271-negative would place it on the collateral parent branch; a result outside FT25406 would overturn the older STR grouping. | Highest-value single upgrade. The genetic result places the tested paternal line; the tester-to-Robert pedigree still needs documentary support. | |
Request the full Big Y bundle for kit 1002232.The documented line reaches James J Glasgow-2738; his father remains unknown. | Directly compare its private and named calls with B580327, verify coverage at the match-only position 11816547, and identify the exact extended STR differences behind Alexander's closest standard Y-111 match. | It may expose a candidate shared sub-branch below FT20271. It cannot by itself identify James's father or prove a paper-tree relationship. | |
Request the full Big Y bundle for kit B696189, plus its tester-to-root pedigree.Reported line to William Glasgow, born c.1655. | Check the five match-side variant positions directly, reproduce the 3-of-650 extended STR comparison, and test whether B696189 and B580327 share any unpromoted derived state below FT20271. | The files can refine branch proximity; only the requested pedigree evidence can validate the historical William label. | |
Request full bundles for kits 999763, 478604, 959947 and 200475.Start with 999763 and 478604 if access is limited; they are the two independent James M. son-lines. | Resolve the off-tree FT6135 pattern by checking genotype and coverage in every branch. Derived calls in both James M. kits would place FT6135 at or above Robert Glasgow-12; ancestral calls in both would exclude it from Robert's ancestral state and force a narrower explanation. | A no-call at FT6135 remains unresolved. Direct VCF/BED evidence is needed; absence from a displayed private-variant list is not a negative genotype. | |
Upgrade kit B835762 from Y-37 to Big Y-700.Reported root: James William Glasgow, 1731–1775, Kilwaughter/Larne. | Test whether its one-step Y-37 pairing and Tight Subgroup 1 assignment with Henry-root kit 325862 represent the same FT25406 branch, a new child branch, or STR convergence. | Neither B835762 nor 325862 has a terminal SNP result; the separate unnumbered Henry-root Big Y cannot safely be imputed to either marker kit. Ideally test both Kilwaughter kits rather than infer one result from the other. | |
| Recruit a second Big Y-700 tester descended from Alexander Glasgow-951 through a different son from B580327's line. | Phase B580327's six private lineage states: variants shared by both descendants arose at or above Alexander; variants found in only one line arose later. That could create a named Alexander branch. | The tester must have a documented unbroken male line and branch from Alexander through a different son; a close relative on the same recent line adds little. | |
| Upgrade one of the three close Farrier/Ferrier Y-111 matches to Big Y-700.Prefer one of the two independent William Farrier–Susanna Abell lines; kit numbers were not supplied in the current export. | Distinguish a surname change or shared paternal ancestor from STR convergence: FT20271-positive would join the cluster, FT25406-only would indicate deeper kinship, and a different branch would reject the apparent close connection. | Do not treat GD 4–5 at Y-111 as proof of Glasgow ancestry before this SNP test. | |
After the priority work, consider Big Y-700 for kit N18544 and the unnumbered Glasgow Y-111 match.N18544 reports John Glasgow, 1767–1851, Ireland to Ohio. | Place two remaining surname lines that are currently supported only by STR similarity and may identify another collateral Northern Irish branch. | Useful breadth, but less likely than 254947 or B835762 to answer the immediate Kilwaughter/Killoquin relationship question. |
Minimum useful “full bundle” request:
Big Y Matches, Named Variants, Private Variants, VCF, BED and the DYS/STR CSV, all downloaded at about the same time, plus a current Block Tree screenshot showing the kit's placement. A BAM file is not needed for the first-pass questions above.Reading distance
Measurements that must not be mixed
Definitions, interpretation boundaries and full source notes.
Reading distance
Measurements that must not be mixed
Definitions, interpretation boundaries and full source notes.
Allele-step distance
This page's transparent sum of allele differences on the smaller shared panel. It reproduces the new B580327 export's available GDist values, but is labelled separately because provider rules for multi-copy markers can differ.
GroupingApp GDist / RDist
GDist is the app's pairwise genetic distance. RDist is its panel-normalized grouping score. Neither is a generation count, TMRCA, SNP branch or proof of relationship.
SAPP original / adjusted GD
Original GD is calculated from the observed STR endpoints. Adjusted GD is recalculated along SAPP's chosen tree to model convergence and back-mutation. It can change when SNPs, genealogies or the input kit set change.
Named SNP branches
A downstream SNP such as FTE32242 gives a reliable branch order. A block may contain several equivalent named SNPs, so one displayed branch step is not necessarily one mutation.
Private Big Y variants
These usually provide the most useful recent separation. They require kit-owner or administrator downloads and coverage checks; public tables do not provide the exact pairwise count.
Data: project-admin research notes, the private B580327 matches/variants/DYS bundle supplied 11 August 2026, an FTDNA Block Tree screenshot supplied 12 August 2026, the Y-DNA Family Grouping App exports Subgroups.csv and Kit_B580327_Rel_Dist_Table.csv, and the SAPP V4.27 HTML/tree output generated 12 August 2026 from 11 STR kits without SNP or genealogy constraints; checked against the FamilyTreeDNA Glasgow Project public Y-STR table, public SNP overview, and the 1950 Humboldt census household documenting kit 959947's final paternal link. FT6135 and FT124483 coordinates/alleles were cross-checked in the ISOGG FT 0K table and FT 120K table. TMRCA ranges are the current working estimates recorded in the project timeline; the linked FTDNA Discover pages are the place to check for later revisions. Ancestor labels are reported pedigrees unless the branch audit says otherwise. Living match names and the screenshots are not republished. Method guidance: FTDNA genetic-distance rules, SAPP's tree method and output definitions, Block Tree and aggregated averages, non-matching variants, Big Y downloads and a father–son mutation study identifying DYS712 as rapidly mutating. Continue into the R-FT20271 timeline section.