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.

G alpha (i) signalling events

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

Genes Reactome places in this mouse pathway, page 3 of 3
GenePlcb3Authority18797Mapping file id18797 NCBI fileEvidenceIEA
GenePlcb4Authority18798Mapping file id18798 NCBI fileEvidenceIEA
GenePmchAuthority110312Mapping file id110312 NCBI fileEvidenceIEA
GenePnocAuthority18155Mapping file id18155 NCBI fileEvidenceIEA
GenePomcAuthority18976Mapping file id18976 NCBI fileEvidenceIEA
GenePpbpAuthority57349Mapping file id57349 NCBI fileEvidenceIEA
GenePpp1caAuthority19045Mapping file id19045 NCBI fileEvidenceIEA
GenePpp1r1bAuthority19049Mapping file id19049 NCBI fileEvidenceIEA
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GenePpyAuthority19064Mapping file id19064 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkacbAuthority18749Mapping file id18749 NCBI fileEvidenceIEA
GenePrkar1aAuthority19084Mapping file id19084 NCBI fileEvidenceIEA
GenePrkar1bAuthority19085Mapping file id19085 NCBI fileEvidenceIEA
GenePrkar2bAuthority19088Mapping file id19088 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GenePrkcdAuthority18753Mapping file id18753 NCBI fileEvidenceIEA
GenePrkcgAuthority18752Mapping file id18752 NCBI fileEvidenceIEA
GenePsapAuthority19156Mapping file id19156 NCBI fileEvidenceIEA
GenePtgdr2Authority14764Mapping file id14764 NCBI fileEvidenceIEA
GenePtger3Authority19218Mapping file idENSMUSG00000040016 Ensembl fileEvidenceIEA
GenePyyAuthority217212Mapping file id217212 NCBI fileEvidenceIEA
GeneRgrAuthority57811Mapping file id57811 NCBI fileEvidenceIEA
GeneRgs1Authority50778Mapping file id50778 NCBI fileEvidenceIEA
GeneRgs11Authority50782Mapping file idENSMUSG00000024186 Ensembl fileEvidenceIEA
GeneRgs12Authority71729Mapping file id71729 NCBI fileEvidenceIEA
GeneRgs13Authority246709Mapping file id246709 NCBI fileEvidenceIEA
GeneRgs14Authority51791Mapping file id51791 NCBI fileEvidenceIEA
GeneRgs16Authority19734Mapping file id19734 NCBI fileEvidenceIEA
GeneRgs17Authority56533Mapping file id56533 NCBI fileEvidenceIEA
GeneRgs18Authority64214Mapping file id64214 NCBI fileEvidenceIEA
GeneRgs19Authority56470Mapping file id56470 NCBI fileEvidenceIEA
GeneRgs20Authority58175Mapping file id58175 NCBI fileEvidenceIEA
GeneRgs21Authority624910Mapping file id624910 NCBI fileEvidenceIEA
GeneRgs3Authority50780Mapping file id50780 NCBI fileEvidenceIEA
GeneRgs4Authority19736Mapping file id19736 NCBI fileEvidenceIEA
GeneRgs5Authority19737Mapping file id19737 NCBI fileEvidenceIEA
GeneRgs6Authority50779Mapping file id50779 NCBI fileEvidenceIEA
GeneRgs7Authority24012Mapping file id24012 NCBI fileEvidenceIEA
GeneRgs8Authority67792Mapping file id67792 NCBI fileEvidenceIEA
GeneRgs9Authority19739Mapping file id19739 NCBI fileEvidenceIEA
GeneRhoAuthority212541Mapping file id212541 NCBI fileEvidenceIEA
GeneRln3Authority212108Mapping file id212108 NCBI fileEvidenceIEA
GeneRrhAuthority20132Mapping file id20132 NCBI fileEvidenceIEA
GeneRxfp3Authority239336Mapping file id239336 NCBI fileEvidenceIEA
GeneRxfp4Authority242093Mapping file id242093 NCBI fileEvidenceIEA
GeneS1pr2Authority14739Mapping file id14739 NCBI fileEvidenceIEA
GeneS1pr3Authority13610Mapping file id13610 NCBI fileEvidenceIEA
GeneS1pr4Authority13611Mapping file id13611 NCBI fileEvidenceIEA
GeneS1pr5Authority94226Mapping file id94226 NCBI fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneSstAuthority20604Mapping file id20604 NCBI fileEvidenceIEA
GeneSstr1Authority20605Mapping file id20605 NCBI fileEvidenceIEA
GeneSstr2Authority20606Mapping file id20606 NCBI fileEvidenceIEA
GeneSstr3Authority20607Mapping file id20607 NCBI fileEvidenceIEA
GeneSstr4Authority20608Mapping file id20608 NCBI fileEvidenceIEA
GeneSstr5Authority20609Mapping file id20609 NCBI fileEvidenceIEA
GeneSucnr1Authority84112Mapping file id84112 NCBI fileEvidenceIEA
GeneTas1r1Authority110326Mapping file id110326 NCBI fileEvidenceIEA
GeneTas1r2Authority83770Mapping file id83770 NCBI fileEvidenceIEA
GeneTas1r3Authority83771Mapping file id83771 NCBI fileEvidenceIEA
GeneTas2r105Authority57252Mapping file id57252 NCBI fileEvidenceIEA
GeneTas2r107Authority387342Mapping file id387342 NCBI fileEvidenceIEA
GeneTas2r108Authority57253Mapping file id57253 NCBI fileEvidenceIEA
GeneTas2r118Authority387347Mapping file id387347 NCBI fileEvidenceIEA
GeneTas2r119Authority57254Mapping file id57254 NCBI fileEvidenceIEA
GeneTas2r120Authority387348Mapping file id387348 NCBI fileEvidenceIEA
GeneTas2r121Authority387349Mapping file id387349 NCBI fileEvidenceIEA
GeneTas2r126Authority387353Mapping file id387353 NCBI fileEvidenceIEA
GeneTas2r130Authority387355Mapping file id387355 NCBI fileEvidenceIEA
GeneTas2r131Authority387356Mapping file id387356 NCBI fileEvidenceIEA
GeneTas2r135Authority387512Mapping file id387512 NCBI fileEvidenceIEA
GeneTas2r136Authority353165Mapping file id353165 NCBI fileEvidenceIEA
GeneTas2r137Authority574417Mapping file id574417 NCBI fileEvidenceIEA
GeneTas2r138Authority387513Mapping file id387513 NCBI fileEvidenceIEA
GeneTas2r139Authority353148Mapping file id353148 NCBI fileEvidenceIEA
GeneTas2r140Authority387616Mapping file id387616 NCBI fileEvidenceIEA
GeneTas2r144Authority387515Mapping file id387515 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.