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.

Signaling by Rho GTPases, Miro GTPases and RHOBTB3

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

Genes Reactome places in this mouse pathway, page 1 of 7
GeneAaasAuthority223921Mapping file id223921 NCBI fileEvidenceIEA
GeneAbcd3Authority19299Mapping file id19299 NCBI fileEvidenceIEA
GeneAbi1Authority11308Mapping file id11308 NCBI fileEvidenceIEA
GeneAbi2Authority329165Mapping file id329165 NCBI fileEvidenceIEA
GeneAbl1Authority11350Mapping file id11350 NCBI fileEvidenceIEA
GeneAbl2Authority11352Mapping file idENSMUSG00000026596 Ensembl fileEvidenceIEA
GeneAbrAuthority109934Mapping file id109934 NCBI fileEvidenceIEA
GeneAcbd5Authority74159Mapping file id74159 NCBI fileEvidenceIEA
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActc1Authority11464Mapping file id11464 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneActn1Authority109711Mapping file id109711 NCBI fileEvidenceIEA
GeneActr2Authority66713Mapping file id66713 NCBI fileEvidenceIEA
GeneActr3Authority74117Mapping file id74117 NCBI fileEvidenceIEA
GeneAdd3Authority27360Mapping file id27360 NCBI fileEvidenceIEA
GeneAhctf1Authority226747Mapping file id226747 NCBI fileEvidenceIEA
GeneAkap12Authority83397Mapping file id83397 NCBI fileEvidenceIEA
GeneAkap13Authority75547Mapping file id75547 NCBI fileEvidenceIEA
GeneAldh3a2Authority11671Mapping file id11671 NCBI fileEvidenceIEA
GeneAls2Authority74018Mapping file id74018 NCBI fileEvidenceIEA
GeneAmigo2Authority105827Mapping file id105827 NCBI fileEvidenceIEA
GeneAnkle2Authority71782Mapping file id71782 NCBI fileEvidenceIEA
GeneAnkrd26Authority232339Mapping file idENSMUSG00000007827 Ensembl fileEvidenceIEA
GeneAnlnAuthority68743Mapping file id68743 NCBI fileEvidenceIEA
GeneArAuthority11835Mapping file id11835 NCBI fileEvidenceIEA
GeneArap1Authority69710Mapping file id69710 NCBI fileEvidenceIEA
GeneArap2Authority212285Mapping file idENSMUSG00000037999 Ensembl fileEvidenceIEA
GeneArap3Authority106952Mapping file id106952 NCBI fileEvidenceIEA
GeneArfgap3Authority66251Mapping file id66251 NCBI fileEvidenceIEA
GeneArhgap1Authority228359Mapping file id228359 NCBI fileEvidenceIEA
GeneArhgap10Authority78514Mapping file id78514 NCBI fileEvidenceIEA
GeneArhgap11aAuthority228482Mapping file id228482 NCBI fileEvidenceIEA
GeneArhgap12Authority75415Mapping file id75415 NCBI fileEvidenceIEA
GeneArhgap15Authority76117Mapping file id76117 NCBI fileEvidenceIEA
GeneArhgap17Authority70497Mapping file id70497 NCBI fileEvidenceIEA
GeneArhgap18Authority73910Mapping file id73910 NCBI fileEvidenceIEA
GeneArhgap19Authority71085Mapping file id71085 NCBI fileEvidenceIEA
GeneArhgap20Authority244867Mapping file id244867 NCBI fileEvidenceIEA
GeneArhgap21Authority71435Mapping file id71435 NCBI fileEvidenceIEA
GeneArhgap22Authority239027Mapping file id239027 NCBI fileEvidenceIEA
GeneArhgap23Authority58996Mapping file id58996 NCBI fileEvidenceIEA
GeneArhgap24Authority231532Mapping file id231532 NCBI fileEvidenceIEA
GeneArhgap25Authority232201Mapping file id232201 NCBI fileEvidenceIEA
GeneArhgap26Authority71302Mapping file id71302 NCBI fileEvidenceIEA
GeneArhgap27Authority544817Mapping file id544817 NCBI fileEvidenceIEA
GeneArhgap28Authority268970Mapping file id268970 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
GeneArhgap6Authority11856Mapping file id11856 NCBI fileEvidenceIEA
GeneArhgap8Authority73167Mapping file id73167 NCBI fileEvidenceIEA
GeneArhgap9Authority216445Mapping file id216445 NCBI fileEvidenceIEA
GeneArhgdiaAuthority192662Mapping file id192662 NCBI fileEvidenceIEA
GeneArhgdibAuthority11857Mapping file id11857 NCBI fileEvidenceIEA
GeneArhgdigAuthority14570Mapping file id14570 NCBI fileEvidenceIEA
GeneArhgef1Authority16801Mapping file id16801 NCBI fileEvidenceIEA
GeneArhgef10Authority234094Mapping file id234094 NCBI fileEvidenceIEA
GeneArhgef10lAuthority72754Mapping file id72754 NCBI fileEvidenceIEA
GeneArhgef11Authority213498Mapping file id213498 NCBI fileEvidenceIEA
GeneArhgef12Authority69632Mapping file id69632 NCBI fileEvidenceIEA
GeneArhgef15Authority442801Mapping file id442801 NCBI fileEvidenceIEA
GeneArhgef16Authority230972Mapping file id230972 NCBI fileEvidenceIEA
GeneArhgef17Authority207212Mapping file id207212 NCBI fileEvidenceIEA
GeneArhgef18Authority102098Mapping file id102098 NCBI fileEvidenceIEA
GeneArhgef19Authority213649Mapping file id213649 NCBI fileEvidenceIEA
GeneArhgef2Authority16800Mapping file id16800 NCBI fileEvidenceIEA
GeneArhgef25Authority52666Mapping file id52666 NCBI fileEvidenceIEA
GeneArhgef26Authority622434Mapping file id622434 NCBI fileEvidenceIEA
GeneArhgef28Authority110596Mapping file id110596 NCBI fileEvidenceIEA
GeneArhgef3Authority71704Mapping file id71704 NCBI fileEvidenceIEA
GeneArhgef39Authority230098Mapping file id230098 NCBI fileEvidenceIEA
GeneArhgef5Authority54324Mapping file id54324 NCBI fileEvidenceIEA
GeneArhgef6Authority73341Mapping file id73341 NCBI fileEvidenceIEA
GeneArhgef7Authority54126Mapping file id54126 NCBI fileEvidenceIEA
GeneArhgef9Authority236915Mapping file id236915 NCBI fileEvidenceIEA
GeneArl13bAuthority68146Mapping file id68146 NCBI fileEvidenceIEA
GeneArmcx3Authority71703Mapping file id71703 NCBI fileEvidenceIEA
GeneArpc1aAuthority56443Mapping file id56443 NCBI fileEvidenceIEA
GeneArpc1bAuthority11867Mapping file id11867 NCBI fileEvidenceIEA
GeneArpc2Authority76709Mapping file id76709 NCBI fileEvidenceIEA
GeneArpc3Authority56378Mapping file id56378 NCBI fileEvidenceIEA
GeneArpc4Authority68089Mapping file id68089 NCBI fileEvidenceIEA
GeneArpc5Authority67771Mapping file id67771 NCBI fileEvidenceIEA
GeneAtp6ap1Authority54411Mapping file id54411 NCBI fileEvidenceIEA
GeneAurkbAuthority20877Mapping file id20877 NCBI fileEvidenceIEA
GeneB9d2Authority232987Mapping file id232987 NCBI fileEvidenceIEA
GeneBaiap2Authority108100Mapping file id108100 NCBI fileEvidenceIEA
GeneBaiap2l1Authority66898Mapping file id66898 NCBI fileEvidenceIEA
GeneBaiap2l2Authority207495Mapping file id207495 NCBI fileEvidenceIEA
GeneBasp1Authority70350Mapping file id70350 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.