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

Genes Reactome places in this mouse pathway, page 4 of 6
GeneNdc1Authority72787Mapping file id72787 NCBI fileEvidenceIEA
GeneNdc80Authority67052Mapping file id67052 NCBI fileEvidenceIEA
GeneNde1Authority67203Mapping file id67203 NCBI fileEvidenceIEA
GeneNdel1Authority83431Mapping file id83431 NCBI fileEvidenceIEA
GeneNedd1Authority17997Mapping file id17997 NCBI fileEvidenceIEA
GeneNek2Authority18005Mapping file id18005 NCBI fileEvidenceIEA
GeneNek9Authority217718Mapping file id217718 NCBI fileEvidenceIEA
GeneNinlAuthority78177Mapping file id78177 NCBI fileEvidenceIEA
GeneNipblAuthority71175Mapping file id71175 NCBI fileEvidenceIEA
GeneNme7Authority171567Mapping file id171567 NCBI fileEvidenceIEA
GeneNsl1Authority381318Mapping file idENSMUSG00000062510 Ensembl fileEvidenceIEA
GeneNudcAuthority18221Mapping file id18221 NCBI fileEvidenceIEA
GeneNuf2Authority66977Mapping file id66977 NCBI fileEvidenceIEA
GeneNuma1Authority101706Mapping file id101706 NCBI fileEvidenceIEA
GeneNup107Authority103468Mapping file id103468 NCBI fileEvidenceIEA
GeneNup133Authority234865Mapping file id234865 NCBI fileEvidenceIEA
GeneNup153Authority218210Mapping file id218210 NCBI fileEvidenceIEA
GeneNup155Authority170762Mapping file id170762 NCBI fileEvidenceIEA
GeneNup160Authority59015Mapping file id59015 NCBI fileEvidenceIEA
GeneNup188Authority227699Mapping file id227699 NCBI fileEvidenceIEA
GeneNup205Authority70699Mapping file id70699 NCBI fileEvidenceIEA
GeneNup210Authority54563Mapping file id54563 NCBI fileEvidenceIEA
GeneNup214Authority227720Mapping file id227720 NCBI fileEvidenceIEA
GeneNup35Authority69482Mapping file id69482 NCBI fileEvidenceIEA
GeneNup37Authority69736Mapping file id69736 NCBI fileEvidenceIEA
GeneNup42Authority231042Mapping file id231042 NCBI fileEvidenceIEA
GeneNup43Authority69912Mapping file id69912 NCBI fileEvidenceIEA
GeneNup50Authority18141Mapping file id18141 NCBI fileEvidenceIEA
GeneNup54Authority269113Mapping file id269113 NCBI fileEvidenceIEA
GeneNup58Authority71844Mapping file id71844 NCBI fileEvidenceIEA
GeneNup62Authority18226Mapping file id18226 NCBI fileEvidenceIEA
GeneNup85Authority445007Mapping file id445007 NCBI fileEvidenceIEA
GeneNup88Authority19069Mapping file id19069 NCBI fileEvidenceIEA
GeneNup93Authority71805Mapping file id71805 NCBI fileEvidenceIEA
GeneNup98Authority269966Mapping file id269966 NCBI fileEvidenceIEA
GeneObi1Authority72486Mapping file id72486 NCBI fileEvidenceIEA
GeneOdf2Authority18286Mapping file id18286 NCBI fileEvidenceIEA
GeneOfd1Authority237222Mapping file id237222 NCBI fileEvidenceIEA
GeneOptnAuthority71648Mapping file id71648 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
GenePafah1b1Authority18472Mapping file id18472 NCBI fileEvidenceIEA
GenePcm1Authority18536Mapping file id18536 NCBI fileEvidenceIEA
GenePcnaAuthority18538Mapping file id18538 NCBI fileEvidenceIEA
GenePcntAuthority18541Mapping file id18541 NCBI fileEvidenceIEA
GenePds5aAuthority71521Mapping file idENSMUSG00000029202 Ensembl fileEvidenceIEA
GenePds5bAuthority100710Mapping file id100710 NCBI fileEvidenceIEA
GenePhlda1Authority21664Mapping file id21664 NCBI fileEvidenceIEA
GenePkmyt1Authority268930Mapping file id268930 NCBI fileEvidenceIEA
GenePlk1Authority18817Mapping file id18817 NCBI fileEvidenceIEA
GenePlk4Authority20873Mapping file id20873 NCBI fileEvidenceIEA
GenePmf1Authority67037Mapping file id67037 NCBI fileEvidenceIEA
GenePola1Authority18968Mapping file id18968 NCBI fileEvidenceIEA
GenePola2Authority18969Mapping file id18969 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
GenePom121Authority107939Mapping file id107939 NCBI fileEvidenceIEA
GenePpme1Authority72590Mapping file id72590 NCBI fileEvidenceIEA
GenePpp1cbAuthority19046Mapping file id19046 NCBI fileEvidenceIEA
GenePpp1ccAuthority19047Mapping file id19047 NCBI fileEvidenceIEA
GenePpp1r12aAuthority17931Mapping file id17931 NCBI fileEvidenceIEA
GenePpp1r12bAuthority329251Mapping file id329251 NCBI fileEvidenceIEA
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r2aAuthority71978Mapping file id71978 NCBI fileEvidenceIEA
GenePpp2r3dAuthority19054Mapping file idENSMUSG00000093803 Ensembl fileEvidenceIEA
GenePpp2r5aAuthority226849Mapping file id226849 NCBI fileEvidenceIEA
GenePpp2r5bAuthority225849Mapping file id225849 NCBI fileEvidenceIEA
GenePpp2r5cAuthority26931Mapping file id26931 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GenePpp2r5eAuthority26932Mapping file id26932 NCBI fileEvidenceIEA
GenePrim1Authority19075Mapping file id19075 NCBI fileEvidenceIEA
GenePrim2Authority19076Mapping file id19076 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkar2bAuthority19088Mapping file id19088 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GenePrkcbAuthority18751Mapping file id18751 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

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.