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 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 5
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkacbAuthority18749Mapping file id18749 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GenePrkcbAuthority18751Mapping file id18751 NCBI fileEvidenceIEA
GenePrkcdAuthority18753Mapping file id18753 NCBI fileEvidenceIEA
GenePrkceAuthority18754Mapping file id18754 NCBI fileEvidenceIEA
GenePrkczAuthority18762Mapping file id18762 NCBI fileEvidenceIEA
GenePrr5Authority109270Mapping file id109270 NCBI fileEvidenceIEA
GenePsen1Authority19164Mapping file id19164 NCBI fileEvidenceIEA
GenePsen2Authority19165Mapping file id19165 NCBI fileEvidenceIEA
GenePsenenAuthority66340Mapping file id66340 NCBI fileEvidenceIEA
GenePtbp1Authority19205Mapping file id19205 NCBI fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GenePtk2bAuthority19229Mapping file id19229 NCBI fileEvidenceIEA
GenePtk6Authority20459Mapping file id20459 NCBI fileEvidenceIEA
GenePtnAuthority19242Mapping file id19242 NCBI fileEvidenceIEA
GenePtpn1Authority19246Mapping file id19246 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GenePtpn12Authority19248Mapping file id19248 NCBI fileEvidenceIEA
GenePtpn18Authority19253Mapping file id19253 NCBI fileEvidenceIEA
GenePtpn2Authority19255Mapping file id19255 NCBI fileEvidenceIEA
GenePtpn3Authority545622Mapping file id545622 NCBI fileEvidenceIEA
GenePtpn6Authority15170Mapping file id15170 NCBI fileEvidenceIEA
GenePtprfAuthority19268Mapping file id19268 NCBI fileEvidenceIEA
GenePtprjAuthority19271Mapping file id19271 NCBI fileEvidenceIEA
GenePtprkAuthority19272Mapping file id19272 NCBI fileEvidenceIEA
GenePtpruAuthority19273Mapping file id19273 NCBI fileEvidenceIEA
GenePtprz1Authority19283Mapping file id19283 NCBI fileEvidenceIEA
GenePxnAuthority19303Mapping file id19303 NCBI fileEvidenceIEA
GeneRab4aAuthority19341Mapping file id19341 NCBI fileEvidenceIEA
GeneRab4bAuthority19342Mapping file id19342 NCBI fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 NCBI fileEvidenceIEA
GeneRalgdsAuthority19730Mapping file id19730 NCBI fileEvidenceIEA
GeneRanbp10Authority74334Mapping file id74334 NCBI fileEvidenceIEA
GeneRanbp9Authority56705Mapping file id56705 NCBI fileEvidenceIEA
GeneRap1aAuthority109905Mapping file id109905 NCBI fileEvidenceIEA
GeneRap1bAuthority215449Mapping file id215449 NCBI fileEvidenceIEA
GeneRapgef1Authority107746Mapping file id107746 NCBI fileEvidenceIEA
GeneRasa1Authority218397Mapping file id218397 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRictorAuthority78757Mapping file id78757 NCBI fileEvidenceIEA
GeneRnf41Authority67588Mapping file id67588 NCBI fileEvidenceIEA
GeneRock1Authority19877Mapping file id19877 NCBI fileEvidenceIEA
GeneRock2Authority19878Mapping file id19878 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRps6ka1Authority20111Mapping file id20111 NCBI fileEvidenceIEA
GeneRps6ka2Authority20112Mapping file id20112 NCBI fileEvidenceIEA
GeneRps6ka3Authority110651Mapping file id110651 NCBI fileEvidenceIEA
GeneRps6ka5Authority73086Mapping file id73086 NCBI fileEvidenceIEA
GeneSack1aAuthority239463Mapping file id239463 NCBI fileEvidenceIEA
GeneSack1bAuthority208994Mapping file id208994 NCBI fileEvidenceIEA
GeneSack1dAuthority71878Mapping file id71878 NCBI fileEvidenceIEA
GeneSgk1Authority20393Mapping file id20393 NCBI fileEvidenceIEA
GeneSh2b2Authority23921Mapping file id23921 NCBI fileEvidenceIEA
GeneSh2b3Authority16923Mapping file id16923 NCBI fileEvidenceIEA
GeneSh2d2aAuthority27371Mapping file id27371 NCBI fileEvidenceIEA
GeneSh3gl1Authority20405Mapping file id20405 NCBI fileEvidenceIEA
GeneSh3gl2Authority20404Mapping file id20404 NCBI fileEvidenceIEA
GeneSh3gl3Authority20408Mapping file id20408 NCBI fileEvidenceIEA
GeneSh3kbp1Authority58194Mapping file id58194 NCBI fileEvidenceIEA
GeneShbAuthority230126Mapping file id230126 NCBI fileEvidenceIEA
GeneShc1Authority20416Mapping file id20416 NCBI fileEvidenceIEA
GeneShc2Authority216148Mapping file id216148 NCBI fileEvidenceIEA
GeneShc3Authority20418Mapping file id20418 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneSphk1Authority20698Mapping file id20698 NCBI fileEvidenceIEA
GeneSpint1Authority20732Mapping file id20732 NCBI fileEvidenceIEA
GeneSpint2Authority20733Mapping file id20733 NCBI fileEvidenceIEA
GeneSpp1Authority20750Mapping file id20750 NCBI fileEvidenceIEA
GeneSpred1Authority114715Mapping file id114715 NCBI fileEvidenceIEA
GeneSpred2Authority114716Mapping file id114716 NCBI fileEvidenceIEA
GeneSpry1Authority24063Mapping file id24063 NCBI fileEvidenceIEA
GeneSpry2Authority24064Mapping file id24064 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneSrfAuthority20807Mapping file id20807 NCBI fileEvidenceIEA
GeneStamAuthority20844Mapping file id20844 NCBI fileEvidenceIEA
GeneStam2Authority56324Mapping file id56324 NCBI fileEvidenceIEA
GeneStat3Authority20848Mapping file id20848 NCBI fileEvidenceIEA
GeneStat5aAuthority20850Mapping file id20850 NCBI fileEvidenceIEA
GeneStat5bAuthority20851Mapping file id20851 NCBI fileEvidenceIEA
GeneStat6Authority20852Mapping file id20852 NCBI fileEvidenceIEA
GeneStub1Authority56424Mapping file id56424 NCBI fileEvidenceIEA
GeneTcirg1Authority27060Mapping file id27060 NCBI fileEvidenceIEA
GeneTecAuthority21682Mapping file id21682 NCBI fileEvidenceIEA
GeneTgfaAuthority21802Mapping file id21802 NCBI fileEvidenceIEA
GeneTgfbr3Authority21814Mapping file id21814 NCBI fileEvidenceIEA
GeneThbs1Authority21825Mapping file idENSMUSG00000040152 Ensembl fileEvidenceIEA
GeneThbs2Authority21826Mapping file id21826 NCBI fileEvidenceIEA
GeneThbs3Authority21827Mapping file id21827 NCBI fileEvidenceIEA
GeneThbs4Authority21828Mapping file id21828 NCBI fileEvidenceIEA
GeneThem4Authority75778Mapping file id75778 NCBI fileEvidenceIEA
GeneTlr9Authority81897Mapping file id81897 NCBI fileEvidenceIEA
GeneTnk2Authority51789Mapping file id51789 NCBI fileEvidenceIEA
GeneTns3Authority319939Mapping file id319939 NCBI fileEvidenceIEA
GeneTns4Authority217169Mapping file id217169 NCBI fileEvidenceIEA
GeneTrib3Authority228775Mapping file id228775 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl 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.