From $19, paid once and yours to keep. See what your file reads first. Check your file →
DeutschFrançaisEspañolPortuguês Sample report Support Log in
aimosti Check your file

Learn Under the hood

The Prothrombin row in every 23andMe file, and why we weren't reading it

Every 23andMe export we have tested carries a call for Prothrombin G20210A, one of the two common inherited clotting variants. Until 28 September our reader never found it. This is how a correct row went unread for three and a half months, and what the report says about the variant now.

Key takeaways

  • 23andMe raw-data files write Prothrombin G20210A as i3002432 at GRCh37 position 11:46,761,055, never as rs1799963. The FDA's 2017 decision summary on 23andMe's thrombophilia report lists the variant under both names[2].
  • Our reader looked for the rsID and then for the GRCh38 coordinate. Neither could find this row, so until 28 September 2026 no 23andMe file had its Prothrombin call read.
  • The fix translates a coordinate only where the 20 bases on each side of the site are identical in both assemblies. A fourth candidate, in a repeat, failed and stays unread.
  • The variant raised the odds of venous thrombosis 2.8-fold in the study that found it, and 3.8-fold in a pooled analysis of eight studies[5, 7]. Many carriers never have a clot[8].
  • In gnomAD, about 2.6 percent of non-Finnish Europeans and about 1 percent of Finns carry at least one copy (our estimate from gnomAD's counts)[10].

Prothrombin G20210A is a single-letter change, G to A, at the far end of the F2 gene, which makes clotting factor II. Its catalogue name is rs1799963, and it sits on chromosome 11 at position 46,739,505 in the current reference genome, GRCh38, and at 46,761,055 in the previous one, GRCh37[1]. 23andMe genotypes it on its chip, and in 2017 the FDA authorised the company's hereditary thrombophilia report, which covers it. The FDA's decision summary names the variant by two identifiers, rs1799963/i3002432[2]. The second one is the name every 23andMe raw-data file uses, and for months our reader looked only for the first.

One row, two names

A 23andMe raw-data download is a text file of several hundred thousand lines. After a header of comments, each line holds four things: an identifier, a chromosome, a position and the two letters the chip read there. The header calls the first column rsid, and most entries are rsIDs, the public catalogue numbers that dbSNP assigns to known variants. Some are not. 23andMe also tests positions under its own identifiers, which begin with an i, and Prothrombin G20210A is one of them.

23andMe

# rsid       chromosome  position  genotype
i3002432     11          46761055  GG
The Prothrombin row as it appears in each of the four 23andMe exports we test with (file versions 3, 4 and 5). The genotype shown, two copies of the usual G, is an example; a carrier's row reads GA or AG. Positions are GRCh37 coordinates[3].

In all four files the row has the same identifier and the same position, and nowhere in any of them does rs1799963 appear. That leaves a reader two ways in: know that i3002432 means rs1799963, or find the row by its coordinate. The FDA decision summary records the equivalence[2]. A reader that matches by rsID alone finds nothing.

Terms this article relies on

Internal identifier
A name a chip vendor gives a probe that it has not labelled with an rsID. 23andMe's begin with i.
GRCh37 and GRCh38
Two versions of the human reference genome; GRCh38 is the newer. The same DNA has different coordinates in each[4]. Consumer chip files are written in GRCh37; our panel is written in GRCh38.
Flank
The bases on either side of a position. If the flanks match in both assemblies, the two coordinates point at the same piece of DNA.

What the variant does

Poort and colleagues in Leiden found the variant in 1996 while sequencing the prothrombin gene in 28 people from families with a history of venous thrombosis. The coding sequence held nothing unusual. One change turned up, in the untranslated region at the gene's 3' end: a G to A at nucleotide 20210, which is where the name comes from. Eighteen percent of those patients carried it, against 1 percent of 100 healthy controls[5]. In current notation the same change is c.*97G>A, 97 bases past the stop codon[1].

The same paper tested the variant in a population-based case-control study. The A allele raised the odds of venous thrombosis almost threefold, and 87 percent of people carrying it were in the top quarter of plasma prothrombin levels[5]. Five years later Gehring and colleagues showed why. The variant is the last base of the gene's messenger RNA, at the point where the message is cut and finished. The A makes that step more efficient, so more message accumulates and more protein is made[6]. The protein itself is normal. There is just more of it.

2.8

odds ratio for venous thrombosis with one A allele in the original population study[5]

3.8

odds ratio in a pooled analysis of 8 case-control studies, 2,310 cases and 3,204 controls[7]

20.0

odds ratio for people carrying one copy of both Prothrombin G20210A and Factor V Leiden[7]

An odds ratio compares groups; it is not anyone's personal chance of a clot. In the pooled data, 23 percent of patients carrying the prothrombin variant also carried Factor V Leiden, the other common inherited clotting variant[7]. MedlinePlus Genetics puts the risk of harmful clots with one copy at two to five times the average, with surgery, injury, pregnancy and oestrogen among the factors that add to it[8].

How common it is, and where

Rosendaal and colleagues pooled general-population samples from eleven centres in 1998: 111 carriers among 5,527 people, an overall prevalence of 2.0 percent. Southern Europe came out at 3.0 percent, northern Europe at 1.7, and the variant was very rare in people of Asian and African descent[9]. MedlinePlus gives two to five percent for Americans of European ancestry[8]. gnomAD, a public collection of sequenced exomes and genomes, now gives counts for far larger groups.

Table 1. rs1799963 in gnomAD v4.1, exomes and genomes together
Genetic ancestry groupPeopleA allele frequencyCarry at least one AAbout
Ashkenazi Jewish14,3063.50%6.9%1 in 15
Middle Eastern2,1191.79%3.5%1 in 29
Non-Finnish European535,4491.29%2.6%1 in 39
Admixed American29,2471.15%2.2%1 in 45
Finnish27,3400.49%1.0%1 in 100
African / African American36,3340.23%0.5%1 in 220
South Asian43,5900.20%0.4%1 in 260
East Asian22,0950.005%0.01%1 in 11,000

Source: gnomAD variant 11-46739505-G-A, read through the gnomAD API on 10 October 2026[10]. People is half the allele number. The carrier share is our estimate: heterozygous plus homozygous people, from gnomAD's allele and homozygote counts, divided by people.

Figure 1. The same estimate as a chart. Finns carry the variant at well under half the rate of other Europeans, consistent with the lower northern European prevalence Rosendaal's group reported[9]. The Middle Eastern group, 2,119 people, is the least certain.

For a service built in Finland the Finnish row matters: by our estimate, about one Finn in a hundred carries the variant, against about one in forty other Europeans. That is common enough that missing it on every 23andMe file was a real gap.

Why the reader missed it

Our report is built on a panel of positions written in GRCh38. The chip reader looks for each panel position by its rsID first and, if that is missing, by its coordinate. On a 23andMe file both lookups failed for Prothrombin, for different reasons at different times.

Figure 2. Three ways to look for the row. The first two cannot reach it; the third is the fix. The difference between the two coordinates is 21,550 bases, our arithmetic from the dbSNP positions[1].
Table 2. What a 23andMe file got for Prothrombin, by date
FromWhat the reader didWhat the chip section said
15 June 2026Matched chip findings by rsID onlyListed Prothrombin among the variants it had checked; when nothing was found, it said those variants were not present
26 July 2026A negative claim now needed proof the file could have shown the variantProthrombin not examined
8 August 2026Stopped looking up GRCh38 coordinates in GRCh37 filesProthrombin not examined
28 September 2026Reads i3002432 through a flank-verified GRCh37 coordinateThe call itself: a finding card for a carrier, nothing for GG

Source: Aimosti's git history: commits cda18199, 45d2b88b, 314e9bc0 and 412d1543. The fix was committed and deployed on 28 September; the call in the file is the same one 23andMe's own report reads[2].

The first stage was the worst. From June the chip section named Prothrombin G20210A as checked, and when it found nothing it said the variants were not present. For a 23andMe file that sentence was unearned: the reader had never seen the row, so a carrier and a non-carrier got the same words. A July quality review found the same pattern in several modules, "we did not see it" read as "it is not there", and from 26 July Prothrombin moved to a separate list of variants the file could not be read for.

On 8 August we found that the coordinate route had been comparing GRCh38 positions against GRCh37 files, where the same number points at a different place. On the Y chromosome a man's paternal-line markers were never found, and the note we showed him offered "this is expected if you are biologically female" as the first explanation. On the autosomes the lookup could land on an unrelated SNP, and only that SNP's letters stood between us and a made-up genotype.

So we stopped translating coordinates on GRCh37 files, except on the Y chromosome, through a table of positions checked one by one, and on mitochondrial DNA, which is numbered the same way in both assemblies. That refusal was right, and it kept the Prothrombin row unread for seven more weeks. For the two weeks before it, the coordinate route had been looking for the row at 46,739,505. The row is at 46,761,055.

A translation we would accept

We found the gap on 27 September, while rebuilding our sample chip report in the shape of a real 23andMe file. The fix is a short table of GRCh37 positions for panel sites that a real export ships under a vendor identifier. We looked up all 1,005 panel rsIDs in Ensembl's GRCh37 service and checked each 23andMe file for a call at that position under another identifier. Four sites turned up: Prothrombin, in all four files, and three sites used by polygenic scores.

Figure 3. The flank check for Prothrombin, with the bases read from Ensembl[11, 12]. The site reads G in both assemblies; a carrier's chip reports an A there.

Three candidates passed. The fourth, rs9411377, which 23andMe ships as i708994, sits in a run of repeated letters whose flanks differ between the assemblies. A repeat is exactly where a probe at the wrong place would still look plausible, so we left it out. If we cannot prove a mapping, we don't use it.

While measuring we found a second fault. 23andMe puts insertion and deletion probes, reported as I and D, at the same coordinate as ordinary probes, and our reader kept whichever row came last. It now sets the I and D rows aside, and if the remaining rows disagree, it leaves the position unread. None of the sites we read by coordinate sat on a disagreeing row in any of our test files.

We ran our 14 real chip exports through the reader before and after the change. Two things moved: Prothrombin is now read on all four 23andMe files, and two polygenic-score sites on the version 4 file. Nothing else changed. Factor V Leiden needed nothing; 23andMe ships it under its rsID, rs6025.

What the report shows now, file by file

Table 3. Prothrombin G20210A in an Aimosti report, by file type, as of 10 October 2026
FileHow the site is foundWhat the report shows
23andMe export (GRCh37)The i3002432 row, through the verified coordinateA carrier gets a Prothrombin G20210A card under risk factors, for that variant only. GG is listed as read, with no card. A missing row, or rows that disagree, is labelled not examined
Other chip exportsrs1799963 by its rsID, from any vendor that names it soThe same card. A row under a vendor's own id is read only at the verified GRCh37 position, from a file that states its build; otherwise it is labelled not examined
Plain VCFA variant record at the siteA carrier gets a finding card under risk factors, with ClinVar's classification, which in the current record is pathogenic or likely pathogenic with two review stars[13]. No record means no matching variant in the file, which is not proof the position was read
gVCFA variant record or a reference block over the siteThe same finding card for a carrier. A reference block with at least 10 reads lets the report count the position as examined, on a genotype-only F2 card
BAM or CRAM (Deep Read)The reads at the siteA genotype for F2. For one or two copies, the number of reads at the position and a note quoting MedlinePlus[8]; for none, a note that no allele was detected

Source: Aimosti's report code and content on 10 October 2026, with ClinVar's classification of the variant[13] and the MedlinePlus text the Deep Read note quotes[8].

Two limits on the chip rows. The card shows the variant's GRCh38 position and rsID, not the i3002432 row it was read from. And a chip call is one probe's reading. In a UK Biobank comparison with sequencing, chip calls for variants more common than 1 percent agreed with the sequence about 99 percent of the time, while calls for very rare variants mostly did not[14]. Prothrombin G20210A sits just above that line in Europeans. The FDA's summary also lists a nearby variant, rs112016113, that could interfere with 23andMe's probe and was not tested[2]. Why rare calls in raw data fail so often covers the other side.

Reports issued before 28 September still show Prothrombin as not examined, or, before 26 July, as one of the variants checked. If you have one, write to us and we will run it again.

What we take from it

"Not examined" is an honest label, and for nine weeks it covered a gap that was ours, not the file's. Before that, for six weeks, the report said something worse. A refusal deserves the same checking as a finding. Here the row was in every 23andMe file we had, and the FDA document naming it was public. Our account of lifting files from GRCh37 to GRCh38 covers the same coordinate problem in VCF files.

What Aimosti would (and wouldn't) show you

On a 23andMe file the report reads the i3002432 row through a coordinate we verified base by base, and a carrier gets a Prothrombin G20210A card for that variant only. If the row is missing or its rows disagree, the report says the variant was not examined. A VCF or gVCF carrier gets a card with ClinVar's classification, and a BAM or CRAM shows the genotype in the Deep Read panel.

What we won't claim

We won't read a position through a coordinate translation we have not checked base by base, and we won't present a Prothrombin result as a diagnosis or as a person's chance of a clot. It is a common risk factor, and many people who carry it never have one.

Bottom line. The call was in the file the whole time, under a name our reader did not look for. A rule we added to stop wrong answers also stopped this right one, and the fix had to meet the same standard of proof as the rule.

Questions people ask

What is i3002432 in my 23andMe raw data?

It is 23andMe's own identifier for Prothrombin G20210A, rs1799963, at chromosome 11, position 46,761,055 in GRCh37. The FDA's decision summary on 23andMe's thrombophilia report names the variant as rs1799963/i3002432[2]. A genotype of GG means two copies of the usual base; GA or AG means one copy of the variant.

Is Prothrombin G20210A the same as Factor V Leiden?

No. They are different variants in different genes, F2 and F5, and both raise the odds of venous thrombosis. A pooled analysis of eight studies put the odds ratios at 3.8 for the prothrombin variant and 4.9 for Factor V Leiden, and 20.0 for people carrying one copy of each[7]. Our Factor V Leiden article covers the other one.

Do AncestryDNA or MyHeritage files include Prothrombin G20210A?

We have measured only 23andMe's handling of this site; our test files from other vendors do not settle it. Our reader finds rs1799963 by its rsID in any chip export that names it so. A row under a vendor's own identifier is read only at the verified GRCh37 position, and only from a file that states its reference build. MyHeritage and FamilyTreeDNA files usually state none, and then the report says the variant was not examined.

My report from before 28 September says Prothrombin was not examined. Was the row missing from my file?

If the file came from 23andMe, almost certainly not. Every 23andMe export we have tested carries the row; our reader did not read it until 28 September. Write to us and we will run the report again with the current reader.

References

  1. rs1799963 (F2): NC_000011.10:g.46739505G>A, NC_000011.9:g.46761055G>A, NM_000506.5:c.*97G>A. NCBI dbSNP, 2026. Read through NCBI E-utilities on 10 October 2026: GRCh38 position 11:46739505, previous assembly 11:46761055.
  2. U.S. Food and Drug Administration. Decision summary DEN160026: 23andMe Personal Genome Service Genetic Health Risk tests, including Hereditary Thrombophilia. FDA, Center for Devices and Radiological Health, 2017. Section D: Factor V Leiden (rs6025) and Prothrombin G20210A (rs1799963/i3002432). Originally issued 6 April 2017; corrected 2 November 2017.
  3. rs1799963 on GRCh37: 11:46761055, alleles G/A, 3 prime UTR variant. Ensembl GRCh37, 2026. Read through the Ensembl REST API on 10 October 2026.
  4. Human genome assemblies: GRCh37 and GRCh38. Genome Reference Consortium, 2026.
  5. Poort SR, Rosendaal FR, Reitsma PH, Bertina RM. A common genetic variation in the 3'-untranslated region of the prothrombin gene is associated with elevated plasma prothrombin levels and an increase in venous thrombosis. Blood, 1996. doi:10.1182/blood.v88.10.3698.bloodjournal88103698
  6. Gehring NH, Frede U, Neu-Yilik G, et al. Increased efficiency of mRNA 3' end formation: a new genetic mechanism contributing to hereditary thrombophilia. Nature Genetics, 2001. doi:10.1038/ng578
  7. Emmerich J, Rosendaal FR, Cattaneo M, et al. Combined effect of factor V Leiden and prothrombin 20210A on the risk of venous thromboembolism: pooled analysis of 8 case-control studies including 2310 cases and 3204 controls. Thrombosis and Haemostasis, 2001.
  8. Prothrombin thrombophilia. MedlinePlus Genetics, U.S. National Library of Medicine, 2026.
  9. Rosendaal FR, Doggen CJ, Zivelin A, et al. Geographic distribution of the 20210 G to A prothrombin variant. Thrombosis and Haemostasis, 1998. doi:10.1055/s-0037-1615049
  10. Variant 11-46739505-G-A (rs1799963), gnomAD v4.1 exomes and genomes. Genome Aggregation Database (gnomAD), 2026. Read through the gnomAD API on 10 October 2026; exome and genome counts added together.
  11. Human GRCh38 chromosome 11, bases 46,739,485 to 46,739,525. Ensembl REST API, 2026. CAATAAAAGTGACTCTCAGCGAGCCTCAATGCTCCCAGTGC, read 10 October 2026.
  12. Human GRCh37 chromosome 11, bases 46,761,035 to 46,761,075. Ensembl REST API (GRCh37), 2026. CAATAAAAGTGACTCTCAGCGAGCCTCAATGCTCCCAGTGC, read 10 October 2026.
  13. VCV000013310: NM_000506.5(F2):c.*97G>A. NCBI ClinVar, 2026. Read through NCBI E-utilities on 10 October 2026: Pathogenic/Likely pathogenic/Pathogenic, low penetrance/Established risk allele; risk factor. Criteria provided, multiple submitters, no conflicts (two stars); last evaluated 3 February 2026.
  14. Weedon MN, Jackson L, Harrison JW, et al. Use of SNP chips to detect rare pathogenic variants: retrospective, population based diagnostic evaluation. BMJ, 2021. doi:10.1136/bmj.n214

Last reviewed . Every number on this page links to the source it comes from; if one of them has moved, tell us.

Free · in your browser

Find out what your own file can read.

The free check opens your DNA file on your device and shows which format you have and what a report could read from it. The file is never uploaded.

Check your fileSee a sample report