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.

Signal Transduction

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

Genes Reactome places in this mouse pathway, page 12 of 23
GeneKitAuthority16590Mapping file id16590 NCBI fileEvidenceIEA
GeneKitlAuthority17311Mapping file id17311 NCBI fileEvidenceIEA
GeneKlAuthority16591Mapping file id16591 NCBI fileEvidenceIEA
GeneKlbAuthority83379Mapping file id83379 NCBI fileEvidenceIEA
GeneKlc1Authority16593Mapping file idENSMUSG00000021288 Ensembl fileEvidenceIEA
GeneKlc2Authority16594Mapping file idENSMUSG00000024862 Ensembl fileEvidenceIEA
GeneKlc3Authority232943Mapping file id232943 NCBI fileEvidenceIEA
GeneKlc4Authority74764Mapping file id74764 NCBI fileEvidenceIEA
GeneKlhl12Authority240756Mapping file id240756 NCBI fileEvidenceIEA
GeneKmt2bAuthority75410Mapping file id75410 NCBI fileEvidenceIEA
GeneKng2Authority385643Mapping file id385643 NCBI fileEvidenceIEA
GeneKntc1Authority208628Mapping file id208628 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneKremen1Authority84035Mapping file id84035 NCBI fileEvidenceIEA
GeneKremen2Authority73016Mapping file id73016 NCBI fileEvidenceIEA
GeneKsr1Authority16706Mapping file id16706 NCBI fileEvidenceIEA
GeneKsr2Authority333050Mapping file id333050 NCBI fileEvidenceIEA
GeneKtn1Authority16709Mapping file id16709 NCBI fileEvidenceIEA
GeneLama4Authority16775Mapping file id16775 NCBI 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
GeneLatAuthority16797Mapping file id16797 NCBI fileEvidenceIEA
GeneLats1Authority16798Mapping file id16798 NCBI fileEvidenceIEA
GeneLats2Authority50523Mapping file id50523 NCBI fileEvidenceIEA
GeneLbrAuthority98386Mapping file id98386 NCBI fileEvidenceIEA
GeneLckAuthority16818Mapping file id16818 NCBI fileEvidenceIEA
GeneLef1Authority16842Mapping file id16842 NCBI fileEvidenceIEA
GeneLeo1Authority235497Mapping file id235497 NCBI fileEvidenceIEA
GeneLetm1Authority56384Mapping file id56384 NCBI fileEvidenceIEA
GeneLgr5Authority14160Mapping file id14160 NCBI fileEvidenceIEA
GeneLhcgrAuthority16867Mapping file id16867 NCBI fileEvidenceIEA
GeneLimk1Authority16885Mapping file id16885 NCBI fileEvidenceIEA
GeneLin7bAuthority22342Mapping file id22342 NCBI fileEvidenceIEA
GeneLingo1Authority235402Mapping file id235402 NCBI fileEvidenceIEA
GeneLman1Authority70361Mapping file id70361 NCBI fileEvidenceIEA
GeneLmnb1Authority16906Mapping file id16906 NCBI fileEvidenceIEA
GeneLpar1Authority14745Mapping file id14745 NCBI fileEvidenceIEA
GeneLpar2Authority53978Mapping file id53978 NCBI fileEvidenceIEA
GeneLpar3Authority65086Mapping file id65086 NCBI fileEvidenceIEA
GeneLpar4Authority78134Mapping file id78134 NCBI fileEvidenceIEA
GeneLpar5Authority381810Mapping file id381810 NCBI fileEvidenceIEA
GeneLpar6Authority67168Mapping file id67168 NCBI fileEvidenceIEA
GeneLrig1Authority16206Mapping file id16206 NCBI fileEvidenceIEA
GeneLrp5Authority16973Mapping file id16973 NCBI fileEvidenceIEA
GeneLrp6Authority16974Mapping file id16974 NCBI fileEvidenceIEA
GeneLrrc1Authority214345Mapping file id214345 NCBI fileEvidenceIEA
GeneLrrc41Authority230654Mapping file id230654 NCBI fileEvidenceIEA
GeneLrrc7Authority242274Mapping file id242274 NCBI fileEvidenceIEA
GeneLrrk2Authority66725Mapping file id66725 NCBI fileEvidenceIEA
GeneLtb4r1Authority16995Mapping file id16995 NCBI fileEvidenceIEA
GeneLtb4r2Authority57260Mapping file id57260 NCBI fileEvidenceIEA
GeneLtbp1Authority268977Mapping file id268977 NCBI fileEvidenceIEA
GeneLtbp2Authority16997Mapping file id16997 NCBI fileEvidenceIEA
GeneLtbp3Authority16998Mapping file id16998 NCBI fileEvidenceIEA
GeneLtbp4Authority108075Mapping file id108075 NCBI fileEvidenceIEA
GeneLtkAuthority17005Mapping file id17005 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 NCBI fileEvidenceIEA
GeneLypla1Authority18777Mapping file id18777 NCBI fileEvidenceIEA
GeneMaco1Authority66146Mapping file id66146 NCBI fileEvidenceIEA
GeneMad1l1Authority17120Mapping file id17120 NCBI fileEvidenceIEA
GeneMad2l1Authority56150Mapping file id56150 NCBI fileEvidenceIEA
GeneMaddAuthority228355Mapping file id228355 NCBI fileEvidenceIEA
GeneMaf1Authority68877Mapping file id68877 NCBI fileEvidenceIEA
GeneMagAuthority17136Mapping file id17136 NCBI fileEvidenceIEA
GeneMaml1Authority103806Mapping file id103806 NCBI fileEvidenceIEA
GeneMaml2Authority270118Mapping file id270118 NCBI fileEvidenceIEA
GeneMaml3Authority433586Mapping file id433586 NCBI fileEvidenceIEA
GeneMamld1Authority333639Mapping file id333639 NCBI fileEvidenceIEA
GeneMap2k1Authority26395Mapping file id26395 NCBI fileEvidenceIEA
GeneMap2k2Authority26396Mapping file id26396 NCBI fileEvidenceIEA
GeneMap3k11Authority26403Mapping file id26403 NCBI fileEvidenceIEA
GeneMap3k7Authority26409Mapping file id26409 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk12Authority29857Mapping file id29857 NCBI fileEvidenceIEA
GeneMapk13Authority26415Mapping file id26415 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk4Authority225724Mapping file id225724 NCBI fileEvidenceIEA
GeneMapk6Authority50772Mapping file id50772 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMapk8Authority26419Mapping file id26419 NCBI fileEvidenceIEA
GeneMapkap1Authority227743Mapping file id227743 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneMapkapk5Authority17165Mapping file id17165 NCBI fileEvidenceIEA
GeneMapre1Authority13589Mapping file id13589 NCBI fileEvidenceIEA
GeneMark3Authority17169Mapping file id17169 NCBI fileEvidenceIEA
GeneMatkAuthority17179Mapping file id17179 NCBI fileEvidenceIEA
GeneMbd3Authority17192Mapping file id17192 NCBI fileEvidenceIEA
GeneMc1rAuthority17199Mapping file id17199 NCBI fileEvidenceIEA
GeneMc2rAuthority17200Mapping file id17200 NCBI fileEvidenceIEA
GeneMc3rAuthority17201Mapping file id17201 NCBI fileEvidenceIEA
GeneMc4rAuthority17202Mapping file id17202 NCBI fileEvidenceIEA
GeneMc5rAuthority17203Mapping file id17203 NCBI fileEvidenceIEA
GeneMcamAuthority84004Mapping file id84004 NCBI fileEvidenceIEA
GeneMcf2Authority109904Mapping file id109904 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.