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.

Centrosome maturation

R-MMU-380287 in Reactome release 97: under G2/M Transition, with 78 genes placed in it by the mapping files and 2 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-380287 (human), R-RNO-380287 (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 78 genes in this mouse pathway; showing 1 to 78, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneActr1aAuthority54130Mapping file id54130 NCBI fileEvidenceIEA
GeneAkap9Authority100986Mapping file id100986 NCBI fileEvidenceIEA
GeneAlms1Authority236266Mapping file id236266 NCBI fileEvidenceIEA
GeneCcp110Authority101565Mapping file id101565 NCBI fileEvidenceIEA
GeneCdk1Authority12534Mapping file id12534 NCBI fileEvidenceIEA
GeneCdk11bAuthority12537Mapping file id12537 NCBI fileEvidenceIEA
GeneCdk5rap2Authority214444Mapping file id214444 NCBI fileEvidenceIEA
GeneCep131Authority12009Mapping file id12009 NCBI fileEvidenceIEA
GeneCep135Authority381644Mapping file id381644 NCBI fileEvidenceIEA
GeneCep152Authority99100Mapping file id99100 NCBI fileEvidenceIEA
GeneCep164Authority214552Mapping file idENSMUSG00000043987 Ensembl fileEvidenceIEA
GeneCep192Authority70799Mapping file id70799 NCBI fileEvidenceIEA
GeneCep250Authority16328Mapping file id16328 NCBI fileEvidenceIEA
GeneCep290Authority216274Mapping file id216274 NCBI fileEvidenceIEA
GeneCep41Authority83922Mapping file id83922 NCBI fileEvidenceIEA
GeneCep43Authority75296Mapping file id75296 NCBI fileEvidenceIEA
GeneCep57Authority74360Mapping file id74360 NCBI fileEvidenceIEA
GeneCep63Authority28135Mapping file id28135 NCBI fileEvidenceIEA
GeneCep70Authority68121Mapping file id68121 NCBI fileEvidenceIEA
GeneCep72Authority74470Mapping file id74470 NCBI fileEvidenceIEA
GeneCep76Authority225659Mapping file id225659 NCBI fileEvidenceIEA
GeneCep78Authority208518Mapping file id208518 NCBI fileEvidenceIEA
GeneCetn2Authority26370Mapping file id26370 NCBI fileEvidenceIEA
GeneCkap5Authority75786Mapping file id75786 NCBI fileEvidenceIEA
GeneClasp1Authority76707Mapping file id76707 NCBI fileEvidenceIEA
GeneCpapAuthority219103Mapping file id219103 NCBI fileEvidenceIEA
GeneCsnk1dAuthority104318Mapping file id104318 NCBI fileEvidenceIEA
GeneCsnk1eAuthority27373Mapping file id27373 NCBI fileEvidenceIEA
GeneDctn1Authority13191Mapping file id13191 NCBI fileEvidenceIEA
GeneDctn2Authority69654Mapping file id69654 NCBI fileEvidenceIEA
GeneDctn3Authority53598Mapping file id53598 NCBI fileEvidenceIEA
GeneDync1h1Authority13424Mapping file id13424 NCBI fileEvidenceIEA
GeneDync1i2Authority13427Mapping file id13427 NCBI fileEvidenceIEA
GeneDynll1Authority56455Mapping file id56455 NCBI fileEvidenceIEA
GeneHaus1Authority225745Mapping file id225745 NCBI fileEvidenceIEA
GeneHaus2Authority66296Mapping file id66296 NCBI fileEvidenceIEA
GeneHaus3Authority231123Mapping file id231123 NCBI fileEvidenceIEA
GeneHaus4Authority219072Mapping file id219072 NCBI fileEvidenceIEA
GeneHaus5Authority71909Mapping file id71909 NCBI fileEvidenceIEA
GeneHaus6Authority230376Mapping file id230376 NCBI fileEvidenceIEA
GeneHaus7Authority73738Mapping file id73738 NCBI fileEvidenceIEA
GeneHaus8Authority76478Mapping file id76478 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneMapre1Authority13589Mapping file id13589 NCBI fileEvidenceIEA
GeneMzt1Authority76789Mapping file id76789 NCBI fileEvidenceIEA
GeneMzt2Authority72083Mapping file id72083 NCBI fileEvidenceIEA
GeneNde1Authority67203Mapping file id67203 NCBI fileEvidenceIEA
GeneNedd1Authority17997Mapping file id17997 NCBI fileEvidenceIEA
GeneNek2Authority18005Mapping file id18005 NCBI fileEvidenceIEA
GeneNinlAuthority78177Mapping file id78177 NCBI fileEvidenceIEA
GeneNme7Authority171567Mapping file id171567 NCBI fileEvidenceIEA
GeneOdf2Authority18286Mapping file id18286 NCBI fileEvidenceIEA
GeneOfd1Authority237222Mapping file id237222 NCBI fileEvidenceIEA
GenePafah1b1Authority18472Mapping file id18472 NCBI fileEvidenceIEA
GenePcm1Authority18536Mapping file id18536 NCBI fileEvidenceIEA
GenePcntAuthority18541Mapping file id18541 NCBI fileEvidenceIEA
GenePlk1Authority18817Mapping file id18817 NCBI fileEvidenceIEA
GenePlk4Authority20873Mapping file id20873 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkar2bAuthority19088Mapping file id19088 NCBI fileEvidenceIEA
GeneSdccag8Authority76816Mapping file id76816 NCBI fileEvidenceIEA
GeneSfi1Authority78887Mapping file id78887 NCBI fileEvidenceIEA
GeneSsna1Authority68475Mapping file id68475 NCBI fileEvidenceIEA
GeneTuba1aAuthority22142Mapping file id22142 NCBI fileEvidenceIEA
GeneTuba4aAuthority22145Mapping file id22145 NCBI fileEvidenceIEA
GeneTubb4aAuthority22153Mapping file id22153 NCBI fileEvidenceIEA
GeneTubb4bAuthority227613Mapping file id227613 NCBI fileEvidenceIEA
GeneTubb5Authority22154Mapping file id22154 NCBI fileEvidenceIEA
GeneTubg1Authority103733Mapping file id103733 NCBI fileEvidenceIEA
GeneTubg2Authority103768Mapping file id103768 NCBI fileEvidenceIEA
GeneTubgcp2Authority74237Mapping file id74237 NCBI fileEvidenceIEA
GeneTubgcp3Authority259279Mapping file id259279 NCBI fileEvidenceIEA
GeneTubgcp4Authority51885Mapping file id51885 NCBI fileEvidenceIEA
GeneTubgcp5Authority233276Mapping file id233276 NCBI fileEvidenceIEA
GeneTubgcp6Authority328580Mapping file id328580 NCBI fileEvidenceIEA
GeneYwhaeAuthority22627Mapping file id22627 NCBI fileEvidenceIEA
GeneYwhagAuthority22628Mapping file id22628 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.