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 VEGF

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

Genes Reactome places in this mouse pathway, page 1 of 2
GeneAbi1Authority11308Mapping file id11308 NCBI fileEvidenceIEA
GeneAbi2Authority329165Mapping file id329165 NCBI fileEvidenceIEA
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneAkt1Authority11651Mapping file id11651 NCBI fileEvidenceIEA
GeneAkt2Authority11652Mapping file id11652 NCBI fileEvidenceIEA
GeneAkt3Authority23797Mapping file id23797 NCBI fileEvidenceIEA
GeneAxlAuthority26362Mapping file id26362 NCBI fileEvidenceIEA
GeneBaiap2Authority108100Mapping file id108100 NCBI fileEvidenceIEA
GeneBcar1Authority12927Mapping file id12927 NCBI fileEvidenceIEA
GeneBrk1Authority101314Mapping file id101314 NCBI fileEvidenceIEA
GeneCalm1Authority12313Mapping file id12313 NCBI fileEvidenceIEA
GeneCalm2Authority12314Mapping file idENSMUSG00000036438 Ensembl fileEvidenceIEA
GeneCalm3Authority12315Mapping file idENSMUSG00000019370 Ensembl fileEvidenceIEA
GeneCav1Authority12389Mapping file id12389 NCBI fileEvidenceIEA
GeneCdc42Authority12540Mapping file id12540 NCBI fileEvidenceIEA
GeneCdh5Authority12562Mapping file id12562 NCBI fileEvidenceIEA
GeneCrkAuthority12928Mapping file id12928 NCBI fileEvidenceIEA
GeneCtnna1Authority12385Mapping file id12385 NCBI fileEvidenceIEA
GeneCtnnb1Authority12387Mapping file id12387 NCBI fileEvidenceIEA
GeneCtnnd1Authority12388Mapping file id12388 NCBI fileEvidenceIEA
GeneCybaAuthority13057Mapping file id13057 NCBI fileEvidenceIEA
GeneCybbAuthority13058Mapping file id13058 NCBI fileEvidenceIEA
GeneCyfip1Authority20430Mapping file id20430 NCBI fileEvidenceIEA
GeneCyfip2Authority76884Mapping file id76884 NCBI fileEvidenceIEA
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneElmo1Authority140580Mapping file id140580 NCBI fileEvidenceIEA
GeneElmo2Authority140579Mapping file id140579 NCBI fileEvidenceIEA
GeneFlt1Authority14254Mapping file id14254 NCBI fileEvidenceIEA
GeneFlt4Authority14257Mapping file id14257 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneHspb1Authority15507Mapping file id15507 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneJupAuthority16480Mapping file id16480 NCBI fileEvidenceIEA
GeneKdrAuthority16542Mapping file id16542 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk12Authority29857Mapping file id29857 NCBI fileEvidenceIEA
GeneMapk13Authority26415Mapping file id26415 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapkap1Authority227743Mapping file id227743 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneMlst8Authority56716Mapping file id56716 NCBI fileEvidenceIEA
GeneMtorAuthority56717Mapping file id56717 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
GeneNos3Authority18127Mapping file id18127 NCBI fileEvidenceIEA
GeneNrp1Authority18186Mapping file id18186 NCBI fileEvidenceIEA
GeneNrp2Authority18187Mapping file id18187 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GenePak2Authority224105Mapping file id224105 NCBI fileEvidenceIEA
GenePak3Authority18481Mapping file id18481 NCBI fileEvidenceIEA
GenePdpk1Authority18607Mapping file id18607 NCBI fileEvidenceIEA
GenePgfAuthority18654Mapping file id18654 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
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
GenePrkczAuthority18762Mapping file id18762 NCBI fileEvidenceIEA
GenePrr5Authority109270Mapping file id109270 NCBI fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GenePtk2bAuthority19229Mapping file id19229 NCBI fileEvidenceIEA
GenePxnAuthority19303Mapping file id19303 NCBI fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 NCBI fileEvidenceIEA
GeneRasa1Authority218397Mapping file id218397 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRictorAuthority78757Mapping file id78757 NCBI fileEvidenceIEA
GeneRock1Authority19877Mapping file id19877 NCBI fileEvidenceIEA
GeneRock2Authority19878Mapping file id19878 NCBI fileEvidenceIEA
GeneSh2d2aAuthority27371Mapping file id27371 NCBI fileEvidenceIEA
GeneShbAuthority230126Mapping file id230126 NCBI fileEvidenceIEA
GeneShc2Authority216148Mapping file id216148 NCBI fileEvidenceIEA
GeneSphk1Authority20698Mapping file id20698 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneThem4Authority75778Mapping file id75778 NCBI fileEvidenceIEA
GeneTrib3Authority228775Mapping file id228775 NCBI fileEvidenceIEA
GeneVav1Authority22324Mapping file id22324 NCBI fileEvidenceIEA
GeneVav2Authority22325Mapping file id22325 NCBI fileEvidenceIEA
GeneVav3Authority57257Mapping file id57257 NCBI fileEvidenceIEA
GeneVegfaAuthority22339Mapping file id22339 NCBI fileEvidenceIEA
GeneVegfbAuthority22340Mapping file id22340 NCBI fileEvidenceIEA
GeneVegfcAuthority22341Mapping file id22341 NCBI fileEvidenceIEA
GeneVegfdAuthority14205Mapping file id14205 NCBI fileEvidenceIEA
GeneWasf1Authority83767Mapping file id83767 NCBI fileEvidenceIEA
GeneWasf2Authority242687Mapping file id242687 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.