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.

Apoptotic execution phase

R-MMU-75153 in Reactome release 97: under Apoptosis, with 50 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-75153 (human), R-RNO-75153 (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 50 genes in this mouse pathway; showing 1 to 50, 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
GeneAcin1Authority56215Mapping file id56215 NCBI fileEvidenceIEA
GeneAdd1Authority11518Mapping file id11518 NCBI fileEvidenceIEA
GeneApcAuthority11789Mapping file idENSMUSG00000005871 Ensembl fileEvidenceIEA
GeneBcap31Authority27061Mapping file id27061 NCBI fileEvidenceIEA
GeneBirc2Authority11797Mapping file id11797 NCBI fileEvidenceIEA
GeneBmxAuthority12169Mapping file id12169 NCBI fileEvidenceIEA
GeneCasp3Authority12367Mapping file id12367 NCBI fileEvidenceIEA
GeneCasp6Authority12368Mapping file id12368 NCBI fileEvidenceIEA
GeneCasp7Authority12369Mapping file id12369 NCBI fileEvidenceIEA
GeneCasp8Authority12370Mapping file id12370 NCBI fileEvidenceIEA
GeneCdh1Authority12550Mapping file id12550 NCBI fileEvidenceIEA
GeneClspnAuthority269582Mapping file id269582 NCBI fileEvidenceIEA
GeneCtnnb1Authority12387Mapping file id12387 NCBI fileEvidenceIEA
GeneDffaAuthority13347Mapping file id13347 NCBI fileEvidenceIEA
GeneDffbAuthority13368Mapping file id13368 NCBI fileEvidenceIEA
GeneDnm1lAuthority74006Mapping file id74006 NCBI fileEvidenceIEA
GeneDsg1aAuthority13510Mapping file id13510 NCBI fileEvidenceIEA
GeneDsg2Authority13511Mapping file id13511 NCBI fileEvidenceIEA
GeneDsg3Authority13512Mapping file id13512 NCBI fileEvidenceIEA
GeneDspAuthority109620Mapping file id109620 NCBI fileEvidenceIEA
GeneFntaAuthority14272Mapping file id14272 NCBI fileEvidenceIEA
GeneGas2Authority14453Mapping file id14453 NCBI fileEvidenceIEA
GeneGsnAuthority227753Mapping file id227753 NCBI fileEvidenceIEA
GeneH1f0Authority14958Mapping file id14958 NCBI fileEvidenceIEA
GeneH1f1Authority80838Mapping file id80838 NCBI fileEvidenceIEA
GeneH1f3Authority14957Mapping file id14957 NCBI fileEvidenceIEA
GeneH1f4Authority50709Mapping file id50709 NCBI fileEvidenceIEA
GeneH1f5Authority56702Mapping file id56702 NCBI fileEvidenceIEA
GeneHmgb1Authority15289Mapping file id15289 NCBI fileEvidenceIEA
GeneHmgb2Authority97165Mapping file id97165 NCBI fileEvidenceIEA
GeneKpna1Authority16646Mapping file id16646 NCBI fileEvidenceIEA
GeneKpnb1Authority16211Mapping file id16211 NCBI fileEvidenceIEA
GeneLmnaAuthority16905Mapping file id16905 NCBI fileEvidenceIEA
GeneLmnb1Authority16906Mapping file id16906 NCBI fileEvidenceIEA
GeneMaptAuthority17762Mapping file id17762 NCBI fileEvidenceIEA
GeneOclnAuthority18260Mapping file id18260 NCBI fileEvidenceIEA
GenePkp1Authority18772Mapping file id18772 NCBI fileEvidenceIEA
GenePlecAuthority18810Mapping file id18810 NCBI fileEvidenceIEA
GenePrkcdAuthority18753Mapping file id18753 NCBI fileEvidenceIEA
GenePrkcqAuthority18761Mapping file id18761 NCBI fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GeneRock1Authority19877Mapping file id19877 NCBI fileEvidenceIEA
GeneSatb1Authority20230Mapping file id20230 NCBI fileEvidenceIEA
GeneSh3glb2Authority227700Mapping file id227700 NCBI fileEvidenceIEA
GeneSptan1Authority20740Mapping file id20740 NCBI fileEvidenceIEA
GeneStk24Authority223255Mapping file id223255 NCBI fileEvidenceIEA
GeneStk26Authority70415Mapping file id70415 NCBI fileEvidenceIEA
GeneTjp1Authority21872Mapping file id21872 NCBI fileEvidenceIEA
GeneTjp2Authority21873Mapping file id21873 NCBI fileEvidenceIEA
GeneVimAuthority22352Mapping file id22352 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.