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

R-MMU-1640170 in Reactome release 97: a top-level pathway, with 616 genes placed in it by the mapping files and 4 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-1640170 (human), R-RNO-1640170 (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 616 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 7
GeneLin9Authority72568Mapping file id72568 NCBI fileEvidenceIEA
GeneLmnaAuthority16905Mapping file id16905 NCBI fileEvidenceIEA
GeneLmnb1Authority16906Mapping file id16906 NCBI fileEvidenceIEA
GeneLpin1Authority14245Mapping file id14245 NCBI fileEvidenceIEA
GeneLpin2Authority64898Mapping file id64898 NCBI fileEvidenceIEA
GeneLpin3Authority64899Mapping file id64899 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 NCBI fileEvidenceIEA
GeneMad1l1Authority17120Mapping file id17120 NCBI fileEvidenceIEA
GeneMad2l1Authority56150Mapping file id56150 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapre1Authority13589Mapping file id13589 NCBI fileEvidenceIEA
GeneMastlAuthority67121Mapping file id67121 NCBI fileEvidenceIEA
GeneMau2Authority74549Mapping file id74549 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
GeneMcph1Authority244329Mapping file id244329 NCBI fileEvidenceIEA
GeneMdc1Authority240087Mapping file id240087 NCBI fileEvidenceIEA
GeneMdm2Authority17246Mapping file id17246 NCBI fileEvidenceIEA
GeneMdm4Authority17248Mapping file id17248 NCBI fileEvidenceIEA
GeneMis12Authority67139Mapping file id67139 NCBI fileEvidenceIEA
GeneMis18aAuthority66578Mapping file id66578 NCBI fileEvidenceIEA
GeneMis18bp1Authority217653Mapping file id217653 NCBI fileEvidenceIEA
GeneMnat1Authority17420Mapping file id17420 NCBI fileEvidenceIEA
GeneMre11aAuthority17535Mapping file id17535 NCBI fileEvidenceIEA
GeneMzt1Authority76789Mapping file id76789 NCBI fileEvidenceIEA
GeneMzt2Authority72083Mapping file id72083 NCBI fileEvidenceIEA
GeneNbnAuthority27354Mapping file id27354 NCBI fileEvidenceIEA
GeneNcapd2Authority68298Mapping file id68298 NCBI fileEvidenceIEA
GeneNcapd3Authority78658Mapping file id78658 NCBI fileEvidenceIEA
GeneNcapgAuthority54392Mapping file id54392 NCBI fileEvidenceIEA
GeneNcapg2Authority76044Mapping file id76044 NCBI fileEvidenceIEA
GeneNcaphAuthority215387Mapping file id215387 NCBI fileEvidenceIEA
GeneNcaph2Authority52683Mapping file id52683 NCBI fileEvidenceIEA
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
GeneNek11Authority208583Mapping file id208583 NCBI fileEvidenceIEA
GeneNek2Authority18005Mapping file id18005 NCBI fileEvidenceIEA
GeneNek9Authority217718Mapping file id217718 NCBI fileEvidenceIEA
GeneNhp2Authority52530Mapping file id52530 NCBI fileEvidenceIEA
GeneNinlAuthority78177Mapping file id78177 NCBI fileEvidenceIEA
GeneNipblAuthority71175Mapping file id71175 NCBI fileEvidenceIEA
GeneNme7Authority171567Mapping file id171567 NCBI fileEvidenceIEA
GeneNop10Authority66181Mapping file id66181 NCBI fileEvidenceIEA
GeneNpm1Authority18148Mapping file id18148 NCBI fileEvidenceIEA
GeneNsd2Authority107823Mapping file id107823 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
GeneOip5Authority70645Mapping file id70645 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
GenePhf20Authority228829Mapping file id228829 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.