World Families Forums - R1b1a2 M269 now what?

Home Help Search Login Register

WorldFamilies has changed our Forum Operating system and migrated the postings from the prior system. We hope that you’ll find this new system easier to use and we expect it to manage spammers much better. If you can’t find an old posting, please check our Legacy Forum to see if you can see the old posting there.
+  World Families Forums
|-+  General Forums - Note: You must Be Logged In to post. Anyone can browse.
| |-+  R1b General (Moderator: Maliclavelli)
| | |-+  R1b1a2 M269 now what?
« previous next »
Pages: [1] Go Down Print
Author Topic: R1b1a2 M269 now what?  (Read 2236 times)
New Member
Offline Offline

Posts: 2

« on: March 03, 2013, 11:02:30 PM »

My father's family is the above.  I've done the 25 markers, trying to decide between going to 37/67 or the SNP.  Any one with ideas on which  might be better.  The surname was Newman, only have it back to 1770's in Gloucestershire, England.  Nothing further, was hoping to make a connection to help further this line.

Appreciate any words of wisdom here.  Thanks much
Offline Offline

Posts: 15

« Reply #1 on: March 04, 2013, 08:14:26 AM »

I would do SNP first to see where does your father belong of M269 to get a better idea.


Senior Member
Offline Offline

Posts: 99

« Reply #2 on: March 04, 2013, 12:02:13 PM »

If you want to find close mathces then upgrading to a higher number of STR's would be of most use.

Board Moderator
Offline Offline

Posts: 5023

« Reply #3 on: March 04, 2013, 09:00:58 PM »

I agree. I would go out to 67 or 111 markers first and check your matches. Some of them may have SNP results. What your closest matches are is probably what you are, too. That can help guide your SNP testing, when you get around to it, and save you some money.
« Last Edit: March 04, 2013, 09:01:11 PM by rms2 » Logged

Pages: [1] Go Up Print 
« previous next »
Jump to:  

SEO light theme by © Mustang forums. Powered by SMF 1.1.13 | SMF © 2006-2011, Simple Machines LLC

Page created in 0.096 seconds with 18 queries.