Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

RAC2 GTPase cycle

R-HSA-9013404 in Reactome release 97: under RHO GTPase cycle, with 88 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-MMU-9013404 (mouse), 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.

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 88 genes in this human pathway; showing 1 to 88, 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
GeneABI1AuthorityHGNC:11320Mapping file id10006 NCBI fileEvidenceTAS
GeneABI2AuthorityHGNC:24011Mapping file id10152 NCBI fileEvidenceTAS
GeneABRAuthorityHGNC:81Mapping file id29 NCBI fileEvidenceTAS
GeneANKLE2AuthorityHGNC:29101Mapping file id23141 NCBI fileEvidenceTAS
GeneARHGAP1AuthorityHGNC:673Mapping file id392 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
GeneARHGAP42AuthorityHGNC:26545Mapping file id143872 NCBI fileEvidenceTAS
GeneARHGDIAAuthorityHGNC:678Mapping file id396 NCBI fileEvidenceTAS
GeneARMCX3AuthorityHGNC:24065Mapping file id51566 NCBI fileEvidenceTAS
GeneBAIAP2L1AuthorityHGNC:21649Mapping file id55971 NCBI fileEvidenceTAS
GeneBCRAuthorityHGNC:1014Mapping file id613 NCBI fileEvidenceTAS
GeneBRK1AuthorityHGNC:23057Mapping file id55845 NCBI fileEvidenceTAS
GeneCAV1AuthorityHGNC:1527Mapping file id857 NCBI fileEvidenceTAS
GeneCDC42AuthorityHGNC:1736Mapping file id998 NCBI fileEvidenceTAS
GeneCDC42EP1AuthorityHGNC:17014Mapping file id11135 NCBI fileEvidenceTAS
GeneCDC42EP4AuthorityHGNC:17147Mapping file id23580 NCBI fileEvidenceTAS
GeneCYBAAuthorityHGNC:2577Mapping file id1535 NCBI fileEvidenceTAS
GeneCYBBAuthorityHGNC:2578Mapping file id1536 NCBI fileEvidenceTAS
GeneCYFIP1AuthorityHGNC:13759Mapping file id23191 NCBI fileEvidenceTAS
GeneDEF6AuthorityHGNC:2760Mapping file id50619 NCBI fileEvidenceTAS
GeneDEPDC1BAuthorityHGNC:24902Mapping file id55789 NCBI fileEvidenceTAS
GeneDIAPH3AuthorityHGNC:15480Mapping file id81624 NCBI fileEvidenceTAS
GeneDOCK1AuthorityHGNC:2987Mapping file id1793 NCBI fileEvidenceTAS
GeneDOCK10AuthorityHGNC:23479Mapping file id55619 NCBI fileEvidenceTAS
GeneDOCK2AuthorityHGNC:2988Mapping file id1794 NCBI fileEvidenceTAS
GeneDOCK3AuthorityHGNC:2989Mapping file id1795 NCBI fileEvidenceTAS
GeneDOCK4AuthorityHGNC:19192Mapping file id9732 NCBI fileEvidenceTAS
GeneDSG2AuthorityHGNC:3049Mapping file id1829 NCBI fileEvidenceTAS
GeneEMDAuthorityHGNC:3331Mapping file id2010 NCBI fileEvidenceTAS
GeneEPHA2AuthorityHGNC:3386Mapping file id1969 NCBI fileEvidenceTAS
GeneERBINAuthorityHGNC:15842Mapping file id55914 NCBI fileEvidenceTAS
GeneESYT1AuthorityHGNC:29534Mapping file id23344 NCBI fileEvidenceTAS
GeneGARRE1AuthorityHGNC:29016Mapping file id9710 NCBI fileEvidenceTAS
GeneGIT1AuthorityHGNC:4272Mapping file id28964 NCBI fileEvidenceTAS
GeneGIT2AuthorityHGNC:4273Mapping file id9815 NCBI fileEvidenceTAS
GeneIQGAP1AuthorityHGNC:6110Mapping file id8826 NCBI fileEvidenceTAS
GeneITGB1AuthorityHGNC:6153Mapping file id3688 NCBI fileEvidenceTAS
GeneLAMTOR1AuthorityHGNC:26068Mapping file id55004 NCBI fileEvidenceTAS
GeneLBRAuthorityHGNC:6518Mapping file id3930 NCBI fileEvidenceTAS
GeneLEMD3AuthorityHGNC:28887Mapping file id23592 NCBI fileEvidenceTAS
GeneLMAN1AuthorityHGNC:6631Mapping file id3998 NCBI fileEvidenceTAS
GeneMCAMAuthorityHGNC:6934Mapping file id4162 NCBI fileEvidenceTAS
GeneMCF2AuthorityHGNC:6940Mapping file id4168 NCBI fileEvidenceTAS
GeneMPP7AuthorityHGNC:26542Mapping file id143098 NCBI fileEvidenceTAS
GeneMTX1AuthorityHGNC:7504Mapping file id4580 NCBI fileEvidenceTAS
GeneNCF1AuthorityHGNC:7660Mapping file id653361 NCBI fileEvidenceTAS
GeneNCF2AuthorityHGNC:7661Mapping file id4688 NCBI fileEvidenceTAS
GeneNCF4AuthorityHGNC:7662Mapping file id4689 NCBI fileEvidenceTAS
GeneNCKAP1AuthorityHGNC:7666Mapping file id10787 NCBI fileEvidenceTAS
GeneNCKAP1LAuthorityHGNC:4862Mapping file id3071 NCBI fileEvidenceTAS
GeneNHSAuthorityHGNC:7820Mapping file id4810 NCBI fileEvidenceTAS
GeneOPHN1AuthorityHGNC:8148Mapping file id4983 NCBI fileEvidenceTAS
GenePAK1AuthorityHGNC:8590Mapping file id5058 NCBI fileEvidenceTAS
GenePAK2AuthorityHGNC:8591Mapping file id5062 NCBI fileEvidenceTAS
GenePAK4AuthorityHGNC:16059Mapping file id10298 NCBI fileEvidenceTAS
GenePGRMC2AuthorityHGNC:16089Mapping file id10424 NCBI fileEvidenceTAS
GenePIK3CAAuthorityHGNC:8975Mapping file id5290 NCBI fileEvidenceTAS
GenePIK3R1AuthorityHGNC:8979Mapping file id5295 NCBI fileEvidenceTAS
GenePIK3R2AuthorityHGNC:8980Mapping file id5296 NCBI fileEvidenceTAS
GenePIK3R3AuthorityHGNC:8981Mapping file id8503 NCBI fileEvidenceTAS
GenePLD2AuthorityHGNC:9068Mapping file id5338 NCBI fileEvidenceTAS
GenePREX1AuthorityHGNC:32594Mapping file id57580 NCBI fileEvidenceTAS
GeneRAB7AAuthorityHGNC:9788Mapping file id7879 NCBI fileEvidenceTAS
GeneRAC2AuthorityHGNC:9802Mapping file id5880 NCBI fileEvidenceTAS
GeneRACGAP1AuthorityHGNC:9804Mapping file id29127 NCBI fileEvidenceTAS
GeneSAMM50AuthorityHGNC:24276Mapping file id25813 NCBI fileEvidenceTAS
GeneSLITRK5AuthorityHGNC:20295Mapping file id26050 NCBI fileEvidenceTAS
GeneSTBD1AuthorityHGNC:24854Mapping file id8987 NCBI fileEvidenceTAS
GeneSWAP70AuthorityHGNC:17070Mapping file id23075 NCBI fileEvidenceTAS
GeneSYDE1AuthorityHGNC:25824Mapping file id85360 NCBI fileEvidenceTAS
GeneTAOK3AuthorityHGNC:18133Mapping file id51347 NCBI fileEvidenceTAS
GeneTFRCAuthorityHGNC:11763Mapping file id7037 NCBI fileEvidenceTAS
GeneTIAM1AuthorityHGNC:11805Mapping file id7074 NCBI fileEvidenceTAS
GeneTMPOAuthorityHGNC:11875Mapping file id7112 NCBI fileEvidenceTAS
GeneTRIOAuthorityHGNC:12303Mapping file id7204 NCBI fileEvidenceTAS
GeneVAMP3AuthorityHGNC:12644Mapping file id9341 NCBI fileEvidenceTAS
GeneVANGL1AuthorityHGNC:15512Mapping file id81839 NCBI fileEvidenceTAS
GeneVAPBAuthorityHGNC:12649Mapping file id9217 NCBI fileEvidenceTAS
GeneVAV1AuthorityHGNC:12657Mapping file id7409 NCBI fileEvidenceTAS
GeneVAV2AuthorityHGNC:12658Mapping file id7410 NCBI fileEvidenceTAS
GeneVAV3AuthorityHGNC:12659Mapping file id10451 NCBI fileEvidenceTAS
GeneVRK2AuthorityHGNC:12719Mapping file id7444 NCBI fileEvidenceTAS
GeneWASF2AuthorityHGNC:12733Mapping file id10163 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.