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.

Dual incision in TC-NER

R-MMU-6782135 in Reactome release 97: under Transcription-Coupled Nucleotide Excision Repair (TC-NER), with 63 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-6782135 (human), R-RNO-6782135 (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 63 genes in this mouse pathway; showing 1 to 63, 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
GeneAqrAuthority11834Mapping file id11834 NCBI fileEvidenceIEA
GeneCcnhAuthority66671Mapping file id66671 NCBI fileEvidenceIEA
GeneCdk7Authority12572Mapping file id12572 NCBI fileEvidenceIEA
GeneCul4aAuthority99375Mapping file id99375 NCBI fileEvidenceIEA
GeneCul4bAuthority72584Mapping file id72584 NCBI fileEvidenceIEA
GeneDdb1Authority13194Mapping file id13194 NCBI fileEvidenceIEA
GeneErcc1Authority13870Mapping file id13870 NCBI fileEvidenceIEA
GeneErcc2Authority13871Mapping file id13871 NCBI fileEvidenceIEA
GeneErcc3Authority13872Mapping file id13872 NCBI fileEvidenceIEA
GeneErcc4Authority50505Mapping file id50505 NCBI fileEvidenceIEA
GeneErcc5Authority22592Mapping file idENSMUSG00000026048 Ensembl fileEvidenceIEA
GeneErcc6Authority319955Mapping file id319955 NCBI fileEvidenceIEA
GeneErcc8Authority71991Mapping file id71991 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
GeneIsy1Authority57905Mapping file id57905 NCBI fileEvidenceIEA
GeneMnat1Authority17420Mapping file id17420 NCBI fileEvidenceIEA
GenePcnaAuthority18538Mapping file id18538 NCBI fileEvidenceIEA
GenePold1Authority18971Mapping file id18971 NCBI fileEvidenceIEA
GenePold2Authority18972Mapping file id18972 NCBI fileEvidenceIEA
GenePold3Authority67967Mapping file id67967 NCBI fileEvidenceIEA
GenePold4Authority69745Mapping file id69745 NCBI fileEvidenceIEA
GenePoleAuthority18973Mapping file id18973 NCBI fileEvidenceIEA
GenePole2Authority18974Mapping file id18974 NCBI fileEvidenceIEA
GenePole3Authority59001Mapping file id59001 NCBI fileEvidenceIEA
GenePole4Authority66979Mapping file id66979 NCBI fileEvidenceIEA
GenePolkAuthority27015Mapping file id27015 NCBI fileEvidenceIEA
GenePolr2aAuthority20020Mapping file id20020 NCBI fileEvidenceIEA
GenePolr2bAuthority231329Mapping file id231329 NCBI fileEvidenceIEA
GenePolr2cAuthority20021Mapping file id20021 NCBI fileEvidenceIEA
GenePolr2dAuthority69241Mapping file id69241 NCBI fileEvidenceIEA
GenePolr2eAuthority66420Mapping file id66420 NCBI fileEvidenceIEA
GenePolr2fAuthority69833Mapping file id69833 NCBI fileEvidenceIEA
GenePolr2gAuthority67710Mapping file id67710 NCBI fileEvidenceIEA
GenePolr2hAuthority245841Mapping file id245841 NCBI fileEvidenceIEA
GenePolr2iAuthority69920Mapping file id69920 NCBI fileEvidenceIEA
GenePolr2kAuthority17749Mapping file id17749 NCBI fileEvidenceIEA
GenePolr2lAuthority66491Mapping file id66491 NCBI fileEvidenceIEA
GenePpieAuthority56031Mapping file id56031 NCBI fileEvidenceIEA
GenePrpf19Authority28000Mapping file id28000 NCBI fileEvidenceIEA
GeneRbx1Authority56438Mapping file id56438 NCBI fileEvidenceIEA
GeneRfc1Authority19687Mapping file id19687 NCBI fileEvidenceIEA
GeneRfc2Authority19718Mapping file id19718 NCBI fileEvidenceIEA
GeneRfc3Authority69263Mapping file id69263 NCBI fileEvidenceIEA
GeneRfc4Authority106344Mapping file id106344 NCBI fileEvidenceIEA
GeneRfc5Authority72151Mapping file id72151 NCBI fileEvidenceIEA
GeneRpa1Authority68275Mapping file id68275 NCBI fileEvidenceIEA
GeneRpa2Authority19891Mapping file id19891 NCBI fileEvidenceIEA
GeneRpa3Authority68240Mapping file id68240 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneTcea1Authority21399Mapping file id21399 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUsp7Authority252870Mapping file id252870 NCBI fileEvidenceIEA
GeneUvssaAuthority71101Mapping file id71101 NCBI fileEvidenceIEA
GeneXab2Authority67439Mapping file id67439 NCBI fileEvidenceIEA
GeneXpaAuthority22590Mapping file id22590 NCBI fileEvidenceIEA
GeneZfp830Authority66983Mapping file id66983 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.