Skip to content
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.

Mitochondrial translation elongation

R-MMU-5389840 in Reactome release 97: under Mitochondrial translation, with 86 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-5389840 (human), R-RNO-5389840 (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 86 genes in this mouse pathway; showing 1 to 86, 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
GeneAurkaip1Authority66077Mapping file id66077 NCBI fileEvidenceIEA
GeneChchd1Authority66121Mapping file id66121 NCBI fileEvidenceIEA
GeneDap3Authority65111Mapping file id65111 NCBI fileEvidenceIEA
GeneEral1Authority57837Mapping file id57837 NCBI fileEvidenceIEA
GeneGadd45gip1Authority102060Mapping file id102060 NCBI fileEvidenceIEA
GeneGfm1Authority28030Mapping file id28030 NCBI fileEvidenceIEA
GeneKdg4Authority66128Mapping file id66128 NCBI fileEvidenceIEA
GeneMrpl1Authority94061Mapping file id94061 NCBI fileEvidenceIEA
GeneMrpl10Authority107732Mapping file id107732 NCBI fileEvidenceIEA
GeneMrpl11Authority66419Mapping file id66419 NCBI fileEvidenceIEA
GeneMrpl12Authority56282Mapping file id56282 NCBI fileEvidenceIEA
GeneMrpl13Authority68537Mapping file id68537 NCBI fileEvidenceIEA
GeneMrpl14Authority68463Mapping file id68463 NCBI fileEvidenceIEA
GeneMrpl15Authority27395Mapping file id27395 NCBI fileEvidenceIEA
GeneMrpl16Authority94063Mapping file id94063 NCBI fileEvidenceIEA
GeneMrpl17Authority27397Mapping file id27397 NCBI fileEvidenceIEA
GeneMrpl18Authority67681Mapping file id67681 NCBI fileEvidenceIEA
GeneMrpl19Authority56284Mapping file id56284 NCBI fileEvidenceIEA
GeneMrpl2Authority27398Mapping file id27398 NCBI fileEvidenceIEA
GeneMrpl20Authority66448Mapping file id66448 NCBI fileEvidenceIEA
GeneMrpl21Authority353242Mapping file id353242 NCBI fileEvidenceIEA
GeneMrpl22Authority216767Mapping file id216767 NCBI fileEvidenceIEA
GeneMrpl23Authority19935Mapping file id19935 NCBI fileEvidenceIEA
GeneMrpl24Authority67707Mapping file id67707 NCBI fileEvidenceIEA
GeneMrpl27Authority94064Mapping file id94064 NCBI fileEvidenceIEA
GeneMrpl28Authority68611Mapping file id68611 NCBI fileEvidenceIEA
GeneMrpl3Authority94062Mapping file id94062 NCBI fileEvidenceIEA
GeneMrpl30Authority107734Mapping file id107734 NCBI fileEvidenceIEA
GeneMrpl32Authority75398Mapping file id75398 NCBI fileEvidenceIEA
GeneMrpl33Authority66845Mapping file id66845 NCBI fileEvidenceIEA
GeneMrpl34Authority94065Mapping file id94065 NCBI fileEvidenceIEA
GeneMrpl35Authority66223Mapping file id66223 NCBI fileEvidenceIEA
GeneMrpl36Authority94066Mapping file id94066 NCBI fileEvidenceIEA
GeneMrpl37Authority56280Mapping file id56280 NCBI fileEvidenceIEA
GeneMrpl38Authority60441Mapping file id60441 NCBI fileEvidenceIEA
GeneMrpl39Authority27393Mapping file id27393 NCBI fileEvidenceIEA
GeneMrpl4Authority66163Mapping file id66163 NCBI fileEvidenceIEA
GeneMrpl40Authority18100Mapping file id18100 NCBI fileEvidenceIEA
GeneMrpl41Authority107733Mapping file id107733 NCBI fileEvidenceIEA
GeneMrpl42Authority67270Mapping file id67270 NCBI fileEvidenceIEA
GeneMrpl43Authority94067Mapping file idENSMUSG00000025208 Ensembl fileEvidenceIEA
GeneMrpl44Authority69163Mapping file id69163 NCBI fileEvidenceIEA
GeneMrpl45Authority67036Mapping file id67036 NCBI fileEvidenceIEA
GeneMrpl46Authority67308Mapping file id67308 NCBI fileEvidenceIEA
GeneMrpl47Authority74600Mapping file id74600 NCBI fileEvidenceIEA
GeneMrpl48Authority52443Mapping file id52443 NCBI fileEvidenceIEA
GeneMrpl49Authority18120Mapping file id18120 NCBI fileEvidenceIEA
GeneMrpl50Authority28028Mapping file id28028 NCBI fileEvidenceIEA
GeneMrpl51Authority66493Mapping file id66493 NCBI fileEvidenceIEA
GeneMrpl52Authority68836Mapping file id68836 NCBI fileEvidenceIEA
GeneMrpl53Authority68499Mapping file id68499 NCBI fileEvidenceIEA
GeneMrpl54Authority66047Mapping file id66047 NCBI fileEvidenceIEA
GeneMrpl55Authority67212Mapping file id67212 NCBI fileEvidenceIEA
GeneMrpl57Authority67840Mapping file id67840 NCBI fileEvidenceIEA
GeneMrpl58Authority68572Mapping file id68572 NCBI fileEvidenceIEA
GeneMrpl9Authority78523Mapping file id78523 NCBI fileEvidenceIEA
GeneMrps10Authority64657Mapping file idENSMUSG00000034729 Ensembl fileEvidenceIEA
GeneMrps11Authority67994Mapping file idENSMUSG00000030611 Ensembl fileEvidenceIEA
GeneMrps12Authority24030Mapping file id24030 NCBI fileEvidenceIEA
GeneMrps14Authority64659Mapping file id64659 NCBI fileEvidenceIEA
GeneMrps15Authority66407Mapping file id66407 NCBI fileEvidenceIEA
GeneMrps16Authority66242Mapping file id66242 NCBI fileEvidenceIEA
GeneMrps17Authority66258Mapping file id66258 NCBI fileEvidenceIEA
GeneMrps18aAuthority68565Mapping file id68565 NCBI fileEvidenceIEA
GeneMrps18bAuthority66973Mapping file id66973 NCBI fileEvidenceIEA
GeneMrps18cAuthority68735Mapping file id68735 NCBI fileEvidenceIEA
GeneMrps2Authority118451Mapping file id118451 NCBI fileEvidenceIEA
GeneMrps21Authority66292Mapping file id66292 NCBI fileEvidenceIEA
GeneMrps22Authority64655Mapping file id64655 NCBI fileEvidenceIEA
GeneMrps23Authority64656Mapping file id64656 NCBI fileEvidenceIEA
GeneMrps24Authority64660Mapping file id64660 NCBI fileEvidenceIEA
GeneMrps25Authority64658Mapping file id64658 NCBI fileEvidenceIEA
GeneMrps26Authority99045Mapping file id99045 NCBI fileEvidenceIEA
GeneMrps27Authority218506Mapping file id218506 NCBI fileEvidenceIEA
GeneMrps28Authority66230Mapping file id66230 NCBI fileEvidenceIEA
GeneMrps30Authority59054Mapping file id59054 NCBI fileEvidenceIEA
GeneMrps31Authority57312Mapping file id57312 NCBI fileEvidenceIEA
GeneMrps33Authority14548Mapping file id14548 NCBI fileEvidenceIEA
GeneMrps34Authority79044Mapping file id79044 NCBI fileEvidenceIEA
GeneMrps35Authority232536Mapping file id232536 NCBI fileEvidenceIEA
GeneMrps5Authority77721Mapping file id77721 NCBI fileEvidenceIEA
GeneMrps6Authority121022Mapping file id121022 NCBI fileEvidenceIEA
GeneMrps7Authority50529Mapping file id50529 NCBI fileEvidenceIEA
GeneMrps9Authority69527Mapping file id69527 NCBI fileEvidenceIEA
GeneOxa1lAuthority69089Mapping file id69089 NCBI fileEvidenceIEA
GenePtcd3Authority69956Mapping file id69956 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.