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.

Protein ubiquitination

R-MMU-8852135 in Reactome release 97: under Post-translational protein modification, with 74 genes placed in it by the mapping files and 2 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-8852135 (human), R-RNO-8852135 (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 74 genes in this mouse pathway; showing 1 to 74, 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
GeneBcl10Authority12042Mapping file id12042 NCBI fileEvidenceIEA
GeneCdc34Authority216150Mapping file id216150 NCBI fileEvidenceIEA
GeneCdc73Authority214498Mapping file id214498 NCBI fileEvidenceIEA
GeneCtr9Authority22083Mapping file id22083 NCBI fileEvidenceIEA
GeneH2bc1Authority319177Mapping file id319177 NCBI fileEvidenceIEA
GeneH2bc11Authority319183Mapping file id319183 NCBI fileEvidenceIEA
GeneH2bc12Authority319184Mapping file id319184 NCBI fileEvidenceIEA
GeneH2bc13Authority319185Mapping file id319185 NCBI fileEvidenceIEA
GeneH2bc15Authority319187Mapping file id319187 NCBI fileEvidenceIEA
GeneH2bc18Authority319189Mapping file id319189 NCBI fileEvidenceIEA
GeneH2bc21Authority319190Mapping file id319190 NCBI fileEvidenceIEA
GeneH2bc22Authority319188Mapping file id319188 NCBI fileEvidenceIEA
GeneH2bc23Authority665596Mapping file idENSMUSG00000069307 Ensembl fileEvidenceIEA
GeneH2bc24Authority665622Mapping file idENSMUSG00000069303 Ensembl fileEvidenceIEA
GeneH2bc3Authority319178Mapping file id319178 NCBI fileEvidenceIEA
GeneH2bc4Authority68024Mapping file id68024 NCBI fileEvidenceIEA
GeneH2bc6Authority319179Mapping file id319179 NCBI fileEvidenceIEA
GeneH2bc7Authority319180Mapping file id319180 NCBI fileEvidenceIEA
GeneH2bc8Authority319181Mapping file id319181 NCBI fileEvidenceIEA
GeneH2bc9Authority319182Mapping file id319182 NCBI fileEvidenceIEA
GeneHltfAuthority20585Mapping file id20585 NCBI fileEvidenceIEA
GeneLeo1Authority235497Mapping file id235497 NCBI fileEvidenceIEA
GeneOtulinAuthority432940Mapping file id432940 NCBI fileEvidenceIEA
GenePaf1Authority54624Mapping file id54624 NCBI fileEvidenceIEA
GenePcnaAuthority18538Mapping file id18538 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
GenePex5Authority19305Mapping file id19305 NCBI fileEvidenceIEA
GenePrkdcAuthority19090Mapping file id19090 NCBI fileEvidenceIEA
GeneRad18Authority58186Mapping file id58186 NCBI fileEvidenceIEA
GeneRnf144aAuthority108089Mapping file id108089 NCBI fileEvidenceIEA
GeneRnf152Authority320311Mapping file id320311 NCBI fileEvidenceIEA
GeneRnf181Authority66510Mapping file id66510 NCBI fileEvidenceIEA
GeneRnf20Authority109331Mapping file id109331 NCBI fileEvidenceIEA
GeneRnf40Authority233900Mapping file id233900 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRragaAuthority68441Mapping file id68441 NCBI fileEvidenceIEA
GeneShprhAuthority268281Mapping file id268281 NCBI fileEvidenceIEA
GeneSkic8Authority66317Mapping file id66317 NCBI fileEvidenceIEA
GeneUba1Authority22201Mapping file id22201 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUba6Authority231380Mapping file id231380 NCBI fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUbe2aAuthority22209Mapping file id22209 NCBI fileEvidenceIEA
GeneUbe2bAuthority22210Mapping file id22210 NCBI fileEvidenceIEA
GeneUbe2cAuthority68612Mapping file id68612 NCBI fileEvidenceIEA
GeneUbe2d1Authority216080Mapping file id216080 NCBI fileEvidenceIEA
GeneUbe2d2aAuthority56550Mapping file id56550 NCBI fileEvidenceIEA
GeneUbe2d3Authority66105Mapping file id66105 NCBI fileEvidenceIEA
GeneUbe2e1Authority22194Mapping file id22194 NCBI fileEvidenceIEA
GeneUbe2e3Authority22193Mapping file id22193 NCBI fileEvidenceIEA
GeneUbe2g1Authority67128Mapping file id67128 NCBI fileEvidenceIEA
GeneUbe2g2Authority22213Mapping file id22213 NCBI fileEvidenceIEA
GeneUbe2hAuthority22214Mapping file id22214 NCBI fileEvidenceIEA
GeneUbe2kAuthority53323Mapping file id53323 NCBI fileEvidenceIEA
GeneUbe2l3Authority22195Mapping file id22195 NCBI fileEvidenceIEA
GeneUbe2nAuthority93765Mapping file id93765 NCBI fileEvidenceIEA
GeneUbe2q2Authority109161Mapping file id109161 NCBI fileEvidenceIEA
GeneUbe2r2Authority67615Mapping file id67615 NCBI fileEvidenceIEA
GeneUbe2sAuthority77891Mapping file id77891 NCBI fileEvidenceIEA
GeneUbe2tAuthority67196Mapping file id67196 NCBI fileEvidenceIEA
GeneUbe2v2Authority70620Mapping file id70620 NCBI fileEvidenceIEA
GeneUbe2wAuthority66799Mapping file id66799 NCBI fileEvidenceIEA
GeneUbe2zAuthority268470Mapping file id268470 NCBI fileEvidenceIEA
GeneUchl3Authority50933Mapping file id50933 NCBI fileEvidenceIEA
GeneUsp5Authority22225Mapping file id22225 NCBI fileEvidenceIEA
GeneUsp7Authority252870Mapping file id252870 NCBI fileEvidenceIEA
GeneUsp9xAuthority22284Mapping file id22284 NCBI fileEvidenceIEA
GeneWacAuthority225131Mapping file id225131 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.