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.

Amino acids regulate mTORC1

R-MMU-9639288 in Reactome release 97: under Cellular response to starvation, with 55 genes placed in it by the mapping files and 0 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-9639288 (human), R-RNO-9639288 (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 55 genes in this mouse pathway; showing 1 to 55, 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
GeneAtp6v0bAuthority114143Mapping file id114143 NCBI fileEvidenceIEA
GeneAtp6v0cAuthority11984Mapping file id11984 NCBI fileEvidenceIEA
GeneAtp6v0d1Authority11972Mapping file id11972 NCBI fileEvidenceIEA
GeneAtp6v0d2Authority242341Mapping file id242341 NCBI fileEvidenceIEA
GeneAtp6v0eAuthority11974Mapping file id11974 NCBI fileEvidenceIEA
GeneAtp6v0e2Authority76252Mapping file id76252 NCBI fileEvidenceIEA
GeneAtp6v1aAuthority11964Mapping file id11964 NCBI fileEvidenceIEA
GeneAtp6v1b1Authority110935Mapping file id110935 NCBI fileEvidenceIEA
GeneAtp6v1b2Authority11966Mapping file id11966 NCBI fileEvidenceIEA
GeneAtp6v1c1Authority66335Mapping file id66335 NCBI fileEvidenceIEA
GeneAtp6v1c2Authority68775Mapping file id68775 NCBI fileEvidenceIEA
GeneAtp6v1dAuthority73834Mapping file id73834 NCBI fileEvidenceIEA
GeneAtp6v1e1Authority11973Mapping file id11973 NCBI fileEvidenceIEA
GeneAtp6v1e2Authority74915Mapping file id74915 NCBI fileEvidenceIEA
GeneAtp6v1fAuthority66144Mapping file id66144 NCBI fileEvidenceIEA
GeneAtp6v1g1Authority66290Mapping file id66290 NCBI fileEvidenceIEA
GeneAtp6v1g2Authority66237Mapping file id66237 NCBI fileEvidenceIEA
GeneAtp6v1g3Authority338375Mapping file id338375 NCBI fileEvidenceIEA
GeneAtp6v1hAuthority108664Mapping file id108664 NCBI fileEvidenceIEA
GeneCastor1Authority71962Mapping file id71962 NCBI fileEvidenceIEA
GeneCastor2Authority80909Mapping file id80909 NCBI fileEvidenceIEA
GeneDepdc5Authority277854Mapping file id277854 NCBI fileEvidenceIEA
GeneFlcnAuthority216805Mapping file id216805 NCBI fileEvidenceIEA
GeneFnip1Authority216742Mapping file id216742 NCBI fileEvidenceIEA
GeneFnip2Authority329679Mapping file id329679 NCBI fileEvidenceIEA
GeneItfg2Authority101142Mapping file id101142 NCBI fileEvidenceIEA
GeneKics2Authority270802Mapping file id270802 NCBI fileEvidenceIEA
GeneKptnAuthority70394Mapping file idENSMUSG00000006021 Ensembl 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
GeneMiosAuthority252875Mapping file id252875 NCBI fileEvidenceIEA
GeneMlst8Authority56716Mapping file id56716 NCBI fileEvidenceIEA
GeneMtorAuthority56717Mapping file id56717 NCBI fileEvidenceIEA
GeneNprl2Authority56032Mapping file id56032 NCBI fileEvidenceIEA
GeneNprl3Authority17168Mapping file id17168 NCBI fileEvidenceIEA
GeneRhebAuthority19744Mapping file id19744 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
GeneSamtorAuthority101148Mapping file id101148 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSeh1lAuthority72124Mapping file id72124 NCBI fileEvidenceIEA
GeneSesn1Authority140742Mapping file id140742 NCBI fileEvidenceIEA
GeneSesn2Authority230784Mapping file id230784 NCBI fileEvidenceIEA
GeneSh3bp4Authority98402Mapping file id98402 NCBI fileEvidenceIEA
GeneSlc38a9Authority268706Mapping file id268706 NCBI fileEvidenceIEA
GeneSzt2Authority230676Mapping file id230676 NCBI fileEvidenceIEA
GeneTcirg1Authority27060Mapping file id27060 NCBI fileEvidenceIEA
GeneWdr24Authority268933Mapping file id268933 NCBI fileEvidenceIEA
GeneWdr59Authority319481Mapping file id319481 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

Children

None: no pathway of this release's list names this one as a parent.

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.