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

R-MMU-1430728 in Reactome release 97: a top-level pathway, with 1,849 genes placed in it by the mapping files and 14 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-1430728 (human), R-RNO-1430728 (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 1,849 genes in this mouse pathway; showing 701 to 800, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 8 of 19
GeneGcshAuthority68133Mapping file id68133 NCBI fileEvidenceIEA
GeneGdaAuthority14544Mapping file id14544 NCBI fileEvidenceIEA
GeneGde1Authority56209Mapping file id56209 NCBI fileEvidenceIEA
GeneGdf1Authority14559Mapping file idENSMUSG00000087408 Ensembl fileEvidenceIEA
GeneGgctAuthority110175Mapping file id110175 NCBI fileEvidenceIEA
GeneGgps1Authority14593Mapping file id14593 NCBI fileEvidenceIEA
GeneGgt1Authority14598Mapping file id14598 NCBI fileEvidenceIEA
GeneGgt5Authority23887Mapping file id23887 NCBI fileEvidenceIEA
GeneGgt6Authority71522Mapping file id71522 NCBI fileEvidenceIEA
GeneGgt7Authority207182Mapping file id207182 NCBI fileEvidenceIEA
GeneGid4Authority66771Mapping file id66771 NCBI fileEvidenceIEA
GeneGid8Authority76425Mapping file id76425 NCBI fileEvidenceIEA
GeneGkAuthority14933Mapping file id14933 NCBI fileEvidenceIEA
GeneGk2Authority14626Mapping file id14626 NCBI fileEvidenceIEA
GeneGlaAuthority11605Mapping file idENSMUSG00000031266 Ensembl fileEvidenceIEA
GeneGlb1Authority12091Mapping file id12091 NCBI fileEvidenceIEA
GeneGlb1lAuthority74577Mapping file id74577 NCBI fileEvidenceIEA
GeneGlb1l2Authority244757Mapping file id244757 NCBI fileEvidenceIEA
GeneGlb1l3Authority70893Mapping file id70893 NCBI fileEvidenceIEA
GeneGldcAuthority104174Mapping file id104174 NCBI fileEvidenceIEA
GeneGlo1Authority109801Mapping file id109801 NCBI fileEvidenceIEA
GeneGlp1rAuthority14652Mapping file id14652 NCBI fileEvidenceIEA
GeneGlrxAuthority93692Mapping file id93692 NCBI fileEvidenceIEA
GeneGlrx5Authority73046Mapping file id73046 NCBI fileEvidenceIEA
GeneGlsAuthority14660Mapping file id14660 NCBI fileEvidenceIEA
GeneGls2Authority216456Mapping file id216456 NCBI fileEvidenceIEA
GeneGlud1Authority14661Mapping file id14661 NCBI fileEvidenceIEA
GeneGlulAuthority14645Mapping file id14645 NCBI fileEvidenceIEA
GeneGlyatAuthority107146Mapping file id107146 NCBI fileEvidenceIEA
GeneGlyatl3Authority435528Mapping file id435528 NCBI fileEvidenceIEA
GeneGlyctkAuthority235582Mapping file id235582 NCBI fileEvidenceIEA
GeneGm2aAuthority14667Mapping file id14667 NCBI fileEvidenceIEA
GeneGmprAuthority66355Mapping file id66355 NCBI fileEvidenceIEA
GeneGmpr2Authority105446Mapping file id105446 NCBI fileEvidenceIEA
GeneGmpsAuthority229363Mapping file id229363 NCBI fileEvidenceIEA
GeneGna11Authority14672Mapping file id14672 NCBI fileEvidenceIEA
GeneGna14Authority14675Mapping file id14675 NCBI fileEvidenceIEA
GeneGnai1Authority14677Mapping file id14677 NCBI fileEvidenceIEA
GeneGnai2Authority14678Mapping file id14678 NCBI fileEvidenceIEA
GeneGnaqAuthority14682Mapping file id14682 NCBI fileEvidenceIEA
GeneGnasAuthority14683Mapping file id14683 NCBI fileEvidenceIEA
GeneGnb1Authority14688Mapping file id14688 NCBI fileEvidenceIEA
GeneGnb2Authority14693Mapping file id14693 NCBI fileEvidenceIEA
GeneGnb3Authority14695Mapping file id14695 NCBI fileEvidenceIEA
GeneGnb4Authority14696Mapping file id14696 NCBI fileEvidenceIEA
GeneGnb5Authority14697Mapping file id14697 NCBI fileEvidenceIEA
GeneGng10Authority14700Mapping file id14700 NCBI fileEvidenceIEA
GeneGng11Authority66066Mapping file id66066 NCBI fileEvidenceIEA
GeneGng12Authority14701Mapping file id14701 NCBI fileEvidenceIEA
GeneGng13Authority64337Mapping file id64337 NCBI fileEvidenceIEA
GeneGng2Authority14702Mapping file id14702 NCBI fileEvidenceIEA
GeneGng3Authority14704Mapping file id14704 NCBI fileEvidenceIEA
GeneGng4Authority14706Mapping file id14706 NCBI fileEvidenceIEA
GeneGng5Authority14707Mapping file id14707 NCBI fileEvidenceIEA
GeneGng7Authority14708Mapping file id14708 NCBI fileEvidenceIEA
GeneGng8Authority14709Mapping file id14709 NCBI fileEvidenceIEA
GeneGngt1Authority14699Mapping file id14699 NCBI fileEvidenceIEA
GeneGngt2Authority14710Mapping file id14710 NCBI fileEvidenceIEA
GeneGnmtAuthority14711Mapping file id14711 NCBI fileEvidenceIEA
GeneGnpatAuthority14712Mapping file id14712 NCBI fileEvidenceIEA
GeneGnpda1Authority26384Mapping file id26384 NCBI fileEvidenceIEA
GeneGnpda2Authority67980Mapping file id67980 NCBI fileEvidenceIEA
GeneGnsAuthority75612Mapping file id75612 NCBI fileEvidenceIEA
GeneGot1Authority14718Mapping file id14718 NCBI fileEvidenceIEA
GeneGot2Authority14719Mapping file id14719 NCBI fileEvidenceIEA
GeneGpamAuthority14732Mapping file id14732 NCBI fileEvidenceIEA
GeneGpat2Authority215456Mapping file id215456 NCBI fileEvidenceIEA
GeneGpat3Authority231510Mapping file id231510 NCBI fileEvidenceIEA
GeneGpat4Authority102247Mapping file id102247 NCBI fileEvidenceIEA
GeneGpc1Authority14733Mapping file id14733 NCBI fileEvidenceIEA
GeneGpc2Authority71951Mapping file id71951 NCBI fileEvidenceIEA
GeneGpc3Authority14734Mapping file id14734 NCBI fileEvidenceIEA
GeneGpc4Authority14735Mapping file id14735 NCBI fileEvidenceIEA
GeneGpc5Authority103978Mapping file id103978 NCBI fileEvidenceIEA
GeneGpc6Authority23888Mapping file id23888 NCBI fileEvidenceIEA
GeneGpd1Authority14555Mapping file id14555 NCBI fileEvidenceIEA
GeneGpd1lAuthority333433Mapping file id333433 NCBI fileEvidenceIEA
GeneGpd2Authority14571Mapping file id14571 NCBI fileEvidenceIEA
GeneGphnAuthority268566Mapping file id268566 NCBI fileEvidenceIEA
GeneGpi1Authority14751Mapping file id14751 NCBI fileEvidenceIEA
GeneGpihbp1Authority68453Mapping file id68453 NCBI fileEvidenceIEA
GeneGptAuthority76282Mapping file id76282 NCBI fileEvidenceIEA
GeneGpt2Authority108682Mapping file id108682 NCBI fileEvidenceIEA
GeneGpx1Authority14775Mapping file id14775 NCBI fileEvidenceIEA
GeneGpx2Authority14776Mapping file id14776 NCBI fileEvidenceIEA
GeneGpx4Authority625249Mapping file id625249 NCBI fileEvidenceIEA
GeneGrhprAuthority76238Mapping file id76238 NCBI fileEvidenceIEA
GeneGsrAuthority14782Mapping file id14782 NCBI fileEvidenceIEA
GeneGssAuthority14854Mapping file id14854 NCBI fileEvidenceIEA
GeneGsta1Authority14857Mapping file id14857 NCBI fileEvidenceIEA
GeneGsta13Authority100042295Mapping file id100042295 NCBI fileEvidenceIEA
GeneGsta2Authority14858Mapping file id14858 NCBI fileEvidenceIEA
GeneGsta3Authority14859Mapping file id14859 NCBI fileEvidenceIEA
GeneGsta5Authority100042314Mapping file id100042314 NCBI fileEvidenceIEA
GeneGstk1Authority76263Mapping file id76263 NCBI fileEvidenceIEA
GeneGstm1Authority14862Mapping file id14862 NCBI fileEvidenceIEA
GeneGstm2Authority14863Mapping file id14863 NCBI fileEvidenceIEA
GeneGstm3Authority14864Mapping file id14864 NCBI fileEvidenceIEA
GeneGstm4Authority14865Mapping file id14865 NCBI fileEvidenceIEA
GeneGstm5Authority14866Mapping file id14866 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.