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.

RHO GTPase cycle

R-MMU-9012999 in Reactome release 97: under Signaling by Rho GTPases, with 414 genes placed in it by the mapping files and 18 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-9012999 (human), R-RNO-9012999 (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 414 genes in this mouse pathway; showing 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 5
GeneCdc37Authority12539Mapping file id12539 NCBI fileEvidenceIEA
GeneCdc42Authority12540Mapping file id12540 NCBI fileEvidenceIEA
GeneCdc42bpaAuthority226751Mapping file id226751 NCBI fileEvidenceIEA
GeneCdc42bpbAuthority217866Mapping file id217866 NCBI fileEvidenceIEA
GeneCdc42ep1Authority104445Mapping file id104445 NCBI fileEvidenceIEA
GeneCdc42ep2Authority104252Mapping file id104252 NCBI fileEvidenceIEA
GeneCdc42ep3Authority260409Mapping file id260409 NCBI fileEvidenceIEA
GeneCdc42ep4Authority56699Mapping file id56699 NCBI fileEvidenceIEA
GeneCep97Authority74201Mapping file id74201 NCBI fileEvidenceIEA
GeneCftrAuthority12638Mapping file id12638 NCBI fileEvidenceIEA
GeneChn1Authority108699Mapping file id108699 NCBI fileEvidenceIEA
GeneChn2Authority69993Mapping file id69993 NCBI fileEvidenceIEA
GeneCitAuthority12704Mapping file id12704 NCBI fileEvidenceIEA
GeneCkap4Authority216197Mapping file id216197 NCBI fileEvidenceIEA
GeneCkbAuthority12709Mapping file id12709 NCBI fileEvidenceIEA
GeneCltcAuthority67300Mapping file id67300 NCBI fileEvidenceIEA
GeneCops2Authority12848Mapping file id12848 NCBI fileEvidenceIEA
GeneCops4Authority26891Mapping file id26891 NCBI fileEvidenceIEA
GeneCpdAuthority12874Mapping file id12874 NCBI fileEvidenceIEA
GeneCpne8Authority66871Mapping file id66871 NCBI fileEvidenceIEA
GeneCpsf7Authority269061Mapping file id269061 NCBI fileEvidenceIEA
GeneCskAuthority12988Mapping file id12988 NCBI fileEvidenceIEA
GeneCul3Authority26554Mapping file id26554 NCBI fileEvidenceIEA
GeneCybaAuthority13057Mapping file id13057 NCBI fileEvidenceIEA
GeneCybbAuthority13058Mapping file id13058 NCBI fileEvidenceIEA
GeneCyfip1Authority20430Mapping file id20430 NCBI fileEvidenceIEA
GeneCyfip2Authority76884Mapping file id76884 NCBI fileEvidenceIEA
GeneDaam1Authority208846Mapping file id208846 NCBI fileEvidenceIEA
GeneDbtAuthority13171Mapping file id13171 NCBI fileEvidenceIEA
GeneDdrgk1Authority77006Mapping file id77006 NCBI fileEvidenceIEA
GeneDdx39bAuthority53817Mapping file id53817 NCBI fileEvidenceIEA
GeneDdx4Authority13206Mapping file id13206 NCBI fileEvidenceIEA
GeneDef6Authority23853Mapping file id23853 NCBI fileEvidenceIEA
GeneDepdc1bAuthority218581Mapping file id218581 NCBI fileEvidenceIEA
GeneDiaph1Authority13367Mapping file id13367 NCBI fileEvidenceIEA
GeneDiaph2Authority54004Mapping file id54004 NCBI fileEvidenceIEA
GeneDiaph3Authority56419Mapping file id56419 NCBI fileEvidenceIEA
GeneDlc1Authority50768Mapping file id50768 NCBI fileEvidenceIEA
GeneDlg5Authority71228Mapping file id71228 NCBI fileEvidenceIEA
GeneDnmbpAuthority71972Mapping file id71972 NCBI fileEvidenceIEA
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneDock10Authority210293Mapping file id210293 NCBI fileEvidenceIEA
GeneDock11Authority75974Mapping file id75974 NCBI fileEvidenceIEA
GeneDock2Authority94176Mapping file id94176 NCBI fileEvidenceIEA
GeneDock4Authority238130Mapping file id238130 NCBI fileEvidenceIEA
GeneDock5Authority68813Mapping file id68813 NCBI fileEvidenceIEA
GeneDock6Authority319899Mapping file id319899 NCBI fileEvidenceIEA
GeneDock7Authority67299Mapping file idENSMUSG00000028556 Ensembl fileEvidenceIEA
GeneDock8Authority76088Mapping file id76088 NCBI fileEvidenceIEA
GeneDock9Authority105445Mapping file idENSMUSG00000025558 Ensembl fileEvidenceIEA
GeneDsg1aAuthority13510Mapping file id13510 NCBI fileEvidenceIEA
GeneDsg2Authority13511Mapping file id13511 NCBI fileEvidenceIEA
GeneDspAuthority109620Mapping file id109620 NCBI fileEvidenceIEA
GeneDstAuthority13518Mapping file id13518 NCBI fileEvidenceIEA
GeneEct2Authority13605Mapping file id13605 NCBI fileEvidenceIEA
GeneElmo2Authority140579Mapping file id140579 NCBI fileEvidenceIEA
GeneEmc3Authority66087Mapping file id66087 NCBI fileEvidenceIEA
GeneEmdAuthority13726Mapping file id13726 NCBI fileEvidenceIEA
GeneEpha2Authority13836Mapping file id13836 NCBI fileEvidenceIEA
GeneEpsti1Authority108670Mapping file id108670 NCBI fileEvidenceIEA
GeneErbinAuthority59079Mapping file id59079 NCBI fileEvidenceIEA
GeneEsyt1Authority23943Mapping file id23943 NCBI fileEvidenceIEA
GeneFaf2Authority76577Mapping file id76577 NCBI fileEvidenceIEA
GeneFam135aAuthority68187Mapping file id68187 NCBI fileEvidenceIEA
GeneFam13aAuthority58909Mapping file id58909 NCBI fileEvidenceIEA
GeneFam13bAuthority225358Mapping file id225358 NCBI fileEvidenceIEA
GeneFam169aAuthority320557Mapping file id320557 NCBI fileEvidenceIEA
GeneFam91a1Authority210998Mapping file id210998 NCBI fileEvidenceIEA
GeneFarp1Authority223254Mapping file id223254 NCBI fileEvidenceIEA
GeneFarp2Authority227377Mapping file id227377 NCBI fileEvidenceIEA
GeneFermt2Authority218952Mapping file id218952 NCBI fileEvidenceIEA
GeneFgd1Authority14163Mapping file id14163 NCBI fileEvidenceIEA
GeneFgd2Authority26382Mapping file id26382 NCBI fileEvidenceIEA
GeneFgd3Authority30938Mapping file idENSMUSG00000037946 Ensembl fileEvidenceIEA
GeneFgd4Authority224014Mapping file id224014 NCBI fileEvidenceIEA
GeneFgd5Authority232237Mapping file id232237 NCBI fileEvidenceIEA
GeneFlot1Authority14251Mapping file id14251 NCBI fileEvidenceIEA
GeneFlot2Authority14252Mapping file id14252 NCBI fileEvidenceIEA
GeneFmnl1Authority57778Mapping file id57778 NCBI fileEvidenceIEA
GeneFmnl2Authority71409Mapping file id71409 NCBI fileEvidenceIEA
GeneFmnl3Authority22379Mapping file id22379 NCBI fileEvidenceIEA
GeneFnbp1Authority14269Mapping file id14269 NCBI fileEvidenceIEA
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFrs3Authority107971Mapping file id107971 NCBI fileEvidenceIEA
GeneGarre1Authority233103Mapping file id233103 NCBI fileEvidenceIEA
GeneGfod1Authority328232Mapping file id328232 NCBI fileEvidenceIEA
GeneGit1Authority216963Mapping file id216963 NCBI fileEvidenceIEA
GeneGit2Authority26431Mapping file id26431 NCBI fileEvidenceIEA
GeneGja1Authority14609Mapping file id14609 NCBI fileEvidenceIEA
GeneGmipAuthority78816Mapping file id78816 NCBI fileEvidenceIEA
GeneGna13Authority14674Mapping file id14674 NCBI fileEvidenceIEA
GeneGolga3Authority269682Mapping file id269682 NCBI fileEvidenceIEA
GeneGopcAuthority94221Mapping file id94221 NCBI fileEvidenceIEA
GeneGps1Authority209318Mapping file idENSMUSG00000025156 Ensembl fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrb7Authority14786Mapping file id14786 NCBI fileEvidenceIEA
GeneHgsAuthority15239Mapping file id15239 NCBI fileEvidenceIEA
GeneHmox2Authority15369Mapping file id15369 NCBI fileEvidenceIEA
GeneHnrnpcAuthority15381Mapping file id15381 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 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.