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.

Metabolism of RNA

R-MMU-8953854 in Reactome release 97: a top-level pathway, with 612 genes placed in it by the mapping files and 11 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-8953854 (human), R-RNO-8953854 (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 612 genes in this mouse pathway; showing 401 to 500, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 5 of 7
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
GeneRpp14Authority67053Mapping file id67053 NCBI fileEvidenceIEA
GeneRpp21Authority67676Mapping file id67676 NCBI fileEvidenceIEA
GeneRpp25Authority102614Mapping file id102614 NCBI fileEvidenceIEA
GeneRpp30Authority54364Mapping file id54364 NCBI fileEvidenceIEA
GeneRpp38Authority227522Mapping file idENSMUSG00000049950 Ensembl fileEvidenceIEA
GeneRpp40Authority208366Mapping file id208366 NCBI fileEvidenceIEA
GeneRps10Authority67097Mapping file id67097 NCBI fileEvidenceIEA
GeneRps11Authority27207Mapping file id27207 NCBI fileEvidenceIEA
GeneRps12Authority20042Mapping file id20042 NCBI fileEvidenceIEA
GeneRps13Authority68052Mapping file id68052 NCBI fileEvidenceIEA
GeneRps14Authority20044Mapping file id20044 NCBI fileEvidenceIEA
GeneRps15Authority20054Mapping file id20054 NCBI fileEvidenceIEA
GeneRps15aAuthority267019Mapping file id267019 NCBI fileEvidenceIEA
GeneRps16Authority20055Mapping file id20055 NCBI fileEvidenceIEA
GeneRps17Authority20068Mapping file id20068 NCBI fileEvidenceIEA
GeneRps18Authority20084Mapping file id20084 NCBI fileEvidenceIEA
GeneRps19Authority20085Mapping file id20085 NCBI fileEvidenceIEA
GeneRps2Authority16898Mapping file id16898 NCBI fileEvidenceIEA
GeneRps20Authority67427Mapping file id67427 NCBI fileEvidenceIEA
GeneRps21Authority66481Mapping file id66481 NCBI fileEvidenceIEA
GeneRps23Authority66475Mapping file id66475 NCBI fileEvidenceIEA
GeneRps24Authority20088Mapping file id20088 NCBI fileEvidenceIEA
GeneRps25Authority75617Mapping file id75617 NCBI fileEvidenceIEA
GeneRps26Authority27370Mapping file id27370 NCBI fileEvidenceIEA
GeneRps27Authority57294Mapping file id57294 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRps27lAuthority67941Mapping file id67941 NCBI fileEvidenceIEA
GeneRps27rtAuthority100043813Mapping file id100043813 NCBI fileEvidenceIEA
GeneRps28Authority54127Mapping file id54127 NCBI fileEvidenceIEA
GeneRps29Authority20090Mapping file id20090 NCBI fileEvidenceIEA
GeneRps3Authority27050Mapping file id27050 NCBI fileEvidenceIEA
GeneRps3a1Authority20091Mapping file id20091 NCBI fileEvidenceIEA
GeneRps4xAuthority20102Mapping file id20102 NCBI fileEvidenceIEA
GeneRps5Authority20103Mapping file id20103 NCBI fileEvidenceIEA
GeneRps6Authority20104Mapping file id20104 NCBI fileEvidenceIEA
GeneRps7Authority20115Mapping file id20115 NCBI fileEvidenceIEA
GeneRps8Authority20116Mapping file id20116 NCBI fileEvidenceIEA
GeneRps9Authority76846Mapping file id76846 NCBI fileEvidenceIEA
GeneRpsaAuthority16785Mapping file id16785 NCBI fileEvidenceIEA
GeneRrp36Authority224823Mapping file id224823 NCBI fileEvidenceIEA
GeneRrp7aAuthority74778Mapping file id74778 NCBI fileEvidenceIEA
GeneRrp9Authority27966Mapping file id27966 NCBI fileEvidenceIEA
GeneSap18Authority20220Mapping file id20220 NCBI fileEvidenceIEA
GeneSarnpAuthority66118Mapping file id66118 NCBI fileEvidenceIEA
GeneSart1Authority20227Mapping file id20227 NCBI fileEvidenceIEA
GeneSde2Authority208768Mapping file id208768 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSeh1lAuthority72124Mapping file id72124 NCBI fileEvidenceIEA
GeneSenp3Authority80886Mapping file id80886 NCBI fileEvidenceIEA
GeneSetAuthority56086Mapping file id56086 NCBI fileEvidenceIEA
GeneSf1Authority22668Mapping file idENSMUSG00000024949 Ensembl fileEvidenceIEA
GeneSf3a1Authority67465Mapping file id67465 NCBI fileEvidenceIEA
GeneSf3a2Authority20222Mapping file idENSMUSG00000020211 Ensembl fileEvidenceIEA
GeneSf3a3Authority75062Mapping file id75062 NCBI fileEvidenceIEA
GeneSf3b1Authority81898Mapping file idENSMUSG00000025982 Ensembl fileEvidenceIEA
GeneSf3b2Authority319322Mapping file id319322 NCBI fileEvidenceIEA
GeneSf3b3Authority101943Mapping file id101943 NCBI fileEvidenceIEA
GeneSf3b4Authority107701Mapping file id107701 NCBI fileEvidenceIEA
GeneSf3b5Authority66125Mapping file id66125 NCBI fileEvidenceIEA
GeneSkic2Authority108077Mapping file id108077 NCBI fileEvidenceIEA
GeneSkic3Authority218343Mapping file id218343 NCBI fileEvidenceIEA
GeneSkic8Authority66317Mapping file id66317 NCBI fileEvidenceIEA
GeneSlbpAuthority20492Mapping file id20492 NCBI fileEvidenceIEA
GeneSlu7Authority193116Mapping file id193116 NCBI fileEvidenceIEA
GeneSmg1Authority233789Mapping file id233789 NCBI fileEvidenceIEA
GeneSmg5Authority229512Mapping file id229512 NCBI fileEvidenceIEA
GeneSmg6Authority103677Mapping file id103677 NCBI fileEvidenceIEA
GeneSmg7Authority226517Mapping file id226517 NCBI fileEvidenceIEA
GeneSmg8Authority74133Mapping file id74133 NCBI fileEvidenceIEA
GeneSmg9Authority71997Mapping file id71997 NCBI fileEvidenceIEA
GeneSmn1Authority20595Mapping file id20595 NCBI fileEvidenceIEA
GeneSmndc1Authority76479Mapping file id76479 NCBI fileEvidenceIEA
GeneSmu1Authority74255Mapping file id74255 NCBI fileEvidenceIEA
GeneSnip1Authority76793Mapping file id76793 NCBI fileEvidenceIEA
GeneSnrnp200Authority320632Mapping file id320632 NCBI fileEvidenceIEA
GeneSnrnp25Authority78372Mapping file id78372 NCBI fileEvidenceIEA
GeneSnrnp27Authority66618Mapping file id66618 NCBI fileEvidenceIEA
GeneSnrnp35Authority76167Mapping file id76167 NCBI fileEvidenceIEA
GeneSnrnp40Authority66585Mapping file id66585 NCBI fileEvidenceIEA
GeneSnrnp48Authority67797Mapping file id67797 NCBI fileEvidenceIEA
GeneSnrnp70Authority20637Mapping file id20637 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.