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.

Peroxisomal protein import

R-MMU-9033241 in Reactome release 97: under Protein localization, with 67 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-9033241 (human), R-RNO-9033241 (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 67 genes in this mouse pathway; showing 1 to 67, 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
GeneAcaa1bAuthority235674Mapping file id235674 NCBI fileEvidenceIEA
GeneAcot1Authority26897Mapping file id26897 NCBI fileEvidenceIEA
GeneAcot2Authority171210Mapping file id171210 NCBI fileEvidenceIEA
GeneAcot3Authority171281Mapping file id171281 NCBI fileEvidenceIEA
GeneAcot4Authority171282Mapping file id171282 NCBI fileEvidenceIEA
GeneAcot5Authority217698Mapping file id217698 NCBI fileEvidenceIEA
GeneAcot8Authority170789Mapping file id170789 NCBI fileEvidenceIEA
GeneAcox1Authority11430Mapping file id11430 NCBI fileEvidenceIEA
GeneAcox2Authority93732Mapping file id93732 NCBI fileEvidenceIEA
GeneAcox3Authority80911Mapping file id80911 NCBI fileEvidenceIEA
GeneAgpsAuthority228061Mapping file id228061 NCBI fileEvidenceIEA
GeneAgxtAuthority11611Mapping file id11611 NCBI fileEvidenceIEA
GeneAmacrAuthority17117Mapping file id17117 NCBI fileEvidenceIEA
GeneBaatAuthority12012Mapping file id12012 NCBI fileEvidenceIEA
GeneCatAuthority12359Mapping file id12359 NCBI fileEvidenceIEA
GeneCratAuthority12908Mapping file id12908 NCBI fileEvidenceIEA
GeneCrotAuthority74114Mapping file id74114 NCBI fileEvidenceIEA
GeneDaoAuthority13142Mapping file id13142 NCBI fileEvidenceIEA
GeneDdoAuthority70503Mapping file id70503 NCBI fileEvidenceIEA
GeneDecr2Authority26378Mapping file id26378 NCBI fileEvidenceIEA
GeneDhrs4Authority28200Mapping file id28200 NCBI fileEvidenceIEA
GeneEch1Authority51798Mapping file id51798 NCBI fileEvidenceIEA
GeneEci2Authority23986Mapping file id23986 NCBI fileEvidenceIEA
GeneEhhadhAuthority74147Mapping file id74147 NCBI fileEvidenceIEA
GeneEphx2Authority13850Mapping file id13850 NCBI fileEvidenceIEA
GeneGnpatAuthority14712Mapping file id14712 NCBI fileEvidenceIEA
GeneGstk1Authority76263Mapping file id76263 NCBI fileEvidenceIEA
GeneHacl1Authority56794Mapping file id56794 NCBI fileEvidenceIEA
GeneHao1Authority15112Mapping file id15112 NCBI fileEvidenceIEA
GeneHao2Authority56185Mapping file id56185 NCBI fileEvidenceIEA
GeneHmgclAuthority15356Mapping file id15356 NCBI fileEvidenceIEA
GeneHsd17b4Authority15488Mapping file id15488 NCBI fileEvidenceIEA
GeneIdeAuthority15925Mapping file idENSMUSG00000056999 Ensembl fileEvidenceIEA
GeneIdh1Authority15926Mapping file id15926 NCBI fileEvidenceIEA
GeneLonp2Authority66887Mapping file id66887 NCBI fileEvidenceIEA
GeneMlycdAuthority56690Mapping file id56690 NCBI fileEvidenceIEA
GeneMpv17Authority17527Mapping file id17527 NCBI fileEvidenceIEA
GeneNos2Authority18126Mapping file id18126 NCBI fileEvidenceIEA
GeneNudt19Authority110959Mapping file id110959 NCBI fileEvidenceIEA
GeneNudt7Authority67528Mapping file id67528 NCBI fileEvidenceIEA
GenePaoxAuthority212503Mapping file id212503 NCBI fileEvidenceIEA
GenePecrAuthority111175Mapping file id111175 NCBI fileEvidenceIEA
GenePex1Authority71382Mapping file id71382 NCBI fileEvidenceIEA
GenePex10Authority668173Mapping file id668173 NCBI fileEvidenceIEA
GenePex12Authority103737Mapping file id103737 NCBI fileEvidenceIEA
GenePex13Authority72129Mapping file id72129 NCBI fileEvidenceIEA
GenePex14Authority56273Mapping file id56273 NCBI fileEvidenceIEA
GenePex2Authority19302Mapping file id19302 NCBI fileEvidenceIEA
GenePex26Authority74043Mapping file id74043 NCBI fileEvidenceIEA
GenePex5Authority19305Mapping file id19305 NCBI fileEvidenceIEA
GenePex6Authority224824Mapping file id224824 NCBI fileEvidenceIEA
GenePex7Authority18634Mapping file id18634 NCBI fileEvidenceIEA
GenePhyhAuthority16922Mapping file id16922 NCBI fileEvidenceIEA
GenePipoxAuthority19193Mapping file id19193 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneScp2Authority20280Mapping file id20280 NCBI fileEvidenceIEA
GeneSlc27a2Authority26458Mapping file id26458 NCBI fileEvidenceIEA
GeneTysnd1Authority71767Mapping file id71767 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUbe2d1Authority216080Mapping file id216080 NCBI fileEvidenceIEA
GeneUbe2d2aAuthority56550Mapping file id56550 NCBI fileEvidenceIEA
GeneUbe2d3Authority66105Mapping file id66105 NCBI fileEvidenceIEA
GeneUsp9xAuthority22284Mapping file id22284 NCBI fileEvidenceIEA
GeneZfand6Authority65098Mapping file id65098 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.