Skip to content
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.

G2/M Checkpoints

R-MMU-69481 in Reactome release 97: under Cell Cycle Checkpoints, with 154 genes placed in it by the mapping files and 3 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-69481 (human), R-RNO-69481 (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 154 genes in this mouse pathway; showing 1 to 100, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 2
GeneAbraxas1Authority70681Mapping file id70681 NCBI fileEvidenceIEA
GeneAdrm1Authority56436Mapping file id56436 NCBI fileEvidenceIEA
GeneAtmAuthority11920Mapping file id11920 NCBI fileEvidenceIEA
GeneAtripAuthority235610Mapping file id235610 NCBI fileEvidenceIEA
GeneBabam1Authority68251Mapping file id68251 NCBI fileEvidenceIEA
GeneBabam2Authority107976Mapping file id107976 NCBI fileEvidenceIEA
GeneBard1Authority12021Mapping file id12021 NCBI fileEvidenceIEA
GeneBlmAuthority12144Mapping file id12144 NCBI fileEvidenceIEA
GeneBrca1Authority12189Mapping file id12189 NCBI fileEvidenceIEA
GeneBrcc3Authority210766Mapping file id210766 NCBI fileEvidenceIEA
GeneBrip1Authority237911Mapping file id237911 NCBI fileEvidenceIEA
GeneCcna1Authority12427Mapping file id12427 NCBI fileEvidenceIEA
GeneCcna2Authority12428Mapping file id12428 NCBI fileEvidenceIEA
GeneCcnb1Authority268697Mapping file id268697 NCBI fileEvidenceIEA
GeneCcnb2Authority12442Mapping file id12442 NCBI fileEvidenceIEA
GeneCdc25aAuthority12530Mapping file id12530 NCBI fileEvidenceIEA
GeneCdc25cAuthority12532Mapping file id12532 NCBI fileEvidenceIEA
GeneCdc45Authority12544Mapping file id12544 NCBI fileEvidenceIEA
GeneCdc6Authority23834Mapping file id23834 NCBI fileEvidenceIEA
GeneCdc7Authority12545Mapping file id12545 NCBI fileEvidenceIEA
GeneCdk1Authority12534Mapping file id12534 NCBI fileEvidenceIEA
GeneCdk2Authority12566Mapping file id12566 NCBI fileEvidenceIEA
GeneChek1Authority12649Mapping file id12649 NCBI fileEvidenceIEA
GeneChek2Authority50883Mapping file id50883 NCBI fileEvidenceIEA
GeneClspnAuthority269582Mapping file id269582 NCBI fileEvidenceIEA
GeneDbf4Authority27214Mapping file id27214 NCBI fileEvidenceIEA
GeneDna2Authority327762Mapping file id327762 NCBI fileEvidenceIEA
GeneExo1Authority26909Mapping file id26909 NCBI fileEvidenceIEA
GeneGtse1Authority29870Mapping file id29870 NCBI fileEvidenceIEA
GeneH2axAuthority15270Mapping file id15270 NCBI fileEvidenceIEA
GeneH2bc1Authority319177Mapping file id319177 NCBI fileEvidenceIEA
GeneH2bc11Authority319183Mapping file id319183 NCBI fileEvidenceIEA
GeneH2bc12Authority319184Mapping file id319184 NCBI fileEvidenceIEA
GeneH2bc13Authority319185Mapping file id319185 NCBI fileEvidenceIEA
GeneH2bc15Authority319187Mapping file id319187 NCBI fileEvidenceIEA
GeneH2bc18Authority319189Mapping file id319189 NCBI fileEvidenceIEA
GeneH2bc21Authority319190Mapping file id319190 NCBI fileEvidenceIEA
GeneH2bc22Authority319188Mapping file id319188 NCBI fileEvidenceIEA
GeneH2bc23Authority665596Mapping file idENSMUSG00000069307 Ensembl fileEvidenceIEA
GeneH2bc24Authority665622Mapping file idENSMUSG00000069303 Ensembl fileEvidenceIEA
GeneH2bc26Authority382522Mapping file id382522 NCBI fileEvidenceIEA
GeneH2bc27Authority78303Mapping file id78303 NCBI fileEvidenceIEA
GeneH2bc3Authority319178Mapping file id319178 NCBI fileEvidenceIEA
GeneH2bc4Authority68024Mapping file id68024 NCBI fileEvidenceIEA
GeneH2bc6Authority319179Mapping file id319179 NCBI fileEvidenceIEA
GeneH2bc7Authority319180Mapping file id319180 NCBI fileEvidenceIEA
GeneH2bc8Authority319181Mapping file id319181 NCBI fileEvidenceIEA
GeneH2bc9Authority319182Mapping file id319182 NCBI fileEvidenceIEA
GeneH3f4Authority382523Mapping file id382523 NCBI fileEvidenceIEA
GeneH4c1Authority326619Mapping file id326619 NCBI fileEvidenceIEA
GeneH4c11Authority319159Mapping file id319159 NCBI fileEvidenceIEA
GeneH4c12Authority319160Mapping file id319160 NCBI fileEvidenceIEA
GeneH4c14Authority97122Mapping file id97122 NCBI fileEvidenceIEA
GeneH4c16Authority320332Mapping file id320332 NCBI fileEvidenceIEA
GeneH4c17Authority100041230Mapping file id100041230 NCBI fileEvidenceIEA
GeneH4c18Authority319161Mapping file id319161 NCBI fileEvidenceIEA
GeneH4c2Authority326620Mapping file id326620 NCBI fileEvidenceIEA
GeneH4c3Authority319155Mapping file id319155 NCBI fileEvidenceIEA
GeneH4c4Authority319156Mapping file id319156 NCBI fileEvidenceIEA
GeneH4c6Authority319157Mapping file id319157 NCBI fileEvidenceIEA
GeneH4c8Authority69386Mapping file id69386 NCBI fileEvidenceIEA
GeneH4c9Authority319158Mapping file id319158 NCBI fileEvidenceIEA
GeneHerc2Authority15204Mapping file id15204 NCBI fileEvidenceIEA
GeneHus1Authority15574Mapping file id15574 NCBI fileEvidenceIEA
GeneKat5Authority81601Mapping file id81601 NCBI fileEvidenceIEA
GeneMcm10Authority70024Mapping file id70024 NCBI fileEvidenceIEA
GeneMcm2Authority17216Mapping file id17216 NCBI fileEvidenceIEA
GeneMcm3Authority17215Mapping file id17215 NCBI fileEvidenceIEA
GeneMcm4Authority17217Mapping file id17217 NCBI fileEvidenceIEA
GeneMcm5Authority17218Mapping file id17218 NCBI fileEvidenceIEA
GeneMcm6Authority17219Mapping file id17219 NCBI fileEvidenceIEA
GeneMcm7Authority17220Mapping file id17220 NCBI fileEvidenceIEA
GeneMcm8Authority66634Mapping file id66634 NCBI fileEvidenceIEA
GeneMdc1Authority240087Mapping file id240087 NCBI fileEvidenceIEA
GeneMre11aAuthority17535Mapping file id17535 NCBI fileEvidenceIEA
GeneNbnAuthority27354Mapping file id27354 NCBI fileEvidenceIEA
GeneNsd2Authority107823Mapping file id107823 NCBI fileEvidenceIEA
GeneOrc1Authority18392Mapping file id18392 NCBI fileEvidenceIEA
GeneOrc2Authority18393Mapping file id18393 NCBI fileEvidenceIEA
GeneOrc3Authority50793Mapping file id50793 NCBI fileEvidenceIEA
GeneOrc4Authority26428Mapping file id26428 NCBI fileEvidenceIEA
GeneOrc5Authority26429Mapping file id26429 NCBI fileEvidenceIEA
GeneOrc6Authority56452Mapping file idENSMUSG00000031697 Ensembl fileEvidenceIEA
GenePias4Authority59004Mapping file id59004 NCBI fileEvidenceIEA
GenePkmyt1Authority268930Mapping file id268930 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

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.