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 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 7
GeneEif4eAuthority13684Mapping file id13684 NCBI fileEvidenceIEA
GeneEif4g1Authority208643Mapping file id208643 NCBI fileEvidenceIEA
GeneElavl1Authority15568Mapping file id15568 NCBI fileEvidenceIEA
GeneEmg1Authority14791Mapping file id14791 NCBI fileEvidenceIEA
GeneErcc2Authority13871Mapping file id13871 NCBI fileEvidenceIEA
GeneErcc3Authority13872Mapping file id13872 NCBI fileEvidenceIEA
GeneEri1Authority67276Mapping file id67276 NCBI fileEvidenceIEA
GeneEtf1Authority225363Mapping file id225363 NCBI fileEvidenceIEA
GeneExosc1Authority66583Mapping file id66583 NCBI fileEvidenceIEA
GeneExosc10Authority50912Mapping file id50912 NCBI fileEvidenceIEA
GeneExosc2Authority227715Mapping file id227715 NCBI fileEvidenceIEA
GeneExosc3Authority66362Mapping file id66362 NCBI fileEvidenceIEA
GeneExosc4Authority109075Mapping file id109075 NCBI fileEvidenceIEA
GeneExosc5Authority27998Mapping file id27998 NCBI fileEvidenceIEA
GeneExosc6Authority72544Mapping file id72544 NCBI fileEvidenceIEA
GeneExosc7Authority66446Mapping file id66446 NCBI fileEvidenceIEA
GeneExosc8Authority69639Mapping file id69639 NCBI fileEvidenceIEA
GeneExosc9Authority50911Mapping file id50911 NCBI fileEvidenceIEA
GeneFam32aAuthority67922Mapping file id67922 NCBI fileEvidenceIEA
GeneFam50aAuthority108160Mapping file id108160 NCBI fileEvidenceIEA
GeneFauAuthority14109Mapping file id14109 NCBI fileEvidenceIEA
GeneFblAuthority14113Mapping file id14113 NCBI fileEvidenceIEA
GeneFcf1Authority73736Mapping file id73736 NCBI fileEvidenceIEA
GeneFip1l1Authority66899Mapping file id66899 NCBI fileEvidenceIEA
GeneFtsj3Authority56095Mapping file id56095 NCBI fileEvidenceIEA
GeneFusAuthority233908Mapping file id233908 NCBI fileEvidenceIEA
GeneFyttd1Authority69823Mapping file id69823 NCBI fileEvidenceIEA
GeneGcfc2Authority330361Mapping file id330361 NCBI fileEvidenceIEA
GeneGemin2Authority66603Mapping file id66603 NCBI fileEvidenceIEA
GeneGemin4Authority276919Mapping file id276919 NCBI fileEvidenceIEA
GeneGemin5Authority216766Mapping file id216766 NCBI fileEvidenceIEA
GeneGemin6Authority67242Mapping file id67242 NCBI fileEvidenceIEA
GeneGemin7Authority69731Mapping file id69731 NCBI fileEvidenceIEA
GeneGemin8Authority237221Mapping file id237221 NCBI fileEvidenceIEA
GeneGle1Authority74412Mapping file id74412 NCBI fileEvidenceIEA
GeneGnl3Authority30877Mapping file id30877 NCBI fileEvidenceIEA
GeneGpatch1Authority67471Mapping file id67471 NCBI fileEvidenceIEA
GeneGpkowAuthority209416Mapping file id209416 NCBI fileEvidenceIEA
GeneGspt1Authority14852Mapping file id14852 NCBI fileEvidenceIEA
GeneGspt2Authority14853Mapping file id14853 NCBI fileEvidenceIEA
GeneGtf2f1Authority98053Mapping file id98053 NCBI fileEvidenceIEA
GeneGtf2f2Authority68705Mapping file id68705 NCBI fileEvidenceIEA
GeneGtf2h1Authority14884Mapping file id14884 NCBI fileEvidenceIEA
GeneGtf2h2Authority23894Mapping file id23894 NCBI fileEvidenceIEA
GeneGtf2h3Authority209357Mapping file id209357 NCBI fileEvidenceIEA
GeneGtf2h4Authority14885Mapping file id14885 NCBI fileEvidenceIEA
GeneGtf2h5Authority66467Mapping file id66467 NCBI fileEvidenceIEA
GeneHbs1lAuthority56422Mapping file id56422 NCBI fileEvidenceIEA
GeneHeatr1Authority217995Mapping file id217995 NCBI fileEvidenceIEA
GeneHnrnpa1Authority15382Mapping file id15382 NCBI fileEvidenceIEA
GeneHnrnpa2b1Authority53379Mapping file id53379 NCBI fileEvidenceIEA
GeneHnrnpa3Authority229279Mapping file id229279 NCBI fileEvidenceIEA
GeneHnrnpcAuthority15381Mapping file id15381 NCBI fileEvidenceIEA
GeneHnrnpdAuthority11991Mapping file id11991 NCBI fileEvidenceIEA
GeneHnrnpfAuthority98758Mapping file id98758 NCBI fileEvidenceIEA
GeneHnrnph1Authority59013Mapping file id59013 NCBI fileEvidenceIEA
GeneHnrnph2Authority56258Mapping file id56258 NCBI fileEvidenceIEA
GeneHnrnpkAuthority15387Mapping file id15387 NCBI fileEvidenceIEA
GeneHnrnplAuthority15388Mapping file id15388 NCBI fileEvidenceIEA
GeneHnrnprAuthority74326Mapping file id74326 NCBI fileEvidenceIEA
GeneHnrnpuAuthority51810Mapping file id51810 NCBI fileEvidenceIEA
GeneHspa1aAuthority193740Mapping file id193740 NCBI fileEvidenceIEA
GeneHspa1bAuthority15511Mapping file id15511 NCBI fileEvidenceIEA
GeneHspa8Authority15481Mapping file id15481 NCBI fileEvidenceIEA
GeneHspb1Authority15507Mapping file id15507 NCBI fileEvidenceIEA
GeneHtatsf1Authority72459Mapping file id72459 NCBI fileEvidenceIEA
GeneIkAuthority24010Mapping file id24010 NCBI fileEvidenceIEA
GeneImp3Authority102462Mapping file id102462 NCBI fileEvidenceIEA
GeneImp4Authority27993Mapping file id27993 NCBI fileEvidenceIEA
GeneIsg20l2Authority229504Mapping file id229504 NCBI fileEvidenceIEA
GeneIsy1Authority57905Mapping file id57905 NCBI fileEvidenceIEA
GeneKhsrpAuthority16549Mapping file id16549 NCBI fileEvidenceIEA
GeneKrr1Authority52705Mapping file id52705 NCBI fileEvidenceIEA
GeneLas1lAuthority76130Mapping file id76130 NCBI fileEvidenceIEA
GeneLeng1Authority69757Mapping file id69757 NCBI fileEvidenceIEA
GeneLsm1Authority67207Mapping file id67207 NCBI fileEvidenceIEA
GeneLsm10Authority116748Mapping file id116748 NCBI fileEvidenceIEA
GeneLsm11Authority72290Mapping file id72290 NCBI fileEvidenceIEA
GeneLsm2Authority27756Mapping file id27756 NCBI fileEvidenceIEA
GeneLsm3Authority67678Mapping file id67678 NCBI fileEvidenceIEA
GeneLsm4Authority50783Mapping file id50783 NCBI fileEvidenceIEA
GeneLsm5Authority66373Mapping file id66373 NCBI fileEvidenceIEA
GeneLsm6Authority78651Mapping file id78651 NCBI fileEvidenceIEA
GeneLsm7Authority66094Mapping file id66094 NCBI fileEvidenceIEA
GeneLsm8Authority76522Mapping file id76522 NCBI fileEvidenceIEA
GeneLtv1Authority353258Mapping file id353258 NCBI fileEvidenceIEA
GeneLuc7l3Authority67684Mapping file id67684 NCBI fileEvidenceIEA
GeneMagohAuthority17149Mapping file id17149 NCBI fileEvidenceIEA
GeneMagohbAuthority66441Mapping file id66441 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMettl14Authority210529Mapping file id210529 NCBI fileEvidenceIEA
GeneMettl3Authority56335Mapping file id56335 NCBI fileEvidenceIEA
GeneMfap1aAuthority67532Mapping file id67532 NCBI fileEvidenceIEA
GeneMfap1bAuthority100034361Mapping file id100034361 NCBI fileEvidenceIEA
GeneMnat1Authority17420Mapping file id17420 NCBI fileEvidenceIEA
GeneMphosph10Authority67973Mapping file id67973 NCBI fileEvidenceIEA
GeneMphosph6Authority68533Mapping file id68533 NCBI fileEvidenceIEA
GeneMtrexAuthority72198Mapping file id72198 NCBI fileEvidenceIEA
GeneNcbp1Authority433702Mapping file id433702 NCBI fileEvidenceIEA
GeneNcbp2Authority68092Mapping file id68092 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.