Coming Soon: Y-DNA Haplogroups for Family Finder

[ArmandoR1b]

Here are the numbers for today's FTDNA haplotree totals for some select countries and R1b branches in Europe, in case anybody wants to run some percentages.

NOTE that Z46512 is mostly made up of U152, DF27 and FGC84729

Did you mean Z46516?

Z46516 is not tested by v2 since there is no positive result for it. It shows presumed positive in v2 kits with a Z195 subclade.

Have you kept track of Big Y participants in the Big Y Block Tree for the same branches you have in that table?

[Mitchell-Atkins]

Here are the numbers for today's FTDNA haplotree totals for some select countries and R1b branches in Europe, in case anybody wants to run some percentages.

NOTE that Z46512 is mostly made up of U152, DF27 and FGC84729

Did you mean Z46516?

Z46516 is not tested by v2 since there is no positive result for it. It shows presumed positive in v2 kits with a Z195 subclade.

Have you kept track of Big Y participants in the Big Y Block Tree for the same branches you have in that table?

Yeah, typo, should be Z46516.  Thanks.  No on tracking BigY tree question

[Mitchell-Atkins]

Here are the numbers for today's FTDNA haplotree totals for some select countries and R1b branches in Europe, in case anybody wants to run some percentages.

NOTE that Z46512 is mostly made up of U152, DF27 and FGC84729

Did you mean Z46516?

Z46516 is not tested by v2 since there is no positive result for it. It shows presumed positive in v2 kits with a Z195 subclade.

Have you kept track of Big Y participants in the Big Y Block Tree for the same branches you have in that table?

Yeah, typo, should be Z46516.  Thanks.  No on tracking BigY tree question

I get " Error retrieving matches" when I try to open the block tree.
 Maybe they are in the middle of an update.

[Riverman]

Did you mean Z46516?

Z46516 is not tested by v2 since there is no positive result for it. It shows presumed positive in v2 kits with a Z195 subclade.

Have you kept track of Big Y participants in the Big Y Block Tree for the same branches you have in that table?

Yeah, typo, should be Z46516.  Thanks.  No on tracking BigY tree question

I get " Error retrieving matches" when I try to open the block tree.
 Maybe they are in the middle of an update.

Works for me. It happens from time to time for some users and should work in some hours.

[Riverman]

Update on Garibaldi, he likely is not just E-V13, but more specifically E-FGC11450:
https://discover.familytreedna.com/y-dna...1450/story

North Italians are undertested, but the best proxy might be the large Sardinian sample from Cagliari, with lots of E-Z5018/Z5017 members.
Under FGC11450 is a specific, pretty old Sardinian branch dating to the La Tene/Iron Age period, E-Z21287. Since most of the Sardinian Z5018/Z5017 branches are likely from Genua/Liguria, I wouldn't wonder if Garibaldi would belong to that branch too. However, the Garibaldi tester was just assigned by the new Family Finder haplogroup assignment and wans't BigY tested, which makes it speculative.
Nice to have that result from Family Finder though, since the Italian tester probably wouldn't have upgraded and Garibaldi was still under E-M35 in the notable matches.

[rmstevens2]

R-BY166 seems to be the default Y-DNA result from Family Finder for my own Y-chromosome line, both for those with my surname and more broadly for most of the guys in the R1b-BY168 and Subclades Project. Old R-M269 predictions are steadily being replaced on the project's DNA Results page with R-BY166. I would rather everyone upgraded to the Big Y-700, but this is much better than no improvement at all.

In my maternal grandfather's Y-chromosome line (Z253>FGC3268>BY43439>BY4303>FGC59516>BY93500>BY132893>FT418639), the old R-M269 predictions are slowly being replaced by R-Z253. That's not quite as good as the R-BY166 in my own Y-DNA line, but, once again, it's much better than no improvement at all.

[rmstevens2]

R-BY166 seems to be the default Y-DNA result from Family Finder for my own Y-chromosome line, both for those with my surname and more broadly for most of the guys in the R1b-BY168 and Subclades Project. Old R-M269 predictions are steadily being replaced on the project's DNA Results page with R-BY166. I would rather everyone upgraded to the Big Y-700, but this is much better than no improvement at all.

In my maternal grandfather's Y-chromosome line (Z253>FGC3268>BY43439>BY4303>FGC59516>BY93500>BY132893>FT418639), the old R-M269 predictions are slowly being replaced by R-Z253. That's not quite as good as the R-BY166 in my own Y-DNA line, but, once again, it's much better than no improvement at all.

