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.

Negative regulation of the PI3K/AKT network

R-MMU-199418 in Reactome release 97: under PIP3 activates AKT signaling, with 119 genes placed in it by the mapping files and 1 child pathway 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-199418 (human), R-RNO-199418 (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 119 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
GeneAkt1Authority11651Mapping file id11651 NCBI fileEvidenceIEA
GeneAkt2Authority11652Mapping file id11652 NCBI fileEvidenceIEA
GeneAkt3Authority23797Mapping file id23797 NCBI fileEvidenceIEA
GeneAregAuthority11839Mapping file id11839 NCBI fileEvidenceIEA
GeneBdnfAuthority12064Mapping file id12064 NCBI fileEvidenceIEA
GeneBtcAuthority12223Mapping file id12223 NCBI fileEvidenceIEA
GeneCd19Authority12478Mapping file id12478 NCBI fileEvidenceIEA
GeneCd28Authority12487Mapping file id12487 NCBI fileEvidenceIEA
GeneCd80Authority12519Mapping file id12519 NCBI fileEvidenceIEA
GeneCd86Authority12524Mapping file id12524 NCBI fileEvidenceIEA
GeneEgfAuthority13645Mapping file id13645 NCBI fileEvidenceIEA
GeneEgfrAuthority13649Mapping file id13649 NCBI fileEvidenceIEA
GeneEpgnAuthority71920Mapping file id71920 NCBI fileEvidenceIEA
GeneErbb2Authority13866Mapping file id13866 NCBI fileEvidenceIEA
GeneErbb3Authority13867Mapping file id13867 NCBI fileEvidenceIEA
GeneErbb4Authority13869Mapping file id13869 NCBI fileEvidenceIEA
GeneEregAuthority13874Mapping file id13874 NCBI fileEvidenceIEA
GeneEsr1Authority13982Mapping file id13982 NCBI fileEvidenceIEA
GeneEsr2Authority13983Mapping file id13983 NCBI fileEvidenceIEA
GeneFgf1Authority14164Mapping file id14164 NCBI fileEvidenceIEA
GeneFgf10Authority14165Mapping file id14165 NCBI fileEvidenceIEA
GeneFgf15Authority14170Mapping file id14170 NCBI fileEvidenceIEA
GeneFgf16Authority80903Mapping file id80903 NCBI fileEvidenceIEA
GeneFgf17Authority14171Mapping file id14171 NCBI fileEvidenceIEA
GeneFgf18Authority14172Mapping file id14172 NCBI fileEvidenceIEA
GeneFgf2Authority14173Mapping file id14173 NCBI fileEvidenceIEA
GeneFgf20Authority80857Mapping file id80857 NCBI fileEvidenceIEA
GeneFgf22Authority67112Mapping file id67112 NCBI fileEvidenceIEA
GeneFgf23Authority64654Mapping file id64654 NCBI fileEvidenceIEA
GeneFgf3Authority14174Mapping file idENSMUSG00000031074 Ensembl fileEvidenceIEA
GeneFgf4Authority14175Mapping file id14175 NCBI fileEvidenceIEA
GeneFgf5Authority14176Mapping file id14176 NCBI fileEvidenceIEA
GeneFgf6Authority14177Mapping file id14177 NCBI fileEvidenceIEA
GeneFgf7Authority14178Mapping file id14178 NCBI fileEvidenceIEA
GeneFgf8Authority14179Mapping file id14179 NCBI fileEvidenceIEA
GeneFgf9Authority14180Mapping file id14180 NCBI fileEvidenceIEA
GeneFgfr1Authority14182Mapping file id14182 NCBI fileEvidenceIEA
GeneFgfr2Authority14183Mapping file id14183 NCBI fileEvidenceIEA
GeneFgfr3Authority14184Mapping file idENSMUSG00000054252 Ensembl fileEvidenceIEA
GeneFgfr4Authority14186Mapping file id14186 NCBI fileEvidenceIEA
GeneFlt3Authority14255Mapping file id14255 NCBI fileEvidenceIEA
GeneFlt3lAuthority14256Mapping file id14256 NCBI fileEvidenceIEA
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneGab1Authority14388Mapping file id14388 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHgfAuthority15234Mapping file id15234 NCBI fileEvidenceIEA
GeneIcosAuthority54167Mapping file id54167 NCBI fileEvidenceIEA
GeneIer3Authority15937Mapping file id15937 NCBI fileEvidenceIEA
GeneIl1rapAuthority16180Mapping file id16180 NCBI fileEvidenceIEA
GeneIl1rl1Authority17082Mapping file id17082 NCBI fileEvidenceIEA
GeneIl33Authority77125Mapping file id77125 NCBI fileEvidenceIEA
GeneIns1Authority16333Mapping file id16333 NCBI fileEvidenceIEA
GeneIns2Authority16334Mapping file id16334 NCBI fileEvidenceIEA
GeneInsrAuthority16337Mapping file id16337 NCBI fileEvidenceIEA
GeneIrak1Authority16179Mapping file id16179 NCBI fileEvidenceIEA
GeneIrak4Authority266632Mapping file id266632 NCBI fileEvidenceIEA
GeneIrs1Authority16367Mapping file id16367 NCBI fileEvidenceIEA
GeneIrs2Authority384783Mapping file id384783 NCBI fileEvidenceIEA
GeneKitAuthority16590Mapping file id16590 NCBI fileEvidenceIEA
GeneKitlAuthority17311Mapping file id17311 NCBI fileEvidenceIEA
GeneKlAuthority16591Mapping file id16591 NCBI fileEvidenceIEA
GeneKlbAuthority83379Mapping file id83379 NCBI fileEvidenceIEA
GeneLckAuthority16818Mapping file id16818 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMetAuthority17295Mapping file idENSMUSG00000009376 Ensembl fileEvidenceIEA
GeneMyd88Authority17874Mapping file id17874 NCBI fileEvidenceIEA
GeneNrg1Authority211323Mapping file id211323 NCBI fileEvidenceIEA
GeneNrg3Authority18183Mapping file id18183 NCBI fileEvidenceIEA
GeneNtf3Authority18205Mapping file id18205 NCBI fileEvidenceIEA
GeneNtf5Authority78405Mapping file id78405 NCBI fileEvidenceIEA
GeneNtrk2Authority18212Mapping file id18212 NCBI fileEvidenceIEA
GeneNtrk3Authority18213Mapping file id18213 NCBI fileEvidenceIEA
GenePdgfaAuthority18590Mapping file id18590 NCBI fileEvidenceIEA
GenePdgfbAuthority18591Mapping file id18591 NCBI fileEvidenceIEA
GenePdgfraAuthority18595Mapping file id18595 NCBI fileEvidenceIEA
GenePdgfrbAuthority18596Mapping file id18596 NCBI fileEvidenceIEA
GenePhlpp1Authority98432Mapping file id98432 NCBI fileEvidenceIEA
GenePhlpp2Authority244650Mapping file id244650 NCBI fileEvidenceIEA
GenePik3ap1Authority83490Mapping file id83490 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3cbAuthority74769Mapping file id74769 NCBI fileEvidenceIEA
GenePik3cdAuthority18707Mapping file id18707 NCBI fileEvidenceIEA
GenePik3cgAuthority30955Mapping file id30955 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePik3r5Authority320207Mapping file id320207 NCBI fileEvidenceIEA
GenePik3r6Authority104709Mapping file id104709 NCBI fileEvidenceIEA
GenePip4k2aAuthority18718Mapping file id18718 NCBI fileEvidenceIEA
GenePip4k2bAuthority108083Mapping file id108083 NCBI fileEvidenceIEA
GenePip4k2cAuthority117150Mapping file id117150 NCBI fileEvidenceIEA
GenePip5k1aAuthority18720Mapping file id18720 NCBI fileEvidenceIEA
GenePip5k1bAuthority18719Mapping file id18719 NCBI fileEvidenceIEA
GenePip5k1cAuthority18717Mapping file id18717 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.