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.

Glucose metabolism

R-MMU-70326 in Reactome release 97: under Metabolism of carbohydrates and carbohydrate derivatives, with 72 genes placed in it by the mapping files and 2 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-70326 (human), R-RNO-70326 (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 72 genes in this mouse pathway; showing 1 to 72, 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
GeneAaasAuthority223921Mapping file id223921 NCBI fileEvidenceIEA
GeneAdpgkAuthority72141Mapping file id72141 NCBI fileEvidenceIEA
GeneAldoaAuthority11674Mapping file id11674 NCBI fileEvidenceIEA
GeneAldobAuthority230163Mapping file id230163 NCBI fileEvidenceIEA
GeneAldocAuthority11676Mapping file id11676 NCBI fileEvidenceIEA
GeneBpgmAuthority12183Mapping file id12183 NCBI fileEvidenceIEA
GeneEno2Authority13807Mapping file id13807 NCBI fileEvidenceIEA
GeneEno3Authority13808Mapping file id13808 NCBI fileEvidenceIEA
GeneEno4Authority226265Mapping file id226265 NCBI fileEvidenceIEA
GeneFbp1Authority14121Mapping file id14121 NCBI fileEvidenceIEA
GeneFbp2Authority14120Mapping file id14120 NCBI fileEvidenceIEA
GeneG6pc1Authority14377Mapping file id14377 NCBI fileEvidenceIEA
GeneG6pc2Authority14378Mapping file id14378 NCBI fileEvidenceIEA
GeneG6pc3Authority68401Mapping file id68401 NCBI fileEvidenceIEA
GeneGapdhAuthority14433Mapping file id14433 NCBI fileEvidenceIEA
GeneGapdhsAuthority14447Mapping file id14447 NCBI fileEvidenceIEA
GeneGckAuthority103988Mapping file id103988 NCBI fileEvidenceIEA
GeneGckrAuthority231103Mapping file id231103 NCBI fileEvidenceIEA
GeneGnpda1Authority26384Mapping file id26384 NCBI fileEvidenceIEA
GeneGnpda2Authority67980Mapping file id67980 NCBI fileEvidenceIEA
GeneGpi1Authority14751Mapping file id14751 NCBI fileEvidenceIEA
GeneHk2Authority15277Mapping file id15277 NCBI fileEvidenceIEA
GeneHk3Authority212032Mapping file id212032 NCBI fileEvidenceIEA
GeneHkdc1Authority216019Mapping file id216019 NCBI fileEvidenceIEA
GeneNdc1Authority72787Mapping file id72787 NCBI fileEvidenceIEA
GeneNup107Authority103468Mapping file id103468 NCBI fileEvidenceIEA
GeneNup133Authority234865Mapping file id234865 NCBI fileEvidenceIEA
GeneNup153Authority218210Mapping file id218210 NCBI fileEvidenceIEA
GeneNup155Authority170762Mapping file id170762 NCBI fileEvidenceIEA
GeneNup160Authority59015Mapping file id59015 NCBI fileEvidenceIEA
GeneNup188Authority227699Mapping file id227699 NCBI fileEvidenceIEA
GeneNup205Authority70699Mapping file id70699 NCBI fileEvidenceIEA
GeneNup210Authority54563Mapping file id54563 NCBI fileEvidenceIEA
GeneNup214Authority227720Mapping file id227720 NCBI fileEvidenceIEA
GeneNup35Authority69482Mapping file id69482 NCBI fileEvidenceIEA
GeneNup37Authority69736Mapping file id69736 NCBI fileEvidenceIEA
GeneNup42Authority231042Mapping file id231042 NCBI fileEvidenceIEA
GeneNup43Authority69912Mapping file id69912 NCBI fileEvidenceIEA
GeneNup50Authority18141Mapping file id18141 NCBI fileEvidenceIEA
GeneNup54Authority269113Mapping file id269113 NCBI fileEvidenceIEA
GeneNup58Authority71844Mapping file id71844 NCBI fileEvidenceIEA
GeneNup62Authority18226Mapping file id18226 NCBI fileEvidenceIEA
GeneNup85Authority445007Mapping file id445007 NCBI fileEvidenceIEA
GeneNup88Authority19069Mapping file id19069 NCBI fileEvidenceIEA
GeneNup93Authority71805Mapping file id71805 NCBI fileEvidenceIEA
GeneNup98Authority269966Mapping file id269966 NCBI fileEvidenceIEA
GenePck1Authority18534Mapping file id18534 NCBI fileEvidenceIEA
GenePck2Authority74551Mapping file id74551 NCBI fileEvidenceIEA
GenePcxAuthority18563Mapping file idENSMUSG00000024892 Ensembl fileEvidenceIEA
GenePfkfb1Authority18639Mapping file id18639 NCBI fileEvidenceIEA
GenePfkfb2Authority18640Mapping file id18640 NCBI fileEvidenceIEA
GenePfkfb3Authority170768Mapping file id170768 NCBI fileEvidenceIEA
GenePfkfb4Authority270198Mapping file id270198 NCBI fileEvidenceIEA
GenePfklAuthority18641Mapping file id18641 NCBI fileEvidenceIEA
GenePfkmAuthority18642Mapping file id18642 NCBI fileEvidenceIEA
GenePfkpAuthority56421Mapping file id56421 NCBI fileEvidenceIEA
GenePgam1Authority18648Mapping file id18648 NCBI fileEvidenceIEA
GenePgam2Authority56012Mapping file id56012 NCBI fileEvidenceIEA
GenePgk1Authority18655Mapping file id18655 NCBI fileEvidenceIEA
GenePgk2Authority18663Mapping file id18663 NCBI fileEvidenceIEA
GenePgm2l1Authority70974Mapping file id70974 NCBI fileEvidenceIEA
GenePkmAuthority18746Mapping file id18746 NCBI fileEvidenceIEA
GenePom121Authority107939Mapping file id107939 NCBI fileEvidenceIEA
GeneRae1Authority66679Mapping file id66679 NCBI fileEvidenceIEA
GeneRanbp2Authority19386Mapping file id19386 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSeh1lAuthority72124Mapping file id72124 NCBI fileEvidenceIEA
GeneSlc37a1Authority224674Mapping file id224674 NCBI fileEvidenceIEA
GeneSlc37a2Authority56857Mapping file id56857 NCBI fileEvidenceIEA
GeneSlc37a4Authority14385Mapping file id14385 NCBI fileEvidenceIEA
GeneTpi1Authority21991Mapping file id21991 NCBI fileEvidenceIEA
GeneTprAuthority108989Mapping file id108989 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.