Skip to content

Create an account and get up to 25% off.

Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

Metabolism of nucleotides

R-MMU-15869 in Reactome release 97: under Metabolism, with 99 genes placed in it by the mapping files and 4 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-HSA-15869 (human), R-RNO-15869 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this mouse pathway

The mapping files place 99 genes in this mouse pathway; showing 1 to 99, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAdaAuthority11486Mapping file id11486 NCBI fileEvidenceIEA
GeneAdkAuthority11534Mapping file id11534 NCBI fileEvidenceIEA
GeneAdprmAuthority66358Mapping file id66358 NCBI fileEvidenceIEA
GeneAdslAuthority11564Mapping file id11564 NCBI fileEvidenceIEA
GeneAdss1Authority11565Mapping file id11565 NCBI fileEvidenceIEA
GeneAdss2Authority11566Mapping file id11566 NCBI fileEvidenceIEA
GeneAk1Authority11636Mapping file id11636 NCBI fileEvidenceIEA
GeneAk2Authority11637Mapping file id11637 NCBI fileEvidenceIEA
GeneAk4Authority11639Mapping file id11639 NCBI fileEvidenceIEA
GeneAk5Authority229949Mapping file id229949 NCBI fileEvidenceIEA
GeneAk6Authority102216272Mapping file id102216272 NCBI fileEvidenceIEA
GeneAk7Authority78801Mapping file id78801 NCBI fileEvidenceIEA
GeneAk8Authority68870Mapping file id68870 NCBI fileEvidenceIEA
GeneAk9Authority633979Mapping file idENSMUSG00000091415 Ensembl fileEvidenceIEA
GeneAmpd1Authority229665Mapping file id229665 NCBI fileEvidenceIEA
GeneAmpd2Authority109674Mapping file id109674 NCBI fileEvidenceIEA
GeneAmpd3Authority11717Mapping file id11717 NCBI fileEvidenceIEA
GeneAprtAuthority11821Mapping file id11821 NCBI fileEvidenceIEA
GeneAticAuthority108147Mapping file id108147 NCBI fileEvidenceIEA
GeneCadAuthority69719Mapping file id69719 NCBI fileEvidenceIEA
GeneCdaAuthority72269Mapping file id72269 NCBI fileEvidenceIEA
GeneCmpk1Authority66588Mapping file id66588 NCBI fileEvidenceIEA
GeneCtps1Authority51797Mapping file id51797 NCBI fileEvidenceIEA
GeneCtps2Authority55936Mapping file id55936 NCBI fileEvidenceIEA
GeneDckAuthority13178Mapping file id13178 NCBI fileEvidenceIEA
GeneDctdAuthority320685Mapping file id320685 NCBI fileEvidenceIEA
GeneDguokAuthority27369Mapping file id27369 NCBI fileEvidenceIEA
GeneDhodhAuthority56749Mapping file id56749 NCBI fileEvidenceIEA
GeneDnph1Authority381101Mapping file id381101 NCBI fileEvidenceIEA
GeneDpydAuthority99586Mapping file id99586 NCBI fileEvidenceIEA
GeneDpysAuthority64705Mapping file id64705 NCBI fileEvidenceIEA
GeneDtymkAuthority21915Mapping file id21915 NCBI fileEvidenceIEA
GeneDutAuthority110074Mapping file id110074 NCBI fileEvidenceIEA
GeneEntpd1Authority12495Mapping file id12495 NCBI fileEvidenceIEA
GeneEntpd2Authority12496Mapping file id12496 NCBI fileEvidenceIEA
GeneEntpd3Authority215446Mapping file id215446 NCBI fileEvidenceIEA
GeneEntpd4Authority67464Mapping file id67464 NCBI fileEvidenceIEA
GeneEntpd4bAuthority100862375Mapping file idENSMUSG00000022066 Ensembl fileEvidenceIEA
GeneEntpd5Authority12499Mapping file id12499 NCBI fileEvidenceIEA
GeneEntpd6Authority12497Mapping file id12497 NCBI fileEvidenceIEA
GeneEntpd7Authority93685Mapping file id93685 NCBI fileEvidenceIEA
GeneEntpd8Authority72090Mapping file id72090 NCBI fileEvidenceIEA
GeneGartAuthority14450Mapping file id14450 NCBI fileEvidenceIEA
GeneGdaAuthority14544Mapping file id14544 NCBI fileEvidenceIEA
GeneGlrxAuthority93692Mapping file id93692 NCBI fileEvidenceIEA
GeneGmprAuthority66355Mapping file id66355 NCBI fileEvidenceIEA
GeneGmpr2Authority105446Mapping file id105446 NCBI fileEvidenceIEA
GeneGmpsAuthority229363Mapping file id229363 NCBI fileEvidenceIEA
GeneGsrAuthority14782Mapping file id14782 NCBI fileEvidenceIEA
GeneGuk1Authority14923Mapping file id14923 NCBI fileEvidenceIEA
GeneHprt1Authority15452Mapping file id15452 NCBI fileEvidenceIEA
GeneImpdh1Authority23917Mapping file id23917 NCBI fileEvidenceIEA
GeneImpdh2Authority23918Mapping file id23918 NCBI fileEvidenceIEA
GeneItpaAuthority16434Mapping file id16434 NCBI fileEvidenceIEA
GeneMapdaAuthority75894Mapping file id75894 NCBI fileEvidenceIEA
GeneNme1Authority18102Mapping file id18102 NCBI fileEvidenceIEA
GeneNme2Authority18103Mapping file id18103 NCBI fileEvidenceIEA
GeneNme3Authority79059Mapping file id79059 NCBI fileEvidenceIEA
GeneNme4Authority56520Mapping file id56520 NCBI fileEvidenceIEA
GeneNme6Authority54369Mapping file id54369 NCBI fileEvidenceIEA
GeneNt5cAuthority50773Mapping file id50773 NCBI fileEvidenceIEA
GeneNt5c1aAuthority230718Mapping file id230718 NCBI fileEvidenceIEA
GeneNt5c1bAuthority70881Mapping file id70881 NCBI fileEvidenceIEA
GeneNt5c2Authority76952Mapping file id76952 NCBI fileEvidenceIEA
GeneNt5c3Authority107569Mapping file id107569 NCBI fileEvidenceIEA
GeneNt5eAuthority23959Mapping file id23959 NCBI fileEvidenceIEA
GeneNt5mAuthority103850Mapping file id103850 NCBI fileEvidenceIEA
GeneNudt1Authority17766Mapping file id17766 NCBI fileEvidenceIEA
GeneNudt13Authority67725Mapping file id67725 NCBI fileEvidenceIEA
GeneNudt15Authority214254Mapping file id214254 NCBI fileEvidenceIEA
GeneNudt16Authority75686Mapping file id75686 NCBI fileEvidenceIEA
GeneNudt18Authority213484Mapping file id213484 NCBI fileEvidenceIEA
GeneNudt5Authority53893Mapping file id53893 NCBI fileEvidenceIEA
GeneNudt9Authority74167Mapping file id74167 NCBI fileEvidenceIEA
GenePaicsAuthority67054Mapping file id67054 NCBI fileEvidenceIEA
GenePfasAuthority237823Mapping file id237823 NCBI fileEvidenceIEA
GenePnpAuthority18950Mapping file id18950 NCBI fileEvidenceIEA
GenePnp2Authority667034Mapping file id667034 NCBI fileEvidenceIEA
GenePpatAuthority231327Mapping file id231327 NCBI fileEvidenceIEA
GenePudpAuthority67365Mapping file id67365 NCBI fileEvidenceIEA
GeneRrm1Authority20133Mapping file id20133 NCBI fileEvidenceIEA
GeneRrm2Authority20135Mapping file id20135 NCBI fileEvidenceIEA
GeneRrm2bAuthority382985Mapping file id382985 NCBI fileEvidenceIEA
GeneSamhd1Authority56045Mapping file id56045 NCBI fileEvidenceIEA
GeneTaf9Authority108143Mapping file idENSMUSG00000078941 Ensembl fileEvidenceIEA
GeneTk1Authority21877Mapping file id21877 NCBI fileEvidenceIEA
GeneTk2Authority57813Mapping file idENSMUSG00000035824 Ensembl fileEvidenceIEA
GeneTxn1Authority22166Mapping file id22166 NCBI fileEvidenceIEA
GeneTxnrd1Authority50493Mapping file id50493 NCBI fileEvidenceIEA
GeneTympAuthority72962Mapping file id72962 NCBI fileEvidenceIEA
GeneTymsAuthority22171Mapping file id22171 NCBI fileEvidenceIEA
GeneUck1Authority22245Mapping file id22245 NCBI fileEvidenceIEA
GeneUck2Authority80914Mapping file id80914 NCBI fileEvidenceIEA
GeneUckl1Authority68556Mapping file id68556 NCBI fileEvidenceIEA
GeneUmpsAuthority22247Mapping file id22247 NCBI fileEvidenceIEA
GeneUpb1Authority103149Mapping file id103149 NCBI fileEvidenceIEA
GeneUpp1Authority22271Mapping file id22271 NCBI fileEvidenceIEA
GeneUpp2Authority76654Mapping file id76654 NCBI fileEvidenceIEA
GeneXdhAuthority22436Mapping file id22436 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the mouse pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.