Skip to content

Create an account and get up to 25% off.

Order

Pathway Rat Rattus norvegicus

Read this first

Every rat pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

CDC42 GTPase cycle

R-RNO-9013148 in Reactome release 97: under RHO GTPase cycle, with 91 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-9013148 (human), R-MMU-9013148 (mouse). 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 rat 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 rat pathway

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

Genes Reactome places in this rat pathway, page 1 of 1
GeneAbrAuthority287537Mapping file id287537 NCBI fileEvidenceIEA
GeneArap1Authority361617Mapping file id361617 NCBI fileEvidenceIEA
GeneArap2Authority305367Mapping file id305367 NCBI fileEvidenceIEA
GeneArap3Authority361314Mapping file idENSRNOG00000055527 Ensembl fileEvidenceIEA
GeneArhgap1Authority311193Mapping file idENSRNOG00000016610 Ensembl fileEvidenceIEA
GeneArhgap10Authority688429Mapping file id688429 NCBI fileEvidenceIEA
GeneArhgap17Authority63994Mapping file id63994 NCBI fileEvidenceIEA
GeneArhgap20Authority367085Mapping file id367085 NCBI fileEvidenceIEA
GeneArhgap21Authority307178Mapping file idENSRNOG00000008659 Ensembl fileEvidenceIEA
GeneArhgap22Authority306279Mapping file id306279 NCBI fileEvidenceIEA
GeneArhgap24Authority305156Mapping file id305156 NCBI fileEvidenceIEA
GeneArhgap26Authority307459Mapping file id307459 NCBI fileEvidenceIEA
GeneArhgap27Authority303583Mapping file id303583 NCBI fileEvidenceIEA
GeneArhgap29Authority310833Mapping file id310833 NCBI fileEvidenceIEA
GeneArhgap30Authority498282Mapping file id498282 NCBI fileEvidenceIEA
GeneArhgap31Authority288093Mapping file id288093 NCBI fileEvidenceIEA
GeneArhgap32Authority315530Mapping file idENSRNOG00000008709 Ensembl fileEvidenceIEA
GeneArhgap33Authority100362311Mapping file idENSRNOG00000024677 Ensembl fileEvidenceIEA
GeneArhgap35Authority306400Mapping file id306400 NCBI fileEvidenceIEA
GeneArhgap4Authority246249Mapping file id246249 NCBI fileEvidenceIEA
GeneArhgap40Authority296323Mapping file id296323 NCBI fileEvidenceIEA
GeneArhgap42Authority500943Mapping file idENSRNOG00000026821 Ensembl fileEvidenceIEA
GeneArhgap44Authority303222Mapping file id303222 NCBI fileEvidenceIEA
GeneArhgap45Authority314618Mapping file id314618 NCBI fileEvidenceIEA
GeneArhgap5Authority299012Mapping file id299012 NCBI fileEvidenceIEA
GeneArhgap9Authority362893Mapping file id362893 NCBI fileEvidenceIEA
GeneArhgdiaAuthority360678Mapping file id360678 NCBI fileEvidenceIEA
GeneArhgdibAuthority362456Mapping file id362456 NCBI fileEvidenceIEA
GeneArhgdigAuthority360500Mapping file id360500 NCBI fileEvidenceIEA
GeneArhgef10Authority306618Mapping file id306618 NCBI fileEvidenceIEA
GeneArhgef11Authority78966Mapping file id78966 NCBI fileEvidenceIEA
GeneArhgef12Authority367072Mapping file idENSRNOG00000008924 Ensembl fileEvidenceIEA
GeneArhgef15Authority287418Mapping file id287418 NCBI fileEvidenceIEA
GeneArhgef16Authority687105Mapping file id687105 NCBI fileEvidenceIEA
GeneArhgef19Authority362648Mapping file id362648 NCBI fileEvidenceIEA
GeneArhgef25Authority314904Mapping file idENSRNOG00000005034 Ensembl fileEvidenceIEA
GeneArhgef26Authority310460Mapping file id310460 NCBI fileEvidenceIEA
GeneArhgef4Authority301334Mapping file id301334 NCBI fileEvidenceIEA
GeneArhgef5Authority140898Mapping file id140898 NCBI fileEvidenceIEA
GeneArhgef6Authority363509Mapping file id363509 NCBI fileEvidenceIEA
GeneArhgef9Authority66013Mapping file id66013 NCBI fileEvidenceIEA
GeneBcrAuthority309696Mapping file id309696 NCBI fileEvidenceIEA
GeneCdc42Authority64465Mapping file id64465 NCBI fileEvidenceIEA
GeneDef6Authority309642Mapping file idENSRNOG00000000502 Ensembl fileEvidenceIEA
GeneDepdc1bAuthority310074Mapping file id310074 NCBI fileEvidenceIEA
GeneDlc1Authority58834Mapping file idENSRNOG00000010780 Ensembl fileEvidenceIEA
GeneDnmbpAuthority309362Mapping file id309362 NCBI fileEvidenceIEA
GeneDock10Authority301556Mapping file idENSRNOG00000053200 Ensembl fileEvidenceIEA
GeneDock11Authority313438Mapping file id313438 NCBI fileEvidenceIEA
GeneDock6Authority367039Mapping file idENSRNOG00000010652 Ensembl fileEvidenceIEA
GeneDock7Authority313388Mapping file id313388 NCBI fileEvidenceIEA
GeneDock8Authority499337Mapping file idENSRNOG00000015894 Ensembl fileEvidenceIEA
GeneEct2Authority361921Mapping file id361921 NCBI fileEvidenceIEA
GeneFam13bAuthority291694Mapping file id291694 NCBI fileEvidenceIEA
GeneFarp1Authority306183Mapping file id306183 NCBI fileEvidenceIEA
GeneFgd1Authority363460Mapping file id363460 NCBI fileEvidenceIEA
GeneFgd2Authority309653Mapping file id309653 NCBI fileEvidenceIEA
GeneFgd3Authority361223Mapping file idENSRNOG00000016225 Ensembl fileEvidenceIEA
GeneFgd4Authority246174Mapping file id246174 NCBI fileEvidenceIEA
GeneGmipAuthority306357Mapping file id306357 NCBI fileEvidenceIEA
GeneGna13Authority303634Mapping file id303634 NCBI fileEvidenceIEA
GeneItsn1Authority29491Mapping file id29491 NCBI fileEvidenceIEA
GeneKtn1Authority361029Mapping file id361029 NCBI fileEvidenceIEA
GeneLbrAuthority89789Mapping file idENSRNOG00000052574 Ensembl fileEvidenceIEA
GeneMcf2Authority317598Mapping file id317598 NCBI fileEvidenceIEA
GeneMcf2lAuthority117020Mapping file id117020 NCBI fileEvidenceIEA
GeneMyo9bAuthority25486Mapping file idENSRNOG00000016256 Ensembl fileEvidenceIEA
GeneNgefAuthority246217Mapping file idENSRNOG00000016653 Ensembl fileEvidenceIEA
GeneOphn1Authority312108Mapping file id312108 NCBI fileEvidenceIEA
GenePik3r1Authority25513Mapping file id25513 NCBI fileEvidenceIEA
GenePlekhg1Authority679812Mapping file idENSRNOG00000016011 Ensembl fileEvidenceIEA
GenePlekhg2Authority292750Mapping file idENSRNOG00000030266 Ensembl fileEvidenceIEA
GenePlekhg3Authority314249Mapping file id314249 NCBI fileEvidenceIEA
GenePrex1Authority311647Mapping file id311647 NCBI fileEvidenceIEA
GenePrex2Authority312912Mapping file idENSRNOG00000005391 Ensembl fileEvidenceIEA
GeneRacgap1Authority315298Mapping file idENSRNOG00000049033 Ensembl fileEvidenceIEA
GeneRalbp1Authority84014Mapping file id84014 NCBI fileEvidenceIEA
GeneRasgrf2Authority114513Mapping file id114513 NCBI fileEvidenceIEA
GeneSpata13Authority305938Mapping file id305938 NCBI fileEvidenceIEA
GeneSrgap1Authority314903Mapping file id314903 NCBI fileEvidenceIEA
GeneSrgap2Authority360840Mapping file id360840 NCBI fileEvidenceIEA
GeneSrgap3Authority500287Mapping file id500287 NCBI fileEvidenceIEA
GeneStard13Authority498130Mapping file id498130 NCBI fileEvidenceIEA
GeneStard8Authority312113Mapping file id312113 NCBI fileEvidenceIEA
GeneSyde1Authority362842Mapping file id362842 NCBI fileEvidenceIEA
GeneTagapAuthority308097Mapping file id308097 NCBI fileEvidenceIEA
GeneTiam1Authority304109Mapping file id304109 NCBI fileEvidenceIEA
GeneTrioAuthority310192Mapping file id310192 NCBI fileEvidenceIEA
GeneVav2Authority296603Mapping file idENSRNOG00000007422 Ensembl fileEvidenceIEA
GeneVav3Authority295378Mapping file id295378 NCBI fileEvidenceIEA
GeneYkt6Authority64351Mapping file id64351 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 64,140 rat pairs both place.

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