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.

Cellular responses to stimuli

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

Genes Reactome places in this mouse pathway, page 4 of 6
GeneHspa5Authority14828Mapping file id14828 NCBI fileEvidenceIEA
GeneHspa8Authority15481Mapping file id15481 NCBI fileEvidenceIEA
GeneHspa9Authority15526Mapping file id15526 NCBI fileEvidenceIEA
GeneHspb8Authority80888Mapping file id80888 NCBI fileEvidenceIEA
GeneHsph1Authority15505Mapping file id15505 NCBI fileEvidenceIEA
GeneId1Authority15901Mapping file idENSMUSG00000042745 Ensembl fileEvidenceIEA
GeneIkbkbAuthority16150Mapping file id16150 NCBI fileEvidenceIEA
GeneIkbkeAuthority56489Mapping file id56489 NCBI fileEvidenceIEA
GeneIkbkgAuthority16151Mapping file id16151 NCBI fileEvidenceIEA
GeneItfg2Authority101142Mapping file id101142 NCBI fileEvidenceIEA
GeneItga5Authority16402Mapping file id16402 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneJunAuthority16476Mapping file id16476 NCBI fileEvidenceIEA
GeneKat5Authority81601Mapping file id81601 NCBI fileEvidenceIEA
GeneKdm6bAuthority216850Mapping file id216850 NCBI fileEvidenceIEA
GeneKeap1Authority50868Mapping file id50868 NCBI fileEvidenceIEA
GeneKics2Authority270802Mapping file id270802 NCBI fileEvidenceIEA
GeneKptnAuthority70394Mapping file idENSMUSG00000006021 Ensembl fileEvidenceIEA
GeneLamtor1Authority66508Mapping file id66508 NCBI fileEvidenceIEA
GeneLamtor2Authority83409Mapping file id83409 NCBI fileEvidenceIEA
GeneLamtor3Authority56692Mapping file id56692 NCBI fileEvidenceIEA
GeneLamtor4Authority66096Mapping file id66096 NCBI fileEvidenceIEA
GeneLamtor5Authority68576Mapping file id68576 NCBI fileEvidenceIEA
GeneLimd1Authority29806Mapping file id29806 NCBI fileEvidenceIEA
GeneLmnb1Authority16906Mapping file id16906 NCBI fileEvidenceIEA
GeneLy96Authority17087Mapping file id17087 NCBI fileEvidenceIEA
GeneMafkAuthority17135Mapping file id17135 NCBI fileEvidenceIEA
GeneMap1lc3bAuthority67443Mapping file id67443 NCBI fileEvidenceIEA
GeneMap2k3Authority26397Mapping file id26397 NCBI fileEvidenceIEA
GeneMap2k4Authority26398Mapping file id26398 NCBI fileEvidenceIEA
GeneMap2k6Authority26399Mapping file id26399 NCBI fileEvidenceIEA
GeneMap2k7Authority26400Mapping file id26400 NCBI fileEvidenceIEA
GeneMap3k5Authority26408Mapping file id26408 NCBI fileEvidenceIEA
GeneMap4k4Authority26921Mapping file id26921 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk10Authority26414Mapping file id26414 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMapk8Authority26419Mapping file id26419 NCBI fileEvidenceIEA
GeneMapk9Authority26420Mapping file id26420 NCBI fileEvidenceIEA
GeneMapkap1Authority227743Mapping file id227743 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneMapkapk5Authority17165Mapping file id17165 NCBI fileEvidenceIEA
GeneMbtps1Authority56453Mapping file id56453 NCBI fileEvidenceIEA
GeneMbtps2Authority270669Mapping file id270669 NCBI fileEvidenceIEA
GeneMdm2Authority17246Mapping file id17246 NCBI fileEvidenceIEA
GeneMdm4Authority17248Mapping file id17248 NCBI fileEvidenceIEA
GeneMed1Authority19014Mapping file id19014 NCBI fileEvidenceIEA
GeneMink1Authority50932Mapping file id50932 NCBI fileEvidenceIEA
GeneMiosAuthority252875Mapping file id252875 NCBI fileEvidenceIEA
GeneMlst8Authority56716Mapping file id56716 NCBI fileEvidenceIEA
GeneMre11aAuthority17535Mapping file id17535 NCBI fileEvidenceIEA
GeneMt2Authority17750Mapping file id17750 NCBI fileEvidenceIEA
GeneMt3Authority17751Mapping file id17751 NCBI fileEvidenceIEA
GeneMtorAuthority56717Mapping file id56717 NCBI fileEvidenceIEA
GeneMul1Authority68350Mapping file id68350 NCBI fileEvidenceIEA
GeneNbnAuthority27354Mapping file id27354 NCBI fileEvidenceIEA
GeneNcf1Authority17969Mapping file id17969 NCBI fileEvidenceIEA
GeneNcf2Authority17970Mapping file id17970 NCBI fileEvidenceIEA
GeneNcf4Authority17972Mapping file id17972 NCBI fileEvidenceIEA
GeneNcoa1Authority17977Mapping file id17977 NCBI fileEvidenceIEA
GeneNcoa2Authority17978Mapping file id17978 NCBI fileEvidenceIEA
GeneNcor2Authority20602Mapping file id20602 NCBI fileEvidenceIEA
GeneNdc1Authority72787Mapping file id72787 NCBI fileEvidenceIEA
GeneNfe2l2Authority18024Mapping file id18024 NCBI fileEvidenceIEA
GeneNfkb1Authority18033Mapping file id18033 NCBI fileEvidenceIEA
GeneNfkbiaAuthority18035Mapping file id18035 NCBI fileEvidenceIEA
GeneNos3Authority18127Mapping file id18127 NCBI fileEvidenceIEA
GeneNox4Authority50490Mapping file id50490 NCBI fileEvidenceIEA
GeneNploc4Authority217365Mapping file id217365 NCBI fileEvidenceIEA
GeneNprl2Authority56032Mapping file id56032 NCBI fileEvidenceIEA
GeneNprl3Authority17168Mapping file id17168 NCBI fileEvidenceIEA
GeneNr3c1Authority14815Mapping file id14815 NCBI fileEvidenceIEA
GeneNr3c2Authority110784Mapping file idENSMUSG00000031618 Ensembl fileEvidenceIEA
GeneNudt2Authority66401Mapping file id66401 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

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.