Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

RHOD GTPase cycle

R-HSA-9013405 in Reactome release 97: under RHO GTPase cycle, with 54 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; neither of the other two lists holds it. 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.

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. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [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 human pathway

The mapping files place 54 genes in this human pathway; showing 1 to 54, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneACTN1AuthorityHGNC:163Mapping file id87 NCBI fileEvidenceTAS
GeneADD3AuthorityHGNC:245Mapping file id120 NCBI fileEvidenceTAS
GeneAKAP12AuthorityHGNC:370Mapping file id9590 NCBI fileEvidenceTAS
GeneANKFY1AuthorityHGNC:20763Mapping file id51479 NCBI fileEvidenceTAS
GeneARHGAP1AuthorityHGNC:673Mapping file id392 NCBI fileEvidenceTAS
GeneARHGAP12AuthorityHGNC:16348Mapping file id94134 NCBI fileEvidenceTAS
GeneARHGAP17AuthorityHGNC:18239Mapping file id55114 NCBI fileEvidenceTAS
GeneARHGAP21AuthorityHGNC:23725Mapping file id57584 NCBI fileEvidenceTAS
GeneARHGAP26AuthorityHGNC:17073Mapping file id23092 NCBI fileEvidenceTAS
GeneARHGAP32AuthorityHGNC:17399Mapping file id9743 NCBI fileEvidenceTAS
GeneARHGAP35AuthorityHGNC:4591Mapping file id2909 NCBI fileEvidenceTAS
GeneARHGAP39AuthorityHGNC:29351Mapping file id80728 NCBI fileEvidenceTAS
GeneARHGAP5AuthorityHGNC:675Mapping file id394 NCBI fileEvidenceTAS
GeneBUB1B-PAK6AuthorityHGNC:52276Mapping file id106821730 NCBI fileEvidenceTAS
GeneCAPZBAuthorityHGNC:1491Mapping file id832 NCBI fileEvidenceTAS
GeneCAV1AuthorityHGNC:1527Mapping file id857 NCBI fileEvidenceTAS
GeneCPNE8AuthorityHGNC:23498Mapping file id144402 NCBI fileEvidenceTAS
GeneDBN1AuthorityHGNC:2695Mapping file id1627 NCBI fileEvidenceTAS
GeneDEPDC1BAuthorityHGNC:24902Mapping file id55789 NCBI fileEvidenceTAS
GeneDIAPH1AuthorityHGNC:2876Mapping file id1729 NCBI fileEvidenceTAS
GeneDIAPH2AuthorityHGNC:2877Mapping file id1730 NCBI fileEvidenceTAS
GeneDIAPH3AuthorityHGNC:15480Mapping file id81624 NCBI fileEvidenceTAS
GeneEFHD2AuthorityHGNC:28670Mapping file id79180 NCBI fileEvidenceTAS
GeneEMDAuthorityHGNC:3331Mapping file id2010 NCBI fileEvidenceTAS
GeneESYT1AuthorityHGNC:29534Mapping file id23344 NCBI fileEvidenceTAS
GeneFILIP1AuthorityHGNC:21015Mapping file id27145 NCBI fileEvidenceTAS
GeneGOLGA8RAuthorityHGNC:44407Mapping file id101059918 NCBI fileEvidenceTAS
GeneHINT2AuthorityHGNC:18344Mapping file id84681 NCBI fileEvidenceTAS
GeneLBRAuthorityHGNC:6518Mapping file id3930 NCBI fileEvidenceTAS
GeneLEMD3AuthorityHGNC:28887Mapping file id23592 NCBI fileEvidenceTAS
GeneLMAN1AuthorityHGNC:6631Mapping file id3998 NCBI fileEvidenceTAS
GeneLMNB1AuthorityHGNC:6637Mapping file id4001 NCBI fileEvidenceTAS
GeneMCAMAuthorityHGNC:6934Mapping file id4162 NCBI fileEvidenceTAS
GeneMOSPD2AuthorityHGNC:28381Mapping file id158747 NCBI fileEvidenceTAS
GenePAK5AuthorityHGNC:15916Mapping file id57144 NCBI fileEvidenceTAS
GenePAK6AuthorityHGNC:16061Mapping file id56924 NCBI fileEvidenceTAS
GenePGRMC2AuthorityHGNC:16089Mapping file id10424 NCBI fileEvidenceTAS
GenePIK3R1AuthorityHGNC:8979Mapping file id5295 NCBI fileEvidenceTAS
GenePIK3R2AuthorityHGNC:8980Mapping file id5296 NCBI fileEvidenceTAS
GenePLXNA1AuthorityHGNC:9099Mapping file id5361 NCBI fileEvidenceTAS
GenePLXNB1AuthorityHGNC:9103Mapping file id5364 NCBI fileEvidenceTAS
GeneRAB7AAuthorityHGNC:9788Mapping file id7879 NCBI fileEvidenceTAS
GeneRACGAP1AuthorityHGNC:9804Mapping file id29127 NCBI fileEvidenceTAS
GeneRHODAuthorityHGNC:670Mapping file id29984 NCBI fileEvidenceTAS
GeneSLC4A7AuthorityHGNC:11033Mapping file id9497 NCBI fileEvidenceTAS
GeneSTBD1AuthorityHGNC:24854Mapping file id8987 NCBI fileEvidenceTAS
GeneSTEAP3AuthorityHGNC:24592Mapping file id55240 NCBI fileEvidenceTAS
GeneTMPOAuthorityHGNC:11875Mapping file id7112 NCBI fileEvidenceTAS
GeneTOR1AIP1AuthorityHGNC:29456Mapping file id26092 NCBI fileEvidenceTAS
GeneVAMP3AuthorityHGNC:12644Mapping file id9341 NCBI fileEvidenceTAS
GeneVANGL1AuthorityHGNC:15512Mapping file id81839 NCBI fileEvidenceTAS
GeneVAPBAuthorityHGNC:12649Mapping file id9217 NCBI fileEvidenceTAS
GeneVRK2AuthorityHGNC:12719Mapping file id7444 NCBI fileEvidenceTAS
GeneWHAMMAuthorityHGNC:30493Mapping file id123720 NCBI fileEvidenceTAS

Evidence codes on this page: TAS, 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: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human 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 human 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.