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.

Mitotic G1 phase and G1/S transition

R-MMU-453279 in Reactome release 97: under Cell Cycle, Mitotic, with 121 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-453279 (human), R-RNO-453279 (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 121 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
GeneAbl1Authority11350Mapping file id11350 NCBI fileEvidenceIEA
GeneAdrm1Authority56436Mapping file id56436 NCBI fileEvidenceIEA
GeneAkt1Authority11651Mapping file id11651 NCBI fileEvidenceIEA
GeneAkt2Authority11652Mapping file id11652 NCBI fileEvidenceIEA
GeneAkt3Authority23797Mapping file id23797 NCBI fileEvidenceIEA
GeneCables1Authority63955Mapping file id63955 NCBI fileEvidenceIEA
GeneCcna1Authority12427Mapping file id12427 NCBI fileEvidenceIEA
GeneCcna2Authority12428Mapping file id12428 NCBI fileEvidenceIEA
GeneCcnd1Authority12443Mapping file id12443 NCBI fileEvidenceIEA
GeneCcnd2Authority12444Mapping file id12444 NCBI fileEvidenceIEA
GeneCcnd3Authority12445Mapping file id12445 NCBI fileEvidenceIEA
GeneCcne1Authority12447Mapping file id12447 NCBI fileEvidenceIEA
GeneCcne2Authority12448Mapping file id12448 NCBI fileEvidenceIEA
GeneCcnhAuthority66671Mapping file id66671 NCBI fileEvidenceIEA
GeneCdc25aAuthority12530Mapping file id12530 NCBI fileEvidenceIEA
GeneCdc45Authority12544Mapping file id12544 NCBI fileEvidenceIEA
GeneCdc6Authority23834Mapping file id23834 NCBI fileEvidenceIEA
GeneCdc7Authority12545Mapping file id12545 NCBI fileEvidenceIEA
GeneCdk2Authority12566Mapping file id12566 NCBI fileEvidenceIEA
GeneCdk4Authority12567Mapping file id12567 NCBI fileEvidenceIEA
GeneCdk6Authority12571Mapping file id12571 NCBI fileEvidenceIEA
GeneCdk7Authority12572Mapping file id12572 NCBI fileEvidenceIEA
GeneCdkn1aAuthority12575Mapping file id12575 NCBI fileEvidenceIEA
GeneCdkn1bAuthority12576Mapping file id12576 NCBI fileEvidenceIEA
GeneCdkn1cAuthority12577Mapping file id12577 NCBI fileEvidenceIEA
GeneCdkn2bAuthority12579Mapping file id12579 NCBI fileEvidenceIEA
GeneCdt1Authority67177Mapping file id67177 NCBI fileEvidenceIEA
GeneCks1bAuthority54124Mapping file id54124 NCBI fileEvidenceIEA
GeneCul1Authority26965Mapping file id26965 NCBI fileEvidenceIEA
GeneDbf4Authority27214Mapping file id27214 NCBI fileEvidenceIEA
GeneDyrk1aAuthority13548Mapping file id13548 NCBI fileEvidenceIEA
GeneE2f1Authority13555Mapping file id13555 NCBI fileEvidenceIEA
GeneE2f2Authority242705Mapping file id242705 NCBI fileEvidenceIEA
GeneE2f3Authority13557Mapping file id13557 NCBI fileEvidenceIEA
GeneE2f4Authority104394Mapping file id104394 NCBI fileEvidenceIEA
GeneE2f5Authority13559Mapping file id13559 NCBI fileEvidenceIEA
GeneGmnnAuthority57441Mapping file id57441 NCBI fileEvidenceIEA
GeneHdac1Authority433759Mapping file id433759 NCBI fileEvidenceIEA
GeneJak2Authority16452Mapping file id16452 NCBI fileEvidenceIEA
GeneLin37Authority75660Mapping file id75660 NCBI fileEvidenceIEA
GeneLin52Authority217708Mapping file id217708 NCBI fileEvidenceIEA
GeneLin54Authority231506Mapping file id231506 NCBI fileEvidenceIEA
GeneLin9Authority72568Mapping file id72568 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 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
GeneMnat1Authority17420Mapping file id17420 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
GenePola1Authority18968Mapping file id18968 NCBI fileEvidenceIEA
GenePola2Authority18969Mapping file id18969 NCBI fileEvidenceIEA
GenePoleAuthority18973Mapping file id18973 NCBI fileEvidenceIEA
GenePole2Authority18974Mapping file id18974 NCBI fileEvidenceIEA
GenePole3Authority59001Mapping file id59001 NCBI fileEvidenceIEA
GenePole4Authority66979Mapping file id66979 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
GenePrim1Authority19075Mapping file id19075 NCBI fileEvidenceIEA
GenePrim2Authority19076Mapping file id19076 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
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

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.