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.

RHO GTPase cycle

R-RNO-9012999 in Reactome release 97: under Signaling by Rho GTPases, with 404 genes placed in it by the mapping files and 18 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-9012999 (human), R-MMU-9012999 (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 404 genes in this rat pathway; showing 201 to 300, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this rat pathway, page 3 of 5
GeneItsn2Authority313934Mapping file id313934 NCBI fileEvidenceIEA
GeneJag1Authority29146Mapping file id29146 NCBI fileEvidenceIEA
GeneJupAuthority81679Mapping file id81679 NCBI fileEvidenceIEA
GeneKalrnAuthority84009Mapping file id84009 NCBI fileEvidenceIEA
GeneKctd13Authority293497Mapping file id293497 NCBI fileEvidenceIEA
GeneKidins220Authority116478Mapping file id116478 NCBI fileEvidenceIEA
GeneKif14Authority360849Mapping file id360849 NCBI fileEvidenceIEA
GeneKtn1Authority361029Mapping file id361029 NCBI fileEvidenceIEA
GeneLamtor1Authority308869Mapping file id308869 NCBI fileEvidenceIEA
GeneLamtor1l1Authority100361543Mapping file idENSRNOG00000004319 Ensembl fileEvidenceIEA
GeneLbrAuthority89789Mapping file idENSRNOG00000052574 Ensembl fileEvidenceIEA
GeneLckAuthority313050Mapping file id313050 NCBI fileEvidenceIEA
GeneLetm1Authority305457Mapping file id305457 NCBI fileEvidenceIEA
GeneLman1Authority116666Mapping file id116666 NCBI fileEvidenceIEA
GeneLmnb1Authority116685Mapping file id116685 NCBI fileEvidenceIEA
GeneMaco1Authority313618Mapping file id313618 NCBI fileEvidenceIEA
GeneMap3k11Authority309168Mapping file id309168 NCBI fileEvidenceIEA
GeneMcamAuthority78967Mapping file id78967 NCBI fileEvidenceIEA
GeneMcf2Authority317598Mapping file id317598 NCBI fileEvidenceIEA
GeneMcf2lAuthority117020Mapping file id117020 NCBI fileEvidenceIEA
GeneMpp7Authority307035Mapping file id307035 NCBI fileEvidenceIEA
GeneMsi2Authority360596Mapping file id360596 NCBI fileEvidenceIEA
GeneMtmr1Authority317296Mapping file id317296 NCBI fileEvidenceIEA
GeneMtrAuthority81522Mapping file id81522 NCBI fileEvidenceIEA
GeneMtx1Authority295241Mapping file idENSRNOG00000042977 Ensembl fileEvidenceIEA
GeneMuc13Authority207126Mapping file idENSRNOG00000001794 Ensembl fileEvidenceIEA
GeneMyo6Authority315840Mapping file id315840 NCBI fileEvidenceIEA
GeneMyo9aAuthority171296Mapping file id171296 NCBI fileEvidenceIEA
GeneMyo9bAuthority25486Mapping file idENSRNOG00000016256 Ensembl fileEvidenceIEA
GeneNcf1Authority114553Mapping file idENSRNOG00000001480 Ensembl fileEvidenceIEA
GeneNcf2Authority364018Mapping file idENSRNOG00000028016 Ensembl fileEvidenceIEA
GeneNcf4Authority500904Mapping file idENSRNOG00000006940 Ensembl fileEvidenceIEA
GeneNck1Authority300955Mapping file id300955 NCBI fileEvidenceIEA
GeneNck2Authority316369Mapping file id316369 NCBI fileEvidenceIEA
GeneNckap1Authority58823Mapping file id58823 NCBI fileEvidenceIEA
GeneNckap1lAuthority315348Mapping file id315348 NCBI fileEvidenceIEA
GeneNdufa5Authority25488Mapping file id25488 NCBI fileEvidenceIEA
GeneNdufs3Authority295923Mapping file idENSRNOG00000009155 Ensembl fileEvidenceIEA
GeneNet1Authority307098Mapping file id307098 NCBI fileEvidenceIEA
GeneNgefAuthority246217Mapping file idENSRNOG00000016653 Ensembl fileEvidenceIEA
GeneNhsAuthority317494Mapping file idENSRNOG00000030759 Ensembl fileEvidenceIEA
GeneNipsnap2Authority498174Mapping file id498174 NCBI fileEvidenceIEA
GeneNischAuthority306255Mapping file idENSRNOG00000018823 Ensembl fileEvidenceIEA
GeneNox1Authority114243Mapping file id114243 NCBI fileEvidenceIEA
GeneNox3Authority292279Mapping file id292279 NCBI fileEvidenceIEA
GeneNoxa1Authority311793Mapping file id311793 NCBI fileEvidenceIEA
GeneNoxo1Authority302976Mapping file id302976 NCBI fileEvidenceIEA
GeneNsfl1cAuthority83809Mapping file id83809 NCBI fileEvidenceIEA
GeneNudcAuthority29648Mapping file id29648 NCBI fileEvidenceIEA
GeneObscnAuthority338458Mapping file idENSRNOG00000058068 Ensembl fileEvidenceIEA
GeneOcrlAuthority317576Mapping file idENSRNOG00000003875 Ensembl fileEvidenceIEA
GeneOphn1Authority312108Mapping file id312108 NCBI fileEvidenceIEA
GeneOsbpl11Authority303888Mapping file id303888 NCBI fileEvidenceIEA
GenePak1Authority29431Mapping file id29431 NCBI fileEvidenceIEA
GenePak2Authority29432Mapping file id29432 NCBI fileEvidenceIEA
GenePak3Authority29433Mapping file id29433 NCBI fileEvidenceIEA
GenePak4Authority292756Mapping file id292756 NCBI fileEvidenceIEA
GenePak5Authority311450Mapping file id311450 NCBI fileEvidenceIEA
GenePak6Authority296078Mapping file idENSRNOG00000007925 Ensembl fileEvidenceIEA
GenePard6aAuthority307799Mapping file idENSRNOG00000017746 Ensembl fileEvidenceIEA
GenePard6bAuthority362279Mapping file id362279 NCBI fileEvidenceIEA
GenePcdh7Authority360942Mapping file id360942 NCBI fileEvidenceIEA
GenePde5aAuthority171115Mapping file id171115 NCBI fileEvidenceIEA
GenePeak1Authority315686Mapping file id315686 NCBI fileEvidenceIEA
GenePgrmc2Authority361940Mapping file id361940 NCBI fileEvidenceIEA
GenePhipAuthority315843Mapping file idENSRNOG00000008652 Ensembl fileEvidenceIEA
GenePicalmAuthority89816Mapping file id89816 NCBI fileEvidenceIEA
GenePik3caAuthority170911Mapping file id170911 NCBI fileEvidenceIEA
GenePik3r1Authority25513Mapping file id25513 NCBI fileEvidenceIEA
GenePik3r3Authority60664Mapping file id60664 NCBI fileEvidenceIEA
GenePkn1Authority29355Mapping file id29355 NCBI fileEvidenceIEA
GenePkn2Authority207122Mapping file idENSRNOG00000011317 Ensembl fileEvidenceIEA
GenePkp4Authority295625Mapping file idENSRNOG00000005504 Ensembl fileEvidenceIEA
GenePld1Authority25096Mapping file id25096 NCBI fileEvidenceIEA
GenePld2Authority25097Mapping file id25097 NCBI fileEvidenceIEA
GenePlekhg1Authority679812Mapping file idENSRNOG00000016011 Ensembl fileEvidenceIEA
GenePlekhg2Authority292750Mapping file idENSRNOG00000030266 Ensembl fileEvidenceIEA
GenePlekhg3Authority314249Mapping file id314249 NCBI fileEvidenceIEA
GenePlekhg5Authority310999Mapping file id310999 NCBI fileEvidenceIEA
GenePlekhg6Authority100362241Mapping file idENSRNOG00000019528 Ensembl fileEvidenceIEA
GenePlxna1Authority362398Mapping file idENSRNOG00000017003 Ensembl fileEvidenceIEA
GenePlxnd1Authority312652Mapping file idENSRNOG00000025209 Ensembl fileEvidenceIEA
GenePrag1Authority306506Mapping file id306506 NCBI fileEvidenceIEA
GenePrex1Authority311647Mapping file id311647 NCBI fileEvidenceIEA
GenePrex2Authority312912Mapping file idENSRNOG00000005391 Ensembl fileEvidenceIEA
GenePtk2bAuthority50646Mapping file id50646 NCBI fileEvidenceIEA
GenePtpn13Authority498331Mapping file id498331 NCBI fileEvidenceIEA
GeneRab7aAuthority29448Mapping file id29448 NCBI fileEvidenceIEA
GeneRac1Authority363875Mapping file id363875 NCBI fileEvidenceIEA
GeneRac2Authority366957Mapping file idENSRNOG00000007350 Ensembl fileEvidenceIEA
GeneRac3Authority688319Mapping file id688319 NCBI fileEvidenceIEA
GeneRacgap1Authority315298Mapping file idENSRNOG00000049033 Ensembl fileEvidenceIEA
GeneRalbp1Authority84014Mapping file id84014 NCBI fileEvidenceIEA
GeneRalgapa1Authority56785Mapping file id56785 NCBI fileEvidenceIEA
GeneRapgef1Authority63881Mapping file idENSRNOG00000014316 Ensembl fileEvidenceIEA
GeneRasal2Authority304893Mapping file id304893 NCBI fileEvidenceIEA
GeneRasgrf2Authority114513Mapping file id114513 NCBI fileEvidenceIEA
GeneRbbp6Authority308968Mapping file id308968 NCBI fileEvidenceIEA
GeneRbmxAuthority302855Mapping file id302855 NCBI fileEvidenceIEA
GeneRhoaAuthority117273Mapping file id117273 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

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.