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 201 to 300, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 3 of 5
GeneJak3Authority16453Mapping file id16453 NCBI fileEvidenceIEA
GeneJupAuthority16480Mapping file id16480 NCBI fileEvidenceIEA
GeneKdrAuthority16542Mapping file id16542 NCBI fileEvidenceIEA
GeneKidins220Authority77480Mapping file id77480 NCBI fileEvidenceIEA
GeneKitAuthority16590Mapping file id16590 NCBI fileEvidenceIEA
GeneKitlAuthority17311Mapping file id17311 NCBI fileEvidenceIEA
GeneKlAuthority16591Mapping file id16591 NCBI fileEvidenceIEA
GeneKlbAuthority83379Mapping file id83379 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneLama4Authority16775Mapping file id16775 NCBI fileEvidenceIEA
GeneLckAuthority16818Mapping file id16818 NCBI fileEvidenceIEA
GeneLrig1Authority16206Mapping file id16206 NCBI fileEvidenceIEA
GeneLtkAuthority17005Mapping file id17005 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 NCBI fileEvidenceIEA
GeneMap2k1Authority26395Mapping file id26395 NCBI fileEvidenceIEA
GeneMap2k2Authority26396Mapping file id26396 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
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMapkap1Authority227743Mapping file id227743 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneMatkAuthority17179Mapping file id17179 NCBI fileEvidenceIEA
GeneMdkAuthority17242Mapping file id17242 NCBI fileEvidenceIEA
GeneMegf11Authority214058Mapping file id214058 NCBI fileEvidenceIEA
GeneMemo1Authority76890Mapping file id76890 NCBI fileEvidenceIEA
GeneMetAuthority17295Mapping file idENSMUSG00000009376 Ensembl fileEvidenceIEA
GeneMknk1Authority17346Mapping file id17346 NCBI fileEvidenceIEA
GeneMlst8Authority56716Mapping file id56716 NCBI fileEvidenceIEA
GeneMmp9Authority17395Mapping file id17395 NCBI fileEvidenceIEA
GeneMst1Authority15235Mapping file id15235 NCBI fileEvidenceIEA
GeneMst1rAuthority19882Mapping file id19882 NCBI fileEvidenceIEA
GeneMtorAuthority56717Mapping file id56717 NCBI fileEvidenceIEA
GeneMuc20Authority224116Mapping file id224116 NCBI fileEvidenceIEA
GeneNab2Authority17937Mapping file id17937 NCBI fileEvidenceIEA
GeneNcbp1Authority433702Mapping file id433702 NCBI fileEvidenceIEA
GeneNcbp2Authority68092Mapping file id68092 NCBI fileEvidenceIEA
GeneNcf1Authority17969Mapping file id17969 NCBI fileEvidenceIEA
GeneNcf2Authority17970Mapping file id17970 NCBI fileEvidenceIEA
GeneNcf4Authority17972Mapping file id17972 NCBI fileEvidenceIEA
GeneNck1Authority17973Mapping file id17973 NCBI fileEvidenceIEA
GeneNck2Authority17974Mapping file id17974 NCBI fileEvidenceIEA
GeneNckap1Authority50884Mapping file id50884 NCBI fileEvidenceIEA
GeneNckap1lAuthority105855Mapping file id105855 NCBI fileEvidenceIEA
GeneNcstnAuthority59287Mapping file id59287 NCBI fileEvidenceIEA
GeneNedd4Authority17999Mapping file id17999 NCBI fileEvidenceIEA
GeneNgfAuthority18049Mapping file id18049 NCBI fileEvidenceIEA
GeneNos3Authority18127Mapping file id18127 NCBI fileEvidenceIEA
GeneNrg1Authority211323Mapping file id211323 NCBI fileEvidenceIEA
GeneNrg3Authority18183Mapping file id18183 NCBI fileEvidenceIEA
GeneNrp1Authority18186Mapping file id18186 NCBI fileEvidenceIEA
GeneNrp2Authority18187Mapping file id18187 NCBI fileEvidenceIEA
GeneNtf3Authority18205Mapping file id18205 NCBI fileEvidenceIEA
GeneNtf5Authority78405Mapping file id78405 NCBI fileEvidenceIEA
GeneNtrk1Authority18211Mapping file id18211 NCBI fileEvidenceIEA
GeneNtrk2Authority18212Mapping file id18212 NCBI fileEvidenceIEA
GeneNtrk3Authority18213Mapping file id18213 NCBI fileEvidenceIEA
GenePag1Authority94212Mapping file id94212 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GenePak2Authority224105Mapping file id224105 NCBI fileEvidenceIEA
GenePak3Authority18481Mapping file id18481 NCBI fileEvidenceIEA
GenePcsk5Authority18552Mapping file id18552 NCBI fileEvidenceIEA
GenePcsk6Authority18553Mapping file id18553 NCBI fileEvidenceIEA
GenePde3bAuthority18576Mapping file id18576 NCBI fileEvidenceIEA
GenePdgfaAuthority18590Mapping file id18590 NCBI fileEvidenceIEA
GenePdgfbAuthority18591Mapping file id18591 NCBI fileEvidenceIEA
GenePdgfcAuthority54635Mapping file id54635 NCBI fileEvidenceIEA
GenePdgfdAuthority71785Mapping file id71785 NCBI fileEvidenceIEA
GenePdgfraAuthority18595Mapping file id18595 NCBI fileEvidenceIEA
GenePdgfrbAuthority18596Mapping file id18596 NCBI fileEvidenceIEA
GenePdpk1Authority18607Mapping file id18607 NCBI fileEvidenceIEA
GenePgfAuthority18654Mapping file id18654 NCBI fileEvidenceIEA
GenePik3c3Authority225326Mapping file id225326 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3cbAuthority74769Mapping file id74769 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePik3r4Authority75669Mapping file id75669 NCBI fileEvidenceIEA
GenePlatAuthority18791Mapping file id18791 NCBI fileEvidenceIEA
GenePlcg1Authority18803Mapping file id18803 NCBI fileEvidenceIEA
GenePlgAuthority18815Mapping file id18815 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
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 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.