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.

Cell Cycle, Mitotic

R-MMU-69278 in Reactome release 97: under Cell Cycle, with 523 genes placed in it by the mapping files and 5 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-69278 (human), R-RNO-69278 (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 523 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 6
GenePsmb5Authority19173Mapping file id19173 NCBI fileEvidenceIEA
GenePsmb6Authority19175Mapping file id19175 NCBI fileEvidenceIEA
GenePsmb7Authority19177Mapping file id19177 NCBI fileEvidenceIEA
GenePsmc1Authority19179Mapping file id19179 NCBI fileEvidenceIEA
GenePsmc2Authority19181Mapping file id19181 NCBI fileEvidenceIEA
GenePsmc3Authority19182Mapping file id19182 NCBI fileEvidenceIEA
GenePsmc4Authority23996Mapping file id23996 NCBI fileEvidenceIEA
GenePsmc5Authority19184Mapping file id19184 NCBI fileEvidenceIEA
GenePsmc6Authority67089Mapping file id67089 NCBI fileEvidenceIEA
GenePsmd1Authority70247Mapping file id70247 NCBI fileEvidenceIEA
GenePsmd11Authority69077Mapping file id69077 NCBI fileEvidenceIEA
GenePsmd12Authority66997Mapping file id66997 NCBI fileEvidenceIEA
GenePsmd13Authority23997Mapping file id23997 NCBI fileEvidenceIEA
GenePsmd14Authority59029Mapping file id59029 NCBI fileEvidenceIEA
GenePsmd2Authority21762Mapping file id21762 NCBI fileEvidenceIEA
GenePsmd3Authority22123Mapping file id22123 NCBI fileEvidenceIEA
GenePsmd6Authority66413Mapping file id66413 NCBI fileEvidenceIEA
GenePsmd7Authority17463Mapping file id17463 NCBI fileEvidenceIEA
GenePsmd8Authority57296Mapping file id57296 NCBI fileEvidenceIEA
GenePtk6Authority20459Mapping file id20459 NCBI fileEvidenceIEA
GenePttg1Authority30939Mapping file id30939 NCBI fileEvidenceIEA
GeneRab1aAuthority19324Mapping file id19324 NCBI fileEvidenceIEA
GeneRab1bAuthority76308Mapping file id76308 NCBI fileEvidenceIEA
GeneRab2aAuthority59021Mapping file id59021 NCBI fileEvidenceIEA
GeneRab8aAuthority17274Mapping file id17274 NCBI fileEvidenceIEA
GeneRad21Authority19357Mapping file id19357 NCBI fileEvidenceIEA
GeneRae1Authority66679Mapping file id66679 NCBI fileEvidenceIEA
GeneRanAuthority19384Mapping file id19384 NCBI fileEvidenceIEA
GeneRanbp2Authority19386Mapping file id19386 NCBI fileEvidenceIEA
GeneRangap1Authority19387Mapping file id19387 NCBI fileEvidenceIEA
GeneRb1Authority19645Mapping file id19645 NCBI fileEvidenceIEA
GeneRbbp4Authority19646Mapping file id19646 NCBI fileEvidenceIEA
GeneRbl1Authority19650Mapping file id19650 NCBI fileEvidenceIEA
GeneRbl2Authority19651Mapping file id19651 NCBI fileEvidenceIEA
GeneRbm39Authority170791Mapping file id170791 NCBI fileEvidenceIEA
GeneRbx1Authority56438Mapping file id56438 NCBI fileEvidenceIEA
GeneRcc1Authority100088Mapping file id100088 NCBI fileEvidenceIEA
GeneRcc2Authority108911Mapping file id108911 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
GeneRps27Authority57294Mapping file id57294 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRps27rtAuthority100043813Mapping file id100043813 NCBI fileEvidenceIEA
GeneSdccag8Authority76816Mapping file id76816 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSeh1lAuthority72124Mapping file id72124 NCBI fileEvidenceIEA
GeneSetAuthority56086Mapping file id56086 NCBI fileEvidenceIEA
GeneSfi1Authority78887Mapping file id78887 NCBI fileEvidenceIEA
GeneSgo1Authority72415Mapping file id72415 NCBI fileEvidenceIEA
GeneSgo2aAuthority68549Mapping file id68549 NCBI fileEvidenceIEA
GeneSirt2Authority64383Mapping file id64383 NCBI fileEvidenceIEA
GeneSka1Authority66468Mapping file id66468 NCBI fileEvidenceIEA
GeneSka2Authority66140Mapping file id66140 NCBI fileEvidenceIEA
GeneSkp1Authority21402Mapping file id21402 NCBI fileEvidenceIEA
GeneSkp2Authority27401Mapping file id27401 NCBI fileEvidenceIEA
GeneSmc1aAuthority24061Mapping file id24061 NCBI fileEvidenceIEA
GeneSmc2Authority14211Mapping file id14211 NCBI fileEvidenceIEA
GeneSmc3Authority13006Mapping file id13006 NCBI fileEvidenceIEA
GeneSmc4Authority70099Mapping file id70099 NCBI fileEvidenceIEA
GeneSpastAuthority50850Mapping file id50850 NCBI fileEvidenceIEA
GeneSpc24Authority67629Mapping file id67629 NCBI fileEvidenceIEA
GeneSpc25Authority66442Mapping file id66442 NCBI fileEvidenceIEA
GeneSpdl1Authority70385Mapping file id70385 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneSsna1Authority68475Mapping file id68475 NCBI fileEvidenceIEA
GeneStag1Authority20842Mapping file id20842 NCBI fileEvidenceIEA
GeneStag2Authority20843Mapping file id20843 NCBI fileEvidenceIEA
GeneSumo1Authority22218Mapping file id22218 NCBI fileEvidenceIEA
GeneTaok1Authority216965Mapping file id216965 NCBI fileEvidenceIEA
GeneTfdp1Authority21781Mapping file id21781 NCBI fileEvidenceIEA
GeneTicrrAuthority77011Mapping file id77011 NCBI fileEvidenceIEA
GeneTprAuthority108989Mapping file id108989 NCBI fileEvidenceIEA
GeneTpx2Authority72119Mapping file id72119 NCBI fileEvidenceIEA
GeneTrp53Authority22059Mapping file id22059 NCBI fileEvidenceIEA
GeneTuba1aAuthority22142Mapping file id22142 NCBI fileEvidenceIEA
GeneTuba1bAuthority22143Mapping file id22143 NCBI fileEvidenceIEA
GeneTuba1cAuthority22146Mapping file id22146 NCBI fileEvidenceIEA
GeneTuba3aAuthority22144Mapping file id22144 NCBI fileEvidenceIEA
GeneTuba3bAuthority22147Mapping file id22147 NCBI fileEvidenceIEA
GeneTuba4aAuthority22145Mapping file id22145 NCBI fileEvidenceIEA
GeneTuba8Authority53857Mapping file id53857 NCBI fileEvidenceIEA
GeneTubal3Authority238463Mapping file id238463 NCBI fileEvidenceIEA
GeneTubb1Authority545486Mapping file id545486 NCBI fileEvidenceIEA
GeneTubb2aAuthority22151Mapping file id22151 NCBI fileEvidenceIEA
GeneTubb2bAuthority73710Mapping file id73710 NCBI fileEvidenceIEA
GeneTubb3Authority22152Mapping file id22152 NCBI fileEvidenceIEA
GeneTubb4aAuthority22153Mapping file id22153 NCBI fileEvidenceIEA
GeneTubb4bAuthority227613Mapping file id227613 NCBI fileEvidenceIEA
GeneTubb5Authority22154Mapping file id22154 NCBI fileEvidenceIEA
GeneTubb6Authority67951Mapping file id67951 NCBI fileEvidenceIEA
GeneTubg1Authority103733Mapping file id103733 NCBI fileEvidenceIEA
GeneTubg2Authority103768Mapping file id103768 NCBI fileEvidenceIEA
GeneTubgcp2Authority74237Mapping file id74237 NCBI fileEvidenceIEA
GeneTubgcp3Authority259279Mapping file id259279 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.