I have probably already mentioned this, but R-BY166 is also the default result for my Y-chromosome line at 23andMe; only there it's given as R-Z18021. That's what I  and a few of my Y relatives have there and also a guy with the Welsh surname Lloyd who contacted me about it some years ago (but then never did any more about it). 

I was hoping he would test with FTDNA and join the R1b-BY168 and Subclades Project. He sounded interested, but of course money was involved, so I guess I can't blame him. Another stingy Welshman.

[Riverman]

Honestly you have no reason to complain, because R-BY166 has a TMRCA of 710 AD!

If I would have such a recent result from my matches, I might already have answered my main open question from the hundreds of new testers. Unfortunately, my most recent tested SNP is much older.

[rmstevens2]

Honestly you have no reason to complain, because R-BY166 has a TMRCA of 710 AD!

If I would have such a recent result from my matches, I might already have answered my main open question from the hundreds of new testers. Unfortunately, my most recent tested SNP is much older.

You're right. I've been hoping for some ancient (medieval really) BY166 results, but that hasn't happened yet.

[Mitchell-Atkins]

On the bright side 710 AD is better than 2500 BC :-)

[rmstevens2]

On the bright side 710 AD is better than 2500 BC :-)

Very true!

[Mabrams]

Numbers are odd.

Earlier today, total of 382,000. Now its 419,150 which is 37,150 in one jump.

But....the number of branches for A-PR2129 has remained constant at 79,532.

My personal match list has not changed due to the 37,150. Not yet, anyway. I did get significant increases in desired SNPs over the last few days but sometimes many hours after the totals were updated.

I am not sure if V2s are starting to ramp up. Some downstream clades, eg L21 or DF27 are still increasing at a large rate. L21 has bumped up over 5,000 in 3 days.

[Barbarroja]

R-BY166 seems to be the default Y-DNA result from Family Finder for my own Y-chromosome line, both for those with my surname and more broadly for most of the guys in the R1b-BY168 and Subclades Project. Old R-M269 predictions are steadily being replaced on the project's DNA Results page with R-BY166. I would rather everyone upgraded to the Big Y-700, but this is much better than no improvement at all.

In my maternal grandfather's Y-chromosome line (Z253>FGC3268>BY43439>BY4303>FGC59516>BY93500>BY132893>FT418639), the old R-M269 predictions are slowly being replaced by R-Z253. That's not quite as good as the R-BY166 in my own Y-DNA line, but, once again, it's much better than no improvement at all.

I have probably already mentioned this, but R-BY166 is also the default result for my Y-chromosome line at 23andMe; only there it's given as R-Z18021. That's what I  and a few of my Y relatives have there and also a guy with the Welsh surname Lloyd who contacted me about it some years ago (but then never did any more about it). 

I was hoping he would test with FTDNA and join the R1b-BY168 and Subclades Project. He sounded interested, but of course money was involved, so I guess I can't blame him. Another stingy Welshman.

Guys, don´t cry. 
My closer YFull match is a 2,100 years old fossil. 
In FTDNA I have not BigY matches, I have exactly 35 people with whom I share some (old, old) relation in the last 3,500 years
And my STR matches are:
111: ZERO
67: ZERO
37: ZERO
25: zero
Well at least in 12 I have... z e r o matches.

[Mitchell-Atkins]

M269 is 145,426, 6815 (4.7%) not in a subclade

Today M269 = 162635, not in a subclade = 6773, a drop of 42.

[ArmandoR1b]

Numbers are odd.

Earlier today, total of 382,000.  Now its 419,150 which is 37,150 in one jump. 

But....the number of branches for A-PR2129 has remained constant at 79,532.   

My personal match list has not changed due to the 37,150.  Not yet, anyway.  I did get significant increases in desired SNPs over the last few days but sometimes many hours after the totals were updated.

I am not sure if V2s are starting to ramp up.  Some downstream clades, eg L21 or DF27 are still increasing at a large rate.  L21 has bumped up over 5,000 in 3 days.

Not sure if I am missing something. I don't see how FF results would change the number of branches. Big Y-700 is able to create new branches but FF is based off of existing branches.

There is no question that v2 kits are being processed. I have seen some that are from 2018 get a subclade.

I believe the v3 kits are still being added to the haplotree counts even if they finished processing those kits. Overnight my subclade grew by 30 kits, both in All Participants and in Branch Participants but Big Y Block did not increase at all. Meaning it is the most downstream SNP tested by FF. I believe they are all from v3 kits but I still don't have proof.