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.

RAC2 GTPase cycle

R-MMU-9013404 in Reactome release 97: under RHO GTPase cycle, with 85 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-9013404 (human), R-RNO-9013404 (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 85 genes in this mouse pathway; showing 1 to 85, 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
GeneAbi1Authority11308Mapping file id11308 NCBI fileEvidenceIEA
GeneAbi2Authority329165Mapping file id329165 NCBI fileEvidenceIEA
GeneAbrAuthority109934Mapping file id109934 NCBI fileEvidenceIEA
GeneAnkle2Authority71782Mapping file id71782 NCBI fileEvidenceIEA
GeneArhgap1Authority228359Mapping file id228359 NCBI fileEvidenceIEA
GeneArhgap17Authority70497Mapping file id70497 NCBI fileEvidenceIEA
GeneArhgap21Authority71435Mapping file id71435 NCBI fileEvidenceIEA
GeneArhgap26Authority71302Mapping file id71302 NCBI fileEvidenceIEA
GeneArhgap32Authority330914Mapping file id330914 NCBI fileEvidenceIEA
GeneArhgap35Authority232906Mapping file id232906 NCBI fileEvidenceIEA
GeneArhgap39Authority223666Mapping file id223666 NCBI fileEvidenceIEA
GeneArhgap42Authority71544Mapping file id71544 NCBI fileEvidenceIEA
GeneArhgdiaAuthority192662Mapping file id192662 NCBI fileEvidenceIEA
GeneArmcx3Authority71703Mapping file id71703 NCBI fileEvidenceIEA
GeneBaiap2l1Authority66898Mapping file id66898 NCBI fileEvidenceIEA
GeneBcrAuthority110279Mapping file id110279 NCBI fileEvidenceIEA
GeneBrk1Authority101314Mapping file id101314 NCBI fileEvidenceIEA
GeneCav1Authority12389Mapping file id12389 NCBI fileEvidenceIEA
GeneCdc42Authority12540Mapping file id12540 NCBI fileEvidenceIEA
GeneCdc42ep1Authority104445Mapping file id104445 NCBI fileEvidenceIEA
GeneCdc42ep4Authority56699Mapping file id56699 NCBI fileEvidenceIEA
GeneCybaAuthority13057Mapping file id13057 NCBI fileEvidenceIEA
GeneCybbAuthority13058Mapping file id13058 NCBI fileEvidenceIEA
GeneCyfip1Authority20430Mapping file id20430 NCBI fileEvidenceIEA
GeneDef6Authority23853Mapping file id23853 NCBI fileEvidenceIEA
GeneDepdc1bAuthority218581Mapping file id218581 NCBI fileEvidenceIEA
GeneDiaph3Authority56419Mapping file id56419 NCBI fileEvidenceIEA
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneDock10Authority210293Mapping file id210293 NCBI fileEvidenceIEA
GeneDock2Authority94176Mapping file id94176 NCBI fileEvidenceIEA
GeneDock4Authority238130Mapping file id238130 NCBI fileEvidenceIEA
GeneDsg2Authority13511Mapping file id13511 NCBI fileEvidenceIEA
GeneEmdAuthority13726Mapping file id13726 NCBI fileEvidenceIEA
GeneEpha2Authority13836Mapping file id13836 NCBI fileEvidenceIEA
GeneErbinAuthority59079Mapping file id59079 NCBI fileEvidenceIEA
GeneEsyt1Authority23943Mapping file id23943 NCBI fileEvidenceIEA
GeneGarre1Authority233103Mapping file id233103 NCBI fileEvidenceIEA
GeneGit1Authority216963Mapping file id216963 NCBI fileEvidenceIEA
GeneGit2Authority26431Mapping file id26431 NCBI fileEvidenceIEA
GeneIqgap1Authority29875Mapping file id29875 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneLamtor1Authority66508Mapping file id66508 NCBI fileEvidenceIEA
GeneLbrAuthority98386Mapping file id98386 NCBI fileEvidenceIEA
GeneLman1Authority70361Mapping file id70361 NCBI fileEvidenceIEA
GeneMcamAuthority84004Mapping file id84004 NCBI fileEvidenceIEA
GeneMcf2Authority109904Mapping file id109904 NCBI fileEvidenceIEA
GeneMpp7Authority75739Mapping file id75739 NCBI fileEvidenceIEA
GeneMtx1Authority17827Mapping file idENSMUSG00000064068 Ensembl fileEvidenceIEA
GeneNcf1Authority17969Mapping file id17969 NCBI fileEvidenceIEA
GeneNcf2Authority17970Mapping file id17970 NCBI fileEvidenceIEA
GeneNcf4Authority17972Mapping file id17972 NCBI fileEvidenceIEA
GeneNckap1Authority50884Mapping file id50884 NCBI fileEvidenceIEA
GeneNckap1lAuthority105855Mapping file id105855 NCBI fileEvidenceIEA
GeneNhsAuthority195727Mapping file id195727 NCBI fileEvidenceIEA
GeneOphn1Authority94190Mapping file id94190 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GenePak2Authority224105Mapping file id224105 NCBI fileEvidenceIEA
GenePak4Authority70584Mapping file id70584 NCBI fileEvidenceIEA
GenePgrmc2Authority70804Mapping file id70804 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePld2Authority18806Mapping file id18806 NCBI fileEvidenceIEA
GenePrex1Authority277360Mapping file id277360 NCBI fileEvidenceIEA
GeneRab7Authority19349Mapping file id19349 NCBI fileEvidenceIEA
GeneRac2Authority19354Mapping file id19354 NCBI fileEvidenceIEA
GeneRacgap1Authority26934Mapping file id26934 NCBI fileEvidenceIEA
GeneRbm39Authority170791Mapping file id170791 NCBI fileEvidenceIEA
GeneSamm50Authority68653Mapping file id68653 NCBI fileEvidenceIEA
GeneSlitrk5Authority75409Mapping file id75409 NCBI fileEvidenceIEA
GeneStbd1Authority52331Mapping file id52331 NCBI fileEvidenceIEA
GeneSwap70Authority20947Mapping file id20947 NCBI fileEvidenceIEA
GeneSyde1Authority71709Mapping file idENSMUSG00000032714 Ensembl fileEvidenceIEA
GeneTaok3Authority330177Mapping file id330177 NCBI fileEvidenceIEA
GeneTfrcAuthority22042Mapping file id22042 NCBI fileEvidenceIEA
GeneTrioAuthority223435Mapping file id223435 NCBI fileEvidenceIEA
GeneVamp3Authority22319Mapping file id22319 NCBI fileEvidenceIEA
GeneVangl1Authority229658Mapping file id229658 NCBI fileEvidenceIEA
GeneVapbAuthority56491Mapping file idENSMUSG00000054455 Ensembl fileEvidenceIEA
GeneVav1Authority22324Mapping file id22324 NCBI fileEvidenceIEA
GeneVav2Authority22325Mapping file id22325 NCBI fileEvidenceIEA
GeneVav3Authority57257Mapping file id57257 NCBI fileEvidenceIEA
GeneVrk2Authority69922Mapping file id69922 NCBI fileEvidenceIEA
GeneWasf2Authority242687Mapping file id242687 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.