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.

Complex I biogenesis

R-MMU-6799198 in Reactome release 97: under Respiratory electron transport, with 65 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-6799198 (human), R-RNO-6799198 (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 65 genes in this mouse pathway; showing 1 to 65, in pages of 100, sorted by symbol for reading. The order carries no ranking. 2 of the rows shown carry an id the identity file does not name, kept as the source wrote it.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAcad9Authority229211Mapping file id229211 NCBI fileEvidenceIEA
GeneDmac1Authority66928Mapping file id66928 NCBI fileEvidenceIEA
GeneDmac2Authority66349Mapping file id66349 NCBI fileEvidenceIEA
GeneEcsitAuthority26940Mapping file id26940 NCBI fileEvidenceIEA
GeneHscbAuthority100900Mapping file id100900 NCBI fileEvidenceIEA
GeneHspa9Authority15526Mapping file id15526 NCBI fileEvidenceIEA
GeneLyrm2Authority108755Mapping file id108755 NCBI fileEvidenceIEA
GeneND1Authority17716Mapping file id17716 NCBI fileEvidenceIEA
GeneND2Authority17717Mapping file id17717 NCBI fileEvidenceIEA
GeneND3Authority17718Mapping file id17718 NCBI fileEvidenceIEA
GeneND4Authority17719Mapping file id17719 NCBI fileEvidenceIEA
GeneND5Authority17721Mapping file id17721 NCBI fileEvidenceIEA
GeneND6Authority17722Mapping file id17722 NCBI fileEvidenceIEA
GeneNdufa1Authority54405Mapping file id54405 NCBI fileEvidenceIEA
GeneNdufa10Authority67273Mapping file id67273 NCBI fileEvidenceIEA
GeneNdufa11Authority69875Mapping file idENSMUSG00000002379 Ensembl fileEvidenceIEA
GeneNdufa12Authority66414Mapping file id66414 NCBI fileEvidenceIEA
GeneNdufa13Authority67184Mapping file id67184 NCBI fileEvidenceIEA
GeneNdufa2Authority17991Mapping file id17991 NCBI fileEvidenceIEA
GeneNdufa3Authority66091Mapping file id66091 NCBI fileEvidenceIEA
GeneNdufa5Authority68202Mapping file id68202 NCBI fileEvidenceIEA
GeneNdufa6Authority67130Mapping file id67130 NCBI fileEvidenceIEA
GeneNdufa7Authority66416Mapping file id66416 NCBI fileEvidenceIEA
GeneNdufa8Authority68375Mapping file id68375 NCBI fileEvidenceIEA
GeneNdufa9Authority66108Mapping file id66108 NCBI fileEvidenceIEA
GeneNdufab1Authority70316Mapping file id70316 NCBI fileEvidenceIEA
GeneNdufaf1Authority69702Mapping file id69702 NCBI fileEvidenceIEA
GeneNdufaf2Authority75597Mapping file id75597 NCBI fileEvidenceIEA
GeneNdufaf3Authority66706Mapping file id66706 NCBI fileEvidenceIEA
GeneNdufaf4Authority68493Mapping file id68493 NCBI fileEvidenceIEA
GeneNdufaf5Authority69487Mapping file id69487 NCBI fileEvidenceIEA
GeneNdufaf6Authority76947Mapping file id76947 NCBI fileEvidenceIEA
GeneNdufaf7Authority73694Mapping file id73694 NCBI fileEvidenceIEA
GeneNdufaf8Authority208501Mapping file id208501 NCBI fileEvidenceIEA
GeneNdufb1Authority102631912Mapping file id102631912 NCBI fileEvidenceIEA
GeneNdufb10Authority68342Mapping file id68342 NCBI fileEvidenceIEA
GeneNdufb11Authority104130Mapping file id104130 NCBI fileEvidenceIEA
GeneNdufb2Authority68198Mapping file id68198 NCBI fileEvidenceIEA
GeneNdufb3Authority66495Mapping file id66495 NCBI fileEvidenceIEA
GeneNdufb4Authority68194Mapping file id68194 NCBI fileEvidenceIEA
GeneNdufb5Authority66046Mapping file id66046 NCBI fileEvidenceIEA
GeneNdufb6Authority230075Mapping file id230075 NCBI fileEvidenceIEA
GeneNdufb7Authority66916Mapping file id66916 NCBI fileEvidenceIEA
GeneNdufb8Authority67264Mapping file id67264 NCBI fileEvidenceIEA
GeneNdufb9Authority66218Mapping file id66218 NCBI fileEvidenceIEA
GeneNdufc1Authority66377Mapping file id66377 NCBI fileEvidenceIEA
GeneNdufc2Authority68197Mapping file id68197 NCBI fileEvidenceIEA
GeneNdufs1Authority227197Mapping file id227197 NCBI fileEvidenceIEA
GeneNdufs2Authority226646Mapping file id226646 NCBI fileEvidenceIEA
GeneNdufs3Authority68349Mapping file id68349 NCBI fileEvidenceIEA
GeneNdufs4Authority17993Mapping file id17993 NCBI fileEvidenceIEA
GeneNdufs5Authority595136Mapping file id595136 NCBI fileEvidenceIEA
GeneNdufs6Authority407785Mapping file id407785 NCBI fileEvidenceIEA
GeneNdufs7Authority75406Mapping file id75406 NCBI fileEvidenceIEA
GeneNdufs8Authority225887Mapping file id225887 NCBI fileEvidenceIEA
GeneNdufv1Authority17995Mapping file id17995 NCBI fileEvidenceIEA
GeneNdufv2Authority72900Mapping file id72900 NCBI fileEvidenceIEA
GeneNdufv3Authority78330Mapping file id78330 NCBI fileEvidenceIEA
GeneNubplAuthority76826Mapping file id76826 NCBI fileEvidenceIEA
GenePyurfAuthority66459Mapping file id66459 NCBI fileEvidenceIEA
GeneTimmdc1Authority76916Mapping file id76916 NCBI fileEvidenceIEA
GeneTmem126bAuthority68472Mapping file id68472 NCBI fileEvidenceIEA
GeneTmem186Authority66690Mapping file id66690 NCBI fileEvidenceIEA
Geneno symbol in the identity fileAuthoritynoneMapping file id3338896 NCBI fileEvidenceIEA
Geneno symbol in the identity fileAuthoritynoneMapping file id3338902 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.