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.

MTOR signalling

R-MMU-165159 in Reactome release 97: under Signal Transduction, with 43 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-165159 (human), R-RNO-165159 (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 43 genes in this mouse pathway; showing 1 to 43, 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
GeneAkt1Authority11651Mapping file id11651 NCBI fileEvidenceIEA
GeneAkt1s1Authority67605Mapping file id67605 NCBI fileEvidenceIEA
GeneAkt2Authority11652Mapping file id11652 NCBI fileEvidenceIEA
GeneAkt3Authority23797Mapping file id23797 NCBI fileEvidenceIEA
GeneCab39Authority12283Mapping file id12283 NCBI fileEvidenceIEA
GeneCab39lAuthority69008Mapping file id69008 NCBI fileEvidenceIEA
GeneEef2kAuthority13631Mapping file id13631 NCBI fileEvidenceIEA
GeneEif4bAuthority75705Mapping file id75705 NCBI fileEvidenceIEA
GeneEif4eAuthority13684Mapping file id13684 NCBI fileEvidenceIEA
GeneEif4ebp1Authority13685Mapping file id13685 NCBI fileEvidenceIEA
GeneEif4g1Authority208643Mapping file id208643 NCBI fileEvidenceIEA
GeneFkbp1aAuthority14225Mapping file id14225 NCBI fileEvidenceIEA
GeneLamtor1Authority66508Mapping file id66508 NCBI fileEvidenceIEA
GeneLamtor2Authority83409Mapping file id83409 NCBI fileEvidenceIEA
GeneLamtor3Authority56692Mapping file id56692 NCBI fileEvidenceIEA
GeneLamtor4Authority66096Mapping file id66096 NCBI fileEvidenceIEA
GeneLamtor5Authority68576Mapping file id68576 NCBI fileEvidenceIEA
GeneMlst8Authority56716Mapping file id56716 NCBI fileEvidenceIEA
GeneMtorAuthority56717Mapping file id56717 NCBI fileEvidenceIEA
GenePgk1Authority18655Mapping file id18655 NCBI fileEvidenceIEA
GenePpm1aAuthority19042Mapping file id19042 NCBI fileEvidenceIEA
GenePrkaa1Authority105787Mapping file id105787 NCBI fileEvidenceIEA
GenePrkaa2Authority108079Mapping file id108079 NCBI fileEvidenceIEA
GenePrkab1Authority19079Mapping file id19079 NCBI fileEvidenceIEA
GenePrkab2Authority108097Mapping file id108097 NCBI fileEvidenceIEA
GenePrkag1Authority19082Mapping file id19082 NCBI fileEvidenceIEA
GenePrkag2Authority108099Mapping file id108099 NCBI fileEvidenceIEA
GenePrkag3Authority241113Mapping file id241113 NCBI fileEvidenceIEA
GeneRhebAuthority19744Mapping file id19744 NCBI fileEvidenceIEA
GeneRps6Authority20104Mapping file id20104 NCBI fileEvidenceIEA
GeneRps6kb1Authority72508Mapping file id72508 NCBI fileEvidenceIEA
GeneRptorAuthority74370Mapping file idENSMUSG00000025583 Ensembl fileEvidenceIEA
GeneRragaAuthority68441Mapping file id68441 NCBI fileEvidenceIEA
GeneRragbAuthority245670Mapping file id245670 NCBI fileEvidenceIEA
GeneRragcAuthority54170Mapping file id54170 NCBI fileEvidenceIEA
GeneRragdAuthority52187Mapping file id52187 NCBI fileEvidenceIEA
GeneSlc38a9Authority268706Mapping file id268706 NCBI fileEvidenceIEA
GeneStk11Authority20869Mapping file id20869 NCBI fileEvidenceIEA
GeneStradaAuthority72149Mapping file id72149 NCBI fileEvidenceIEA
GeneStradbAuthority227154Mapping file id227154 NCBI fileEvidenceIEA
GeneTsc1Authority64930Mapping file id64930 NCBI fileEvidenceIEA
GeneTsc2Authority22084Mapping file idENSMUSG00000002496 Ensembl 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.