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.

Signaling by Receptor Tyrosine Kinases

R-MMU-9006934 in Reactome release 97: under Signal Transduction, with 419 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-9006934 (human), R-RNO-9006934 (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 419 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 5
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneDock7Authority67299Mapping file idENSMUSG00000028556 Ensembl fileEvidenceIEA
GeneDusp3Authority72349Mapping file id72349 NCBI fileEvidenceIEA
GeneDusp4Authority319520Mapping file id319520 NCBI fileEvidenceIEA
GeneDusp6Authority67603Mapping file id67603 NCBI fileEvidenceIEA
GeneDusp7Authority235584Mapping file id235584 NCBI fileEvidenceIEA
GeneEgfAuthority13645Mapping file id13645 NCBI fileEvidenceIEA
GeneEgfrAuthority13649Mapping file id13649 NCBI fileEvidenceIEA
GeneEgr2Authority13654Mapping file id13654 NCBI fileEvidenceIEA
GeneElmo1Authority140580Mapping file id140580 NCBI fileEvidenceIEA
GeneElmo2Authority140579Mapping file id140579 NCBI fileEvidenceIEA
GeneEp300Authority328572Mapping file id328572 NCBI fileEvidenceIEA
GeneEpgnAuthority71920Mapping file id71920 NCBI fileEvidenceIEA
GeneEpn1Authority13854Mapping file id13854 NCBI fileEvidenceIEA
GeneEps15Authority13858Mapping file id13858 NCBI fileEvidenceIEA
GeneEps15l1Authority13859Mapping file id13859 NCBI fileEvidenceIEA
GeneErbb2Authority13866Mapping file id13866 NCBI fileEvidenceIEA
GeneErbb3Authority13867Mapping file id13867 NCBI fileEvidenceIEA
GeneErbb4Authority13869Mapping file id13869 NCBI fileEvidenceIEA
GeneErbinAuthority59079Mapping file id59079 NCBI fileEvidenceIEA
GeneEregAuthority13874Mapping file id13874 NCBI fileEvidenceIEA
GeneEsr1Authority13982Mapping file id13982 NCBI fileEvidenceIEA
GeneFerAuthority14158Mapping file id14158 NCBI fileEvidenceIEA
GeneFesAuthority14159Mapping file id14159 NCBI fileEvidenceIEA
GeneFgf1Authority14164Mapping file id14164 NCBI fileEvidenceIEA
GeneFgf10Authority14165Mapping file id14165 NCBI fileEvidenceIEA
GeneFgf15Authority14170Mapping file id14170 NCBI fileEvidenceIEA
GeneFgf16Authority80903Mapping file id80903 NCBI fileEvidenceIEA
GeneFgf17Authority14171Mapping file id14171 NCBI fileEvidenceIEA
GeneFgf18Authority14172Mapping file id14172 NCBI fileEvidenceIEA
GeneFgf2Authority14173Mapping file id14173 NCBI fileEvidenceIEA
GeneFgf20Authority80857Mapping file id80857 NCBI fileEvidenceIEA
GeneFgf22Authority67112Mapping file id67112 NCBI fileEvidenceIEA
GeneFgf23Authority64654Mapping file id64654 NCBI fileEvidenceIEA
GeneFgf3Authority14174Mapping file idENSMUSG00000031074 Ensembl fileEvidenceIEA
GeneFgf4Authority14175Mapping file id14175 NCBI fileEvidenceIEA
GeneFgf5Authority14176Mapping file id14176 NCBI fileEvidenceIEA
GeneFgf6Authority14177Mapping file id14177 NCBI fileEvidenceIEA
GeneFgf7Authority14178Mapping file id14178 NCBI fileEvidenceIEA
GeneFgf8Authority14179Mapping file id14179 NCBI fileEvidenceIEA
GeneFgf9Authority14180Mapping file id14180 NCBI fileEvidenceIEA
GeneFgfbp1Authority14181Mapping file id14181 NCBI fileEvidenceIEA
GeneFgfbp3Authority72514Mapping file id72514 NCBI fileEvidenceIEA
GeneFgfr1Authority14182Mapping file id14182 NCBI fileEvidenceIEA
GeneFgfr2Authority14183Mapping file id14183 NCBI fileEvidenceIEA
GeneFgfr3Authority14184Mapping file idENSMUSG00000054252 Ensembl fileEvidenceIEA
GeneFgfr4Authority14186Mapping file id14186 NCBI fileEvidenceIEA
GeneFgfrl1Authority116701Mapping file id116701 NCBI fileEvidenceIEA
GeneFlrt1Authority396184Mapping file id396184 NCBI fileEvidenceIEA
GeneFlrt2Authority399558Mapping file id399558 NCBI fileEvidenceIEA
GeneFlrt3Authority71436Mapping file id71436 NCBI fileEvidenceIEA
GeneFlt1Authority14254Mapping file id14254 NCBI fileEvidenceIEA
GeneFlt3Authority14255Mapping file id14255 NCBI fileEvidenceIEA
GeneFlt3lAuthority14256Mapping file id14256 NCBI fileEvidenceIEA
GeneFlt4Authority14257Mapping file id14257 NCBI fileEvidenceIEA
GeneFn1Authority14268Mapping file id14268 NCBI fileEvidenceIEA
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFrs3Authority107971Mapping file id107971 NCBI fileEvidenceIEA
GeneFurinAuthority18550Mapping file id18550 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneGab1Authority14388Mapping file id14388 NCBI fileEvidenceIEA
GeneGalnt3Authority14425Mapping file id14425 NCBI fileEvidenceIEA
GeneGga3Authority260302Mapping file id260302 NCBI fileEvidenceIEA
GeneGipc1Authority67903Mapping file id67903 NCBI fileEvidenceIEA
GeneGrapAuthority71520Mapping file id71520 NCBI fileEvidenceIEA
GeneGrap2Authority17444Mapping file id17444 NCBI fileEvidenceIEA
GeneGrb10Authority14783Mapping file id14783 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrb7Authority14786Mapping file id14786 NCBI fileEvidenceIEA
GeneGtf2f1Authority98053Mapping file id98053 NCBI fileEvidenceIEA
GeneGtf2f2Authority68705Mapping file id68705 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHdac1Authority433759Mapping file id433759 NCBI fileEvidenceIEA
GeneHdac2Authority15182Mapping file id15182 NCBI fileEvidenceIEA
GeneHdac3Authority15183Mapping file id15183 NCBI fileEvidenceIEA
GeneHgfAuthority15234Mapping file id15234 NCBI fileEvidenceIEA
GeneHgfacAuthority54426Mapping file id54426 NCBI fileEvidenceIEA
GeneHgsAuthority15239Mapping file id15239 NCBI fileEvidenceIEA
GeneHnrnpa1Authority15382Mapping file id15382 NCBI fileEvidenceIEA
GeneHpnAuthority15451Mapping file id15451 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneHspb1Authority15507Mapping file id15507 NCBI fileEvidenceIEA
GeneIdeAuthority15925Mapping file idENSMUSG00000056999 Ensembl fileEvidenceIEA
GeneIgf1Authority16000Mapping file id16000 NCBI fileEvidenceIEA
GeneIgf1rAuthority16001Mapping file id16001 NCBI fileEvidenceIEA
GeneIgf2Authority16002Mapping file id16002 NCBI fileEvidenceIEA
GeneIns1Authority16333Mapping file id16333 NCBI fileEvidenceIEA
GeneIns2Authority16334Mapping file id16334 NCBI fileEvidenceIEA
GeneInsrAuthority16337Mapping file id16337 NCBI fileEvidenceIEA
GeneIrs1Authority16367Mapping file id16367 NCBI fileEvidenceIEA
GeneIrs2Authority384783Mapping file id384783 NCBI fileEvidenceIEA
GeneIrs4Authority16370Mapping file id16370 NCBI fileEvidenceIEA
GeneItchAuthority16396Mapping file id16396 NCBI fileEvidenceIEA
GeneItga2Authority16398Mapping file id16398 NCBI fileEvidenceIEA
GeneItga3Authority16400Mapping file id16400 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneJak2Authority16452Mapping file id16452 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.