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.

RND2 GTPase cycle

R-MMU-9696270 in Reactome release 97: under RHO GTPase cycle, with 43 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-9696270 (human), R-RNO-9696270 (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 43 genes in this mouse pathway; showing 1 to 43, 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
GeneAldh3a2Authority11671Mapping file id11671 NCBI fileEvidenceIEA
GeneAnkrd26Authority232339Mapping file idENSMUSG00000007827 Ensembl fileEvidenceIEA
GeneArhgap1Authority228359Mapping file id228359 NCBI fileEvidenceIEA
GeneArhgap35Authority232906Mapping file id232906 NCBI fileEvidenceIEA
GeneArhgap5Authority11855Mapping file id11855 NCBI fileEvidenceIEA
GeneBltp3bAuthority75089Mapping file id75089 NCBI fileEvidenceIEA
GeneCav1Authority12389Mapping file id12389 NCBI fileEvidenceIEA
GeneCkap4Authority216197Mapping file id216197 NCBI fileEvidenceIEA
GeneDepdc1bAuthority218581Mapping file id218581 NCBI fileEvidenceIEA
GeneDlg5Authority71228Mapping file id71228 NCBI fileEvidenceIEA
GeneDsg1aAuthority13510Mapping file id13510 NCBI fileEvidenceIEA
GeneDstAuthority13518Mapping file id13518 NCBI fileEvidenceIEA
GeneEpha2Authority13836Mapping file id13836 NCBI fileEvidenceIEA
GeneFnbp1Authority14269Mapping file id14269 NCBI fileEvidenceIEA
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFrs3Authority107971Mapping file id107971 NCBI fileEvidenceIEA
GeneGolga3Authority269682Mapping file id269682 NCBI fileEvidenceIEA
GeneKctd13Authority233877Mapping file id233877 NCBI fileEvidenceIEA
GeneKidins220Authority77480Mapping file id77480 NCBI fileEvidenceIEA
GeneKif14Authority381293Mapping file id381293 NCBI fileEvidenceIEA
GeneKtn1Authority16709Mapping file id16709 NCBI fileEvidenceIEA
GeneLrrc1Authority214345Mapping file id214345 NCBI fileEvidenceIEA
GeneMuc13Authority17063Mapping file id17063 NCBI fileEvidenceIEA
GeneNischAuthority64652Mapping file id64652 NCBI fileEvidenceIEA
GeneNudcAuthority18221Mapping file id18221 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePkp4Authority227937Mapping file id227937 NCBI fileEvidenceIEA
GenePlxnd1Authority67784Mapping file id67784 NCBI fileEvidenceIEA
GenePrag1Authority244418Mapping file id244418 NCBI fileEvidenceIEA
GenePtpn13Authority19249Mapping file id19249 NCBI fileEvidenceIEA
GeneRbm39Authority170791Mapping file id170791 NCBI fileEvidenceIEA
GeneRbmxAuthority19655Mapping file id19655 NCBI fileEvidenceIEA
GeneRnd2Authority11858Mapping file id11858 NCBI fileEvidenceIEA
GeneSack1bAuthority208994Mapping file id208994 NCBI fileEvidenceIEA
GeneScribAuthority105782Mapping file id105782 NCBI fileEvidenceIEA
GeneTfrcAuthority22042Mapping file id22042 NCBI fileEvidenceIEA
GeneTnfaip1Authority21927Mapping file id21927 NCBI fileEvidenceIEA
GeneTxnl1Authority53382Mapping file id53382 NCBI fileEvidenceIEA
GeneUbxn11Authority67586Mapping file id67586 NCBI fileEvidenceIEA
GeneVangl1Authority229658Mapping file id229658 NCBI fileEvidenceIEA
GeneVangl2Authority93840Mapping file id93840 NCBI fileEvidenceIEA
GeneWdr6Authority83669Mapping file id83669 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.