Skip to content
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.

Signaling by Nuclear Receptors

R-MMU-9006931 in Reactome release 97: under Signal Transduction, with 218 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-9006931 (human), R-RNO-9006931 (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 218 genes in this mouse pathway; showing 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 3
GeneH2bc6Authority319179Mapping file id319179 NCBI fileEvidenceIEA
GeneH2bc7Authority319180Mapping file id319180 NCBI fileEvidenceIEA
GeneH2bc8Authority319181Mapping file id319181 NCBI fileEvidenceIEA
GeneH2bc9Authority319182Mapping file id319182 NCBI fileEvidenceIEA
GeneH3c1Authority360198Mapping file id360198 NCBI fileEvidenceIEA
GeneH3c10Authority319152Mapping file id319152 NCBI fileEvidenceIEA
GeneH3c11Authority319153Mapping file id319153 NCBI fileEvidenceIEA
GeneH3c13Authority319154Mapping file id319154 NCBI fileEvidenceIEA
GeneH3c14Authority15077Mapping file id15077 NCBI fileEvidenceIEA
GeneH3c15Authority97114Mapping file id97114 NCBI fileEvidenceIEA
GeneH3c2Authority319150Mapping file id319150 NCBI fileEvidenceIEA
GeneH3c3Authority319148Mapping file id319148 NCBI fileEvidenceIEA
GeneH3c4Authority319149Mapping file id319149 NCBI fileEvidenceIEA
GeneH3c6Authority319151Mapping file id319151 NCBI fileEvidenceIEA
GeneH3c7Authority260423Mapping file id260423 NCBI fileEvidenceIEA
GeneH3c8Authority97908Mapping file id97908 NCBI fileEvidenceIEA
GeneH3f3aAuthority15078Mapping file id15078 NCBI fileEvidenceIEA
GeneH3f3bAuthority15081Mapping file id15081 NCBI fileEvidenceIEA
GeneH4c1Authority326619Mapping file id326619 NCBI fileEvidenceIEA
GeneH4c11Authority319159Mapping file id319159 NCBI fileEvidenceIEA
GeneH4c12Authority319160Mapping file id319160 NCBI fileEvidenceIEA
GeneH4c14Authority97122Mapping file id97122 NCBI fileEvidenceIEA
GeneH4c16Authority320332Mapping file id320332 NCBI fileEvidenceIEA
GeneH4c17Authority100041230Mapping file id100041230 NCBI fileEvidenceIEA
GeneH4c18Authority319161Mapping file id319161 NCBI fileEvidenceIEA
GeneH4c2Authority326620Mapping file id326620 NCBI fileEvidenceIEA
GeneH4c3Authority319155Mapping file id319155 NCBI fileEvidenceIEA
GeneH4c4Authority319156Mapping file id319156 NCBI fileEvidenceIEA
GeneH4c6Authority319157Mapping file id319157 NCBI fileEvidenceIEA
GeneH4c8Authority69386Mapping file id69386 NCBI fileEvidenceIEA
GeneH4c9Authority319158Mapping file id319158 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHdac3Authority15183Mapping file id15183 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneHsp90ab1Authority15516Mapping file id15516 NCBI fileEvidenceIEA
GeneHspb1Authority15507Mapping file id15507 NCBI fileEvidenceIEA
GeneIgf1rAuthority16001Mapping file id16001 NCBI fileEvidenceIEA
GeneKat2bAuthority18519Mapping file id18519 NCBI fileEvidenceIEA
GeneKat5Authority81601Mapping file id81601 NCBI fileEvidenceIEA
GeneKdm1aAuthority99982Mapping file id99982 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMed1Authority19014Mapping file id19014 NCBI fileEvidenceIEA
GeneMmp2Authority17390Mapping file id17390 NCBI fileEvidenceIEA
GeneMmp3Authority17392Mapping file id17392 NCBI fileEvidenceIEA
GeneMmp7Authority17393Mapping file id17393 NCBI fileEvidenceIEA
GeneMmp9Authority17395Mapping file id17395 NCBI fileEvidenceIEA
GeneNcoa1Authority17977Mapping file id17977 NCBI fileEvidenceIEA
GeneNcoa2Authority17978Mapping file id17978 NCBI fileEvidenceIEA
GeneNcor2Authority20602Mapping file id20602 NCBI fileEvidenceIEA
GeneNos3Authority18127Mapping file id18127 NCBI fileEvidenceIEA
GeneNr1h2Authority22260Mapping file id22260 NCBI fileEvidenceIEA
GeneNr1h3Authority22259Mapping file id22259 NCBI fileEvidenceIEA
GeneNrip1Authority268903Mapping file id268903 NCBI fileEvidenceIEA
GenePdha1Authority18597Mapping file id18597 NCBI fileEvidenceIEA
GenePdha2Authority18598Mapping file id18598 NCBI fileEvidenceIEA
GenePdhbAuthority68263Mapping file id68263 NCBI fileEvidenceIEA
GenePdhxAuthority27402Mapping file id27402 NCBI fileEvidenceIEA
GenePdk1Authority228026Mapping file id228026 NCBI fileEvidenceIEA
GenePdk2Authority18604Mapping file id18604 NCBI fileEvidenceIEA
GenePdk3Authority236900Mapping file id236900 NCBI fileEvidenceIEA
GenePdk4Authority27273Mapping file id27273 NCBI fileEvidenceIEA
GenePdpk1Authority18607Mapping file id18607 NCBI fileEvidenceIEA
GenePgrAuthority18667Mapping file id18667 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePolr2aAuthority20020Mapping file id20020 NCBI fileEvidenceIEA
GenePolr2bAuthority231329Mapping file id231329 NCBI fileEvidenceIEA
GenePolr2cAuthority20021Mapping file id20021 NCBI fileEvidenceIEA
GenePolr2dAuthority69241Mapping file id69241 NCBI fileEvidenceIEA
GenePolr2eAuthority66420Mapping file id66420 NCBI fileEvidenceIEA
GenePolr2fAuthority69833Mapping file id69833 NCBI fileEvidenceIEA
GenePolr2gAuthority67710Mapping file id67710 NCBI fileEvidenceIEA
GenePolr2hAuthority245841Mapping file id245841 NCBI fileEvidenceIEA
GenePolr2iAuthority69920Mapping file id69920 NCBI fileEvidenceIEA
GenePolr2kAuthority17749Mapping file id17749 NCBI fileEvidenceIEA
GenePolr2lAuthority66491Mapping file id66491 NCBI fileEvidenceIEA
GenePpardAuthority19015Mapping file id19015 NCBI fileEvidenceIEA
GenePpidAuthority67738Mapping file id67738 NCBI fileEvidenceIEA
GenePpp5cAuthority19060Mapping file id19060 NCBI fileEvidenceIEA
GenePrkczAuthority18762Mapping file id18762 NCBI fileEvidenceIEA
GenePrmt1Authority15469Mapping file id15469 NCBI fileEvidenceIEA
GenePtges3Authority56351Mapping file id56351 NCBI fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GeneRaraAuthority19401Mapping file id19401 NCBI fileEvidenceIEA
GeneRarbAuthority218772Mapping file id218772 NCBI fileEvidenceIEA
GeneRargAuthority19411Mapping file id19411 NCBI fileEvidenceIEA
GeneRdh1Authority107605Mapping file id107605 NCBI fileEvidenceIEA
GeneRdh10Authority98711Mapping file id98711 NCBI fileEvidenceIEA
GeneRdh11Authority17252Mapping file id17252 NCBI fileEvidenceIEA
GeneRdh13Authority108841Mapping file id108841 NCBI fileEvidenceIEA
GeneRdh14Authority105014Mapping file id105014 NCBI fileEvidenceIEA
GeneRdh5Authority19682Mapping file id19682 NCBI fileEvidenceIEA
GeneRxraAuthority20181Mapping file id20181 NCBI fileEvidenceIEA
GeneRxrbAuthority20182Mapping file id20182 NCBI fileEvidenceIEA
GeneRxrgAuthority20183Mapping file id20183 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.