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.

Ribosome Quality Control (RQC) complex extracts and degrades nascent peptide

R-MMU-9954709 in Reactome release 97: under Ribosome-associated quality control, with 98 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-9954709 (human), R-RNO-9954709 (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 98 genes in this mouse pathway; showing 1 to 98, 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
GeneAdrm1Authority56436Mapping file id56436 NCBI fileEvidenceIEA
GeneCul2Authority71745Mapping file id71745 NCBI fileEvidenceIEA
GeneElobAuthority67673Mapping file id67673 NCBI fileEvidenceIEA
GeneElocAuthority67923Mapping file id67923 NCBI fileEvidenceIEA
GeneKlhdc10Authority76788Mapping file id76788 NCBI fileEvidenceIEA
GeneLtn1Authority78913Mapping file id78913 NCBI fileEvidenceIEA
GeneNemfAuthority66244Mapping file id66244 NCBI fileEvidenceIEA
GenePsma1Authority26440Mapping file id26440 NCBI fileEvidenceIEA
GenePsma2Authority19166Mapping file id19166 NCBI fileEvidenceIEA
GenePsma3Authority19167Mapping file id19167 NCBI fileEvidenceIEA
GenePsma4Authority26441Mapping file id26441 NCBI fileEvidenceIEA
GenePsma5Authority26442Mapping file id26442 NCBI fileEvidenceIEA
GenePsma6Authority26443Mapping file id26443 NCBI fileEvidenceIEA
GenePsma7Authority26444Mapping file id26444 NCBI fileEvidenceIEA
GenePsmb1Authority19170Mapping file id19170 NCBI fileEvidenceIEA
GenePsmb2Authority26445Mapping file id26445 NCBI fileEvidenceIEA
GenePsmb3Authority26446Mapping file id26446 NCBI fileEvidenceIEA
GenePsmb4Authority19172Mapping file id19172 NCBI fileEvidenceIEA
GenePsmb5Authority19173Mapping file id19173 NCBI fileEvidenceIEA
GenePsmb6Authority19175Mapping file id19175 NCBI fileEvidenceIEA
GenePsmb7Authority19177Mapping file id19177 NCBI fileEvidenceIEA
GenePsmc1Authority19179Mapping file id19179 NCBI fileEvidenceIEA
GenePsmc2Authority19181Mapping file id19181 NCBI fileEvidenceIEA
GenePsmc3Authority19182Mapping file id19182 NCBI fileEvidenceIEA
GenePsmc4Authority23996Mapping file id23996 NCBI fileEvidenceIEA
GenePsmc5Authority19184Mapping file id19184 NCBI fileEvidenceIEA
GenePsmc6Authority67089Mapping file id67089 NCBI fileEvidenceIEA
GenePsmd1Authority70247Mapping file id70247 NCBI fileEvidenceIEA
GenePsmd11Authority69077Mapping file id69077 NCBI fileEvidenceIEA
GenePsmd12Authority66997Mapping file id66997 NCBI fileEvidenceIEA
GenePsmd13Authority23997Mapping file id23997 NCBI fileEvidenceIEA
GenePsmd14Authority59029Mapping file id59029 NCBI fileEvidenceIEA
GenePsmd2Authority21762Mapping file id21762 NCBI fileEvidenceIEA
GenePsmd3Authority22123Mapping file id22123 NCBI fileEvidenceIEA
GenePsmd6Authority66413Mapping file id66413 NCBI fileEvidenceIEA
GenePsmd7Authority17463Mapping file id17463 NCBI fileEvidenceIEA
GenePsmd8Authority57296Mapping file id57296 NCBI fileEvidenceIEA
GeneRbx1Authority56438Mapping file id56438 NCBI fileEvidenceIEA
GeneRchy1Authority68098Mapping file id68098 NCBI fileEvidenceIEA
GeneRpl10Authority110954Mapping file id110954 NCBI fileEvidenceIEA
GeneRpl10-ps3Authority100043346Mapping file idENSMUSG00000058443 Ensembl fileEvidenceIEA
GeneRpl10lAuthority238217Mapping file id238217 NCBI fileEvidenceIEA
GeneRpl11Authority67025Mapping file id67025 NCBI fileEvidenceIEA
GeneRpl12Authority269261Mapping file id269261 NCBI fileEvidenceIEA
GeneRpl13Authority270106Mapping file id270106 NCBI fileEvidenceIEA
GeneRpl13aAuthority22121Mapping file id22121 NCBI fileEvidenceIEA
GeneRpl14Authority67115Mapping file id67115 NCBI fileEvidenceIEA
GeneRpl15Authority66480Mapping file id66480 NCBI fileEvidenceIEA
GeneRpl18Authority19899Mapping file id19899 NCBI fileEvidenceIEA
GeneRpl18aAuthority76808Mapping file id76808 NCBI fileEvidenceIEA
GeneRpl19Authority19921Mapping file id19921 NCBI fileEvidenceIEA
GeneRpl21Authority19933Mapping file id19933 NCBI fileEvidenceIEA
GeneRpl22Authority19934Mapping file id19934 NCBI fileEvidenceIEA
GeneRpl22l1Authority68028Mapping file id68028 NCBI fileEvidenceIEA
GeneRpl23Authority65019Mapping file id65019 NCBI fileEvidenceIEA
GeneRpl23aAuthority268449Mapping file id268449 NCBI fileEvidenceIEA
GeneRpl24Authority68193Mapping file id68193 NCBI fileEvidenceIEA
GeneRpl26Authority19941Mapping file id19941 NCBI fileEvidenceIEA
GeneRpl27Authority19942Mapping file id19942 NCBI fileEvidenceIEA
GeneRpl27aAuthority26451Mapping file id26451 NCBI fileEvidenceIEA
GeneRpl28Authority19943Mapping file id19943 NCBI fileEvidenceIEA
GeneRpl29Authority19944Mapping file id19944 NCBI fileEvidenceIEA
GeneRpl3Authority27367Mapping file id27367 NCBI fileEvidenceIEA
GeneRpl30Authority19946Mapping file id19946 NCBI fileEvidenceIEA
GeneRpl31Authority114641Mapping file id114641 NCBI fileEvidenceIEA
GeneRpl32Authority19951Mapping file id19951 NCBI fileEvidenceIEA
GeneRpl34Authority68436Mapping file id68436 NCBI fileEvidenceIEA
GeneRpl35Authority66489Mapping file id66489 NCBI fileEvidenceIEA
GeneRpl35aAuthority57808Mapping file id57808 NCBI fileEvidenceIEA
GeneRpl35rtAuthority100038991Mapping file idENSMUSG00000078193 Ensembl fileEvidenceIEA
GeneRpl36-ps4Authority626888Mapping file idENSMUSG00000093922 Ensembl fileEvidenceIEA
GeneRpl36aAuthority19982Mapping file id19982 NCBI fileEvidenceIEA
GeneRpl36a-ps1Authority100043787Mapping file idENSMUSG00000060377 Ensembl fileEvidenceIEA
GeneRpl36alAuthority66483Mapping file id66483 NCBI fileEvidenceIEA
GeneRpl37Authority67281Mapping file id67281 NCBI fileEvidenceIEA
GeneRpl37aAuthority19981Mapping file id19981 NCBI fileEvidenceIEA
GeneRpl37rtAuthority100502825Mapping file id100502825 NCBI fileEvidenceIEA
GeneRpl38Authority67671Mapping file id67671 NCBI fileEvidenceIEA
GeneRpl39Authority67248Mapping file id67248 NCBI fileEvidenceIEA
GeneRpl39lAuthority68172Mapping file id68172 NCBI fileEvidenceIEA
GeneRpl3lAuthority66211Mapping file id66211 NCBI fileEvidenceIEA
GeneRpl4Authority67891Mapping file id67891 NCBI fileEvidenceIEA
GeneRpl5Authority100503670Mapping file id100503670 NCBI fileEvidenceIEA
GeneRpl6Authority19988Mapping file id19988 NCBI fileEvidenceIEA
GeneRpl7Authority19989Mapping file id19989 NCBI fileEvidenceIEA
GeneRpl8Authority26961Mapping file id26961 NCBI fileEvidenceIEA
GeneRpl9Authority20005Mapping file id20005 NCBI fileEvidenceIEA
GeneRplp0Authority11837Mapping file id11837 NCBI fileEvidenceIEA
GeneRplp1Authority56040Mapping file id56040 NCBI fileEvidenceIEA
GeneRplp2Authority67186Mapping file id67186 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneTcf25Authority66855Mapping file id66855 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

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.