J-L817 Clade - News

17 August 2013

Y-SNP markers ZS252 and ZS261 are now available for testing at Family Tree DNA. These markers, along with others in ZS250-ZS263 range, were discovered on chromosome Y of a Finnish J-L816 person published by 1000 Genomes project. Subsequently, ZS261 was also found on chromosome Y of another J-L816 person published by Personal Genomes Project. To evaluate the phylogenetic importance of these SNPs, they need to be tested by members of each subgroup in our FTDNA project.


19 July 2013


The International Society of Genetic Genealogy (ISOGG) has added SNP markers L817, L818, L816 to their Haplogroup J tree. The broader J-P58 clade (earlier known as J1c3, J1e), has become J1a2b as per the current version of ISOGG tree. L817 was added as J1a2b3, L818 as J1a2b3a, and L816 as J1a2b3a1.


11 May 2013


A descendant of a Syrian Jew (member of Y-DNA Haplogroup J project) has tested positively for SNP marker L817 but negatively for L818. Thus, based on what is known today, the broader J-L817 clade breaks down into
(I) L818- cluster (beside the confirmed Syrian Jewish case, may include two other cases, including one originating from China);
(II) L818+ subclade, which in its turn breaks down into:
(a) L816- Kurdish lineage (one confirmed case)
(b) L816- German lineage (one confirmed and two presumed cases)
(c) L816+ subclade, predominantly Ashkenazi Jewish and by far the largest one (~97% of all confirmed or presumed L817 cases, 9 confirmed and ~420 presumed).



18 April 2013

A Kurdish person has tested positively for SNPs L817 and L818 but negatively for SNP L816 in Family Tree DNA testing. This result is the same as the one obtained in 2012 in a person whose paternal lineage originates from Germany and is the first confirmed J-L817 case in a member of a Middle-Eastern nation other than Jews.



10 January 2013


Following the approval by Haplogroup J project administrators and Family Tree DNA, Bnei Yahya project was renamed into J-L817 clade project and moved to Y-DNA haplogroup projects category. The renaming will not cause any changes for current project members, except that they will see "J-L817 clade" instead of "Bnei Yahya" on projects lists in their MyFTDNA profiles. 


16 December 2012

Everything we currently know about J-L817 clade and some speculations based on this knowledge can now be found in our research summary document. Another addition to our website is FAQ section.


23 May 2012

A J1c3* kit tested positively for SNP markers L817 and L818 and negatively for L816. The kit in question has the following Y-STR results: DYS392=14, DYS439=12. The kit owner's earliest known paternal ancestor was from Germany; he reports no known Jewish or other Middle-Eastern ancestry. The kit in question is 19 steps away from the base haplotype based on more than sixty 67-marker tests that are confirmed or predicted to be L816+ (among the latter, the most remote ones are only 9 steps away from the base haplotype). Don, thanks for ordering the tests! 


10 March 2012

The hypothesis that SNPs L816, L817 and L818 can provide the basis to strictly define our cluster as a subclade of Y-DNA haplogroup J1c3 has received new confirmation: two members of our FTDNA project tested positively for all of these SNPs.

The respective kits have different values at 7 of 37 Y-STR markers tested; besides, one of them has differences at 8 of 37 markers vs. kit where SNPs L816-L818 were initially discovered, and another one differs from that kit at 9 of 37 markers. Collecting confirmed cases of SNPs L816-L818 that are relatively remote from each other is important in the context of 
listing criteria for SNP inclusion into the ISOGG Y-DNA Haplogroup Tree, which require that the individuals tested for new SNPs must have STR haplotypes whose allele values differ in 15% or more of the markers genotyped.

Our thanks go to Steven and David who tested their kits for these SNPs.

Members of our project who are interested to discuss whether testing their kits for SNPs L816-L818 would make sense in the context of further study of our cluster are welcome to contact the project administrator.