Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Nuclear RNA decay

R-HSA-9930044 in Reactome release 97: under Metabolism of RNA, with 35 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-MMU-9930044 (mouse), R-RNO-9930044 (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.

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. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [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 human pathway

The mapping files place 35 genes in this human pathway; showing 1 to 35, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneC1DAuthorityHGNC:29911Mapping file id10438 NCBI fileEvidenceTAS
GeneDIS3AuthorityHGNC:20604Mapping file id22894 NCBI fileEvidenceTAS
GeneDXOAuthorityHGNC:2992Mapping file id1797 NCBI fileEvidenceIEA
GeneEXOSC1AuthorityHGNC:17286Mapping file id51013 NCBI fileEvidenceTAS
GeneEXOSC10AuthorityHGNC:9138Mapping file id5394 NCBI fileEvidenceTAS
GeneEXOSC2AuthorityHGNC:17097Mapping file id23404 NCBI fileEvidenceTAS
GeneEXOSC3AuthorityHGNC:17944Mapping file id51010 NCBI fileEvidenceTAS
GeneEXOSC4AuthorityHGNC:18189Mapping file id54512 NCBI fileEvidenceTAS
GeneEXOSC5AuthorityHGNC:24662Mapping file id56915 NCBI fileEvidenceTAS
GeneEXOSC6AuthorityHGNC:19055Mapping file id118460 NCBI fileEvidenceTAS
GeneEXOSC7AuthorityHGNC:28112Mapping file id23016 NCBI fileEvidenceTAS
GeneEXOSC8AuthorityHGNC:17035Mapping file id11340 NCBI fileEvidenceTAS
GeneEXOSC9AuthorityHGNC:9137Mapping file id5393 NCBI fileEvidenceTAS
GeneMPHOSPH6AuthorityHGNC:7214Mapping file id10200 NCBI fileEvidenceTAS
GeneMTREXAuthorityHGNC:18734Mapping file id23517 NCBI fileEvidenceTAS
GeneNCBP1AuthorityHGNC:7658Mapping file id4686 NCBI fileEvidenceTAS
GeneNCBP2AuthorityHGNC:7659Mapping file id22916 NCBI fileEvidenceTAS
GenePABPN1AuthorityHGNC:8565Mapping file id8106 NCBI fileEvidenceTAS
GenePAPOLGAuthorityHGNC:14982Mapping file id64895 NCBI fileEvidenceTAS
GeneRBM26AuthorityHGNC:20327Mapping file id64062 NCBI fileEvidenceTAS
GeneRBM27AuthorityHGNC:29243Mapping file id54439 NCBI fileEvidenceTAS
GeneRBM7AuthorityHGNC:9904Mapping file id10179 NCBI fileEvidenceTAS
GeneSRRTAuthorityHGNC:24101Mapping file id51593 NCBI fileEvidenceTAS
GeneTENT4AAuthorityHGNC:16705Mapping file id11044 NCBI fileEvidenceTAS
GeneTENT4BAuthorityHGNC:30758Mapping file id64282 NCBI fileEvidenceTAS
GeneWDR82AuthorityHGNC:28826Mapping file id80335 NCBI fileEvidenceTAS
GeneXRN2AuthorityHGNC:12836Mapping file id22803 NCBI fileEvidenceIEA
GeneYTHDC1AuthorityHGNC:30626Mapping file id91746 NCBI fileEvidenceTAS
GeneYTHDC2AuthorityHGNC:24721Mapping file id64848 NCBI fileEvidenceTAS
GeneZC3H18AuthorityHGNC:25091Mapping file id124245 NCBI fileEvidenceTAS
GeneZC3H3AuthorityHGNC:28972Mapping file id23144 NCBI fileEvidenceTAS
GeneZC3H4AuthorityHGNC:17808Mapping file id23211 NCBI fileEvidenceTAS
GeneZCCHC7AuthorityHGNC:26209Mapping file id84186 NCBI fileEvidenceTAS
GeneZCCHC8AuthorityHGNC:25265Mapping file id55596 NCBI fileEvidenceTAS
GeneZFC3H1AuthorityHGNC:28328Mapping file id196441 NCBI fileEvidenceTAS

Evidence codes on this page: IEA, TAS, 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: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human 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 human 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.