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 MET

R-MMU-6806834 in Reactome release 97: under Signaling by Receptor Tyrosine Kinases, with 68 genes placed in it by the mapping files and 8 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-6806834 (human), R-RNO-6806834 (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 68 genes in this mouse pathway; showing 1 to 68, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneArf6Authority11845Mapping file id11845 NCBI fileEvidenceIEA
GeneCblAuthority12402Mapping file id12402 NCBI fileEvidenceIEA
GeneCol11a1Authority12814Mapping file id12814 NCBI fileEvidenceIEA
GeneCol11a2Authority12815Mapping file id12815 NCBI fileEvidenceIEA
GeneCol24a1Authority71355Mapping file id71355 NCBI fileEvidenceIEA
GeneCol27a1Authority373864Mapping file id373864 NCBI fileEvidenceIEA
GeneCol2a1Authority12824Mapping file id12824 NCBI fileEvidenceIEA
GeneCol3a1Authority12825Mapping file id12825 NCBI fileEvidenceIEA
GeneCol5a1Authority12831Mapping file id12831 NCBI fileEvidenceIEA
GeneCol5a2Authority12832Mapping file id12832 NCBI fileEvidenceIEA
GeneCol5a3Authority53867Mapping file id53867 NCBI fileEvidenceIEA
GeneCrkAuthority12928Mapping file id12928 NCBI fileEvidenceIEA
GeneCrklAuthority12929Mapping file id12929 NCBI fileEvidenceIEA
GeneDock7Authority67299Mapping file idENSMUSG00000028556 Ensembl fileEvidenceIEA
GeneEps15Authority13858Mapping file id13858 NCBI fileEvidenceIEA
GeneFn1Authority14268Mapping file id14268 NCBI fileEvidenceIEA
GeneGab1Authority14388Mapping file id14388 NCBI fileEvidenceIEA
GeneGga3Authority260302Mapping file id260302 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneHgfAuthority15234Mapping file id15234 NCBI fileEvidenceIEA
GeneHgfacAuthority54426Mapping file id54426 NCBI fileEvidenceIEA
GeneHgsAuthority15239Mapping file id15239 NCBI fileEvidenceIEA
GeneHpnAuthority15451Mapping file id15451 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneItga2Authority16398Mapping file id16398 NCBI fileEvidenceIEA
GeneItga3Authority16400Mapping file id16400 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneLama4Authority16775Mapping file id16775 NCBI fileEvidenceIEA
GeneLrig1Authority16206Mapping file id16206 NCBI fileEvidenceIEA
GeneMegf11Authority214058Mapping file id214058 NCBI fileEvidenceIEA
GeneMetAuthority17295Mapping file idENSMUSG00000009376 Ensembl fileEvidenceIEA
GeneMuc20Authority224116Mapping file id224116 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GenePtpn1Authority19246Mapping file id19246 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GenePtpn2Authority19255Mapping file id19255 NCBI fileEvidenceIEA
GenePtprjAuthority19271Mapping file id19271 NCBI fileEvidenceIEA
GeneRab4aAuthority19341Mapping file id19341 NCBI fileEvidenceIEA
GeneRab4bAuthority19342Mapping file id19342 NCBI fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 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
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneSh3gl1Authority20405Mapping file id20405 NCBI fileEvidenceIEA
GeneSh3gl2Authority20404Mapping file id20404 NCBI fileEvidenceIEA
GeneSh3gl3Authority20408Mapping file id20408 NCBI fileEvidenceIEA
GeneSh3kbp1Authority58194Mapping file id58194 NCBI fileEvidenceIEA
GeneShc1Authority20416Mapping file id20416 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneSpint1Authority20732Mapping file id20732 NCBI fileEvidenceIEA
GeneSpint2Authority20733Mapping file id20733 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneStamAuthority20844Mapping file id20844 NCBI fileEvidenceIEA
GeneStam2Authority56324Mapping file id56324 NCBI fileEvidenceIEA
GeneStat3Authority20848Mapping file id20848 NCBI fileEvidenceIEA
GeneTns3Authority319939Mapping file id319939 NCBI fileEvidenceIEA
GeneTns4Authority217169Mapping file id217169 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUsp8Authority84092Mapping file id84092 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.