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 NTRKs

R-MMU-166520 in Reactome release 97: under Signaling by Receptor Tyrosine Kinases, with 76 genes placed in it by the mapping files and 4 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-166520 (human), R-RNO-166520 (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 76 genes in this mouse pathway; showing 1 to 76, 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
GeneAp2a1Authority11771Mapping file id11771 NCBI fileEvidenceIEA
GeneAp2a2Authority11772Mapping file id11772 NCBI fileEvidenceIEA
GeneAp2b1Authority71770Mapping file id71770 NCBI fileEvidenceIEA
GeneAp2m1Authority11773Mapping file id11773 NCBI fileEvidenceIEA
GeneAp2s1Authority232910Mapping file id232910 NCBI fileEvidenceIEA
GeneAtf1Authority11908Mapping file id11908 NCBI fileEvidenceIEA
GeneBdnfAuthority12064Mapping file id12064 NCBI fileEvidenceIEA
GeneBrafAuthority109880Mapping file id109880 NCBI fileEvidenceIEA
GeneChd4Authority107932Mapping file id107932 NCBI fileEvidenceIEA
GeneCltaAuthority12757Mapping file idENSMUSG00000028478 Ensembl fileEvidenceIEA
GeneCltcAuthority67300Mapping file id67300 NCBI fileEvidenceIEA
GeneCreb1Authority12912Mapping file id12912 NCBI fileEvidenceIEA
GeneCrkAuthority12928Mapping file id12928 NCBI fileEvidenceIEA
GeneCrklAuthority12929Mapping file id12929 NCBI fileEvidenceIEA
GeneDnal4Authority54152Mapping file id54152 NCBI fileEvidenceIEA
GeneDusp3Authority72349Mapping file id72349 NCBI fileEvidenceIEA
GeneDusp4Authority319520Mapping file id319520 NCBI fileEvidenceIEA
GeneDusp6Authority67603Mapping file id67603 NCBI fileEvidenceIEA
GeneDusp7Authority235584Mapping file id235584 NCBI fileEvidenceIEA
GeneEgr2Authority13654Mapping file id13654 NCBI fileEvidenceIEA
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFurinAuthority18550Mapping file id18550 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneIrs1Authority16367Mapping file id16367 NCBI fileEvidenceIEA
GeneIrs2Authority384783Mapping file id384783 NCBI fileEvidenceIEA
GeneKidins220Authority77480Mapping file id77480 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneMap2k1Authority26395Mapping file id26395 NCBI fileEvidenceIEA
GeneMap2k2Authority26396Mapping file id26396 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneNab2Authority17937Mapping file id17937 NCBI fileEvidenceIEA
GeneNgfAuthority18049Mapping file id18049 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
GenePcsk5Authority18552Mapping file id18552 NCBI fileEvidenceIEA
GenePcsk6Authority18553Mapping file id18553 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3cbAuthority74769Mapping file id74769 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePlcg1Authority18803Mapping file id18803 NCBI fileEvidenceIEA
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 NCBI fileEvidenceIEA
GeneRalgdsAuthority19730Mapping file id19730 NCBI fileEvidenceIEA
GeneRap1aAuthority109905Mapping file id109905 NCBI fileEvidenceIEA
GeneRapgef1Authority107746Mapping file id107746 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRps6ka1Authority20111Mapping file id20111 NCBI fileEvidenceIEA
GeneRps6ka2Authority20112Mapping file id20112 NCBI fileEvidenceIEA
GeneRps6ka3Authority110651Mapping file id110651 NCBI fileEvidenceIEA
GeneRps6ka5Authority73086Mapping file id73086 NCBI fileEvidenceIEA
GeneSgk1Authority20393Mapping file id20393 NCBI fileEvidenceIEA
GeneSh3gl2Authority20404Mapping file id20404 NCBI fileEvidenceIEA
GeneShc1Authority20416Mapping file id20416 NCBI fileEvidenceIEA
GeneShc2Authority216148Mapping file id216148 NCBI fileEvidenceIEA
GeneShc3Authority20418Mapping file id20418 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneSrfAuthority20807Mapping file id20807 NCBI fileEvidenceIEA
GeneVrk3Authority101568Mapping file id101568 NCBI fileEvidenceIEA
GeneYwhabAuthority54401Mapping file id54401 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.