Evening, Ole. Thomas Krahn (of YSEQ and, prior to that, who FTDNA had moved to Houston to help design, build, and operationalize its Gene by Gene testing laboratory), does a great job--as an unpaid volunteer, I might add--of keeping YBrowse as up-to-date as possible. As a courtesy to the genetic genealogy community, he also makes available the source data files he uses in YBrowse's instance of GBrowse: ybrowse.org/gbrowse2/gff/. The most recent main upload of Y-SNPs was 28 May. Just FYI, the .CSV file contains--let me look--1,177,810 rows counting the header, so you'd want to open it in a database tool rather than Excel, which can only load 1,048,576 rows.
And, unfortunately, dbSNP doesn't offer compiled release data by chromosome, so the files there, even the VCFs, can get truly massive. But you can always get to the latest data at ftp.ncbi.nih.gov/snp/latest_release/.
And since I don't think Pip will ever again ask me about yDNA please tell him that I agree with your assessment of the associated SNPs he sees with his CTS13034. With so many SNPs that have, as yet, not been determined to define a new haplotree branch or node, that location is ripe to see new branching sometime soon.
I know it's an odd way to put it, but this truly is the golden age of yDNA testing for genealogy. The FTDNA haplotree contains over 170,000 SNPs; the YBrowse primary dataset consists of 1,177,809 SNPs; the BigY-700 full-sequence test targets about 23.6 million base pairs. New SNPs will continue to be named, and they along with SNPs already in the catalog will drive the Y-haplotree deeper and deeper...and closer to the current generation in all clades. My own "terminal" SNP is R-BY35083, with which only BY35082 is shown as associated, and I have one private variant. Pip has much more room for refinement very soon.
And BTW, I paid Yfull for an analysis last year, and they show me as BY19276, on a completely different sub-branch of BY3332 than does FTDNA. Many of the detailed, Big Y results I've seen are in disagreement between FTDNA and Yfull. Since I'm R-P312, I've also made my BAM available to Alex Williamson's Big Tree: www.ytree.net/DisplayTree.php?blockID=1058, which agrees with FTDNA that BY19276 is not on my branch.