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.

CDC42 GTPase cycle

R-MMU-9013148 in Reactome release 97: under RHO GTPase cycle, with 94 genes placed in it by the mapping files and 0 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-9013148 (human), R-RNO-9013148 (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 94 genes in this mouse pathway; showing 1 to 94, 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
GeneAbrAuthority109934Mapping file id109934 NCBI fileEvidenceIEA
GeneArap1Authority69710Mapping file id69710 NCBI fileEvidenceIEA
GeneArap2Authority212285Mapping file idENSMUSG00000037999 Ensembl fileEvidenceIEA
GeneArap3Authority106952Mapping file id106952 NCBI fileEvidenceIEA
GeneArhgap1Authority228359Mapping file id228359 NCBI fileEvidenceIEA
GeneArhgap10Authority78514Mapping file id78514 NCBI fileEvidenceIEA
GeneArhgap17Authority70497Mapping file id70497 NCBI fileEvidenceIEA
GeneArhgap20Authority244867Mapping file id244867 NCBI fileEvidenceIEA
GeneArhgap21Authority71435Mapping file id71435 NCBI fileEvidenceIEA
GeneArhgap22Authority239027Mapping file id239027 NCBI fileEvidenceIEA
GeneArhgap24Authority231532Mapping file id231532 NCBI fileEvidenceIEA
GeneArhgap26Authority71302Mapping file id71302 NCBI fileEvidenceIEA
GeneArhgap27Authority544817Mapping file id544817 NCBI fileEvidenceIEA
GeneArhgap29Authority214137Mapping file id214137 NCBI fileEvidenceIEA
GeneArhgap30Authority226652Mapping file id226652 NCBI fileEvidenceIEA
GeneArhgap31Authority12549Mapping file id12549 NCBI fileEvidenceIEA
GeneArhgap32Authority330914Mapping file id330914 NCBI fileEvidenceIEA
GeneArhgap33Authority233071Mapping file id233071 NCBI fileEvidenceIEA
GeneArhgap35Authority232906Mapping file id232906 NCBI fileEvidenceIEA
GeneArhgap39Authority223666Mapping file id223666 NCBI fileEvidenceIEA
GeneArhgap4Authority171207Mapping file idENSMUSG00000031389 Ensembl fileEvidenceIEA
GeneArhgap40Authority545481Mapping file id545481 NCBI fileEvidenceIEA
GeneArhgap42Authority71544Mapping file id71544 NCBI fileEvidenceIEA
GeneArhgap44Authority216831Mapping file id216831 NCBI fileEvidenceIEA
GeneArhgap45Authority70719Mapping file id70719 NCBI fileEvidenceIEA
GeneArhgap5Authority11855Mapping file id11855 NCBI fileEvidenceIEA
GeneArhgap9Authority216445Mapping file id216445 NCBI fileEvidenceIEA
GeneArhgdiaAuthority192662Mapping file id192662 NCBI fileEvidenceIEA
GeneArhgdibAuthority11857Mapping file id11857 NCBI fileEvidenceIEA
GeneArhgdigAuthority14570Mapping file id14570 NCBI fileEvidenceIEA
GeneArhgef10Authority234094Mapping file id234094 NCBI fileEvidenceIEA
GeneArhgef11Authority213498Mapping file id213498 NCBI fileEvidenceIEA
GeneArhgef12Authority69632Mapping file id69632 NCBI fileEvidenceIEA
GeneArhgef15Authority442801Mapping file id442801 NCBI fileEvidenceIEA
GeneArhgef16Authority230972Mapping file id230972 NCBI fileEvidenceIEA
GeneArhgef19Authority213649Mapping file id213649 NCBI fileEvidenceIEA
GeneArhgef25Authority52666Mapping file id52666 NCBI fileEvidenceIEA
GeneArhgef26Authority622434Mapping file id622434 NCBI fileEvidenceIEA
GeneArhgef5Authority54324Mapping file id54324 NCBI fileEvidenceIEA
GeneArhgef6Authority73341Mapping file id73341 NCBI fileEvidenceIEA
GeneArhgef9Authority236915Mapping file id236915 NCBI fileEvidenceIEA
GeneBcrAuthority110279Mapping file id110279 NCBI fileEvidenceIEA
GeneCav1Authority12389Mapping file id12389 NCBI fileEvidenceIEA
GeneCdc42Authority12540Mapping file id12540 NCBI fileEvidenceIEA
GeneChn1Authority108699Mapping file id108699 NCBI fileEvidenceIEA
GeneDef6Authority23853Mapping file id23853 NCBI fileEvidenceIEA
GeneDepdc1bAuthority218581Mapping file id218581 NCBI fileEvidenceIEA
GeneDlc1Authority50768Mapping file id50768 NCBI fileEvidenceIEA
GeneDnmbpAuthority71972Mapping file id71972 NCBI fileEvidenceIEA
GeneDock10Authority210293Mapping file id210293 NCBI fileEvidenceIEA
GeneDock11Authority75974Mapping file id75974 NCBI fileEvidenceIEA
GeneDock6Authority319899Mapping file id319899 NCBI fileEvidenceIEA
GeneDock7Authority67299Mapping file idENSMUSG00000028556 Ensembl fileEvidenceIEA
GeneDock8Authority76088Mapping file id76088 NCBI fileEvidenceIEA
GeneDock9Authority105445Mapping file idENSMUSG00000025558 Ensembl fileEvidenceIEA
GeneEct2Authority13605Mapping file id13605 NCBI fileEvidenceIEA
GeneFam13bAuthority225358Mapping file id225358 NCBI fileEvidenceIEA
GeneFarp1Authority223254Mapping file id223254 NCBI fileEvidenceIEA
GeneFgd1Authority14163Mapping file id14163 NCBI fileEvidenceIEA
GeneFgd2Authority26382Mapping file id26382 NCBI fileEvidenceIEA
GeneFgd3Authority30938Mapping file idENSMUSG00000037946 Ensembl fileEvidenceIEA
GeneFgd4Authority224014Mapping file id224014 NCBI fileEvidenceIEA
GeneGmipAuthority78816Mapping file id78816 NCBI fileEvidenceIEA
GeneGna13Authority14674Mapping file id14674 NCBI fileEvidenceIEA
GeneItsn1Authority16443Mapping file id16443 NCBI fileEvidenceIEA
GeneKtn1Authority16709Mapping file id16709 NCBI fileEvidenceIEA
GeneLbrAuthority98386Mapping file id98386 NCBI fileEvidenceIEA
GeneMcf2Authority109904Mapping file id109904 NCBI fileEvidenceIEA
GeneMcf2lAuthority17207Mapping file idENSMUSG00000031442 Ensembl fileEvidenceIEA
GeneMyo9bAuthority17925Mapping file idENSMUSG00000004677 Ensembl fileEvidenceIEA
GeneNgefAuthority53972Mapping file id53972 NCBI fileEvidenceIEA
GeneOphn1Authority94190Mapping file id94190 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePlekhg1Authority213783Mapping file idENSMUSG00000040624 Ensembl fileEvidenceIEA
GenePlekhg2Authority101497Mapping file id101497 NCBI fileEvidenceIEA
GenePlekhg3Authority263406Mapping file id263406 NCBI fileEvidenceIEA
GenePrex1Authority277360Mapping file id277360 NCBI fileEvidenceIEA
GenePrex2Authority109294Mapping file id109294 NCBI fileEvidenceIEA
GeneRacgap1Authority26934Mapping file id26934 NCBI fileEvidenceIEA
GeneRalbp1Authority19765Mapping file id19765 NCBI fileEvidenceIEA
GeneRasgrf2Authority19418Mapping file id19418 NCBI fileEvidenceIEA
GeneSpata13Authority219140Mapping file id219140 NCBI fileEvidenceIEA
GeneSrgap1Authority117600Mapping file id117600 NCBI fileEvidenceIEA
GeneSrgap2Authority14270Mapping file id14270 NCBI fileEvidenceIEA
GeneSrgap3Authority259302Mapping file id259302 NCBI fileEvidenceIEA
GeneStard13Authority243362Mapping file id243362 NCBI fileEvidenceIEA
GeneStard8Authority236920Mapping file id236920 NCBI fileEvidenceIEA
GeneSyde1Authority71709Mapping file idENSMUSG00000032714 Ensembl fileEvidenceIEA
GeneTagapAuthority72536Mapping file id72536 NCBI fileEvidenceIEA
GeneTrioAuthority223435Mapping file id223435 NCBI fileEvidenceIEA
GeneVav2Authority22325Mapping file id22325 NCBI fileEvidenceIEA
GeneVav3Authority57257Mapping file id57257 NCBI fileEvidenceIEA
GeneYkt6Authority56418Mapping file id56418 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

Children

None: no pathway of this release's list names this one as a parent.

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.