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.

GPCR downstream signalling

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

Genes Reactome places in this mouse pathway, page 3 of 6
GeneGalr2Authority14428Mapping file id14428 NCBI fileEvidenceIEA
GeneGalr3Authority14429Mapping file id14429 NCBI fileEvidenceIEA
GeneGastAuthority14459Mapping file id14459 NCBI fileEvidenceIEA
GeneGcgAuthority14526Mapping file id14526 NCBI fileEvidenceIEA
GeneGcgrAuthority14527Mapping file id14527 NCBI fileEvidenceIEA
GeneGhrhAuthority14601Mapping file id14601 NCBI fileEvidenceIEA
GeneGhrhrAuthority14602Mapping file id14602 NCBI fileEvidenceIEA
GeneGhrlAuthority58991Mapping file id58991 NCBI fileEvidenceIEA
GeneGhsrAuthority208188Mapping file id208188 NCBI fileEvidenceIEA
GeneGipAuthority14607Mapping file id14607 NCBI fileEvidenceIEA
GeneGiprAuthority381853Mapping file id381853 NCBI fileEvidenceIEA
GeneGlp1rAuthority14652Mapping file id14652 NCBI fileEvidenceIEA
GeneGlp2rAuthority93896Mapping file id93896 NCBI fileEvidenceIEA
GeneGna11Authority14672Mapping file id14672 NCBI fileEvidenceIEA
GeneGna12Authority14673Mapping file id14673 NCBI fileEvidenceIEA
GeneGna13Authority14674Mapping file id14674 NCBI fileEvidenceIEA
GeneGna14Authority14675Mapping file id14675 NCBI fileEvidenceIEA
GeneGnai1Authority14677Mapping file id14677 NCBI fileEvidenceIEA
GeneGnai2Authority14678Mapping file id14678 NCBI fileEvidenceIEA
GeneGnai3Authority14679Mapping file id14679 NCBI fileEvidenceIEA
GeneGnalAuthority14680Mapping file id14680 NCBI fileEvidenceIEA
GeneGnaqAuthority14682Mapping file id14682 NCBI fileEvidenceIEA
GeneGnasAuthority14683Mapping file id14683 NCBI fileEvidenceIEA
GeneGnat1Authority14685Mapping file id14685 NCBI fileEvidenceIEA
GeneGnat2Authority14686Mapping file id14686 NCBI fileEvidenceIEA
GeneGnat3Authority242851Mapping file id242851 NCBI fileEvidenceIEA
GeneGnazAuthority14687Mapping file id14687 NCBI fileEvidenceIEA
GeneGnb1Authority14688Mapping file id14688 NCBI fileEvidenceIEA
GeneGnb2Authority14693Mapping file id14693 NCBI fileEvidenceIEA
GeneGnb3Authority14695Mapping file id14695 NCBI fileEvidenceIEA
GeneGnb4Authority14696Mapping file id14696 NCBI fileEvidenceIEA
GeneGnb5Authority14697Mapping file id14697 NCBI fileEvidenceIEA
GeneGng10Authority14700Mapping file id14700 NCBI fileEvidenceIEA
GeneGng11Authority66066Mapping file id66066 NCBI fileEvidenceIEA
GeneGng12Authority14701Mapping file id14701 NCBI fileEvidenceIEA
GeneGng13Authority64337Mapping file id64337 NCBI fileEvidenceIEA
GeneGng2Authority14702Mapping file id14702 NCBI fileEvidenceIEA
GeneGng3Authority14704Mapping file id14704 NCBI fileEvidenceIEA
GeneGng4Authority14706Mapping file id14706 NCBI fileEvidenceIEA
GeneGng5Authority14707Mapping file id14707 NCBI fileEvidenceIEA
GeneGng7Authority14708Mapping file id14708 NCBI fileEvidenceIEA
GeneGng8Authority14709Mapping file id14709 NCBI fileEvidenceIEA
GeneGngt1Authority14699Mapping file id14699 NCBI fileEvidenceIEA
GeneGngt2Authority14710Mapping file id14710 NCBI fileEvidenceIEA
GeneGnrh1Authority14714Mapping file id14714 NCBI fileEvidenceIEA
GeneGnrhrAuthority14715Mapping file id14715 NCBI fileEvidenceIEA
GeneGpbar1Authority227289Mapping file id227289 NCBI fileEvidenceIEA
GeneGper1Authority76854Mapping file id76854 NCBI fileEvidenceIEA
GeneGpha2Authority170458Mapping file id170458 NCBI fileEvidenceIEA
GeneGphb5Authority217674Mapping file id217674 NCBI fileEvidenceIEA
GeneGpr132Authority56696Mapping file id56696 NCBI fileEvidenceIEA
GeneGpr143Authority18241Mapping file id18241 NCBI fileEvidenceIEA
GeneGpr15Authority71223Mapping file id71223 NCBI fileEvidenceIEA
GeneGpr150Authority238725Mapping file id238725 NCBI fileEvidenceIEA
GeneGpr17Authority574402Mapping file id574402 NCBI fileEvidenceIEA
GeneGpr176Authority381413Mapping file id381413 NCBI fileEvidenceIEA
GeneGpr18Authority110168Mapping file id110168 NCBI fileEvidenceIEA
GeneGpr183Authority321019Mapping file id321019 NCBI fileEvidenceIEA
GeneGpr20Authority239530Mapping file id239530 NCBI fileEvidenceIEA
GeneGpr25Authority383563Mapping file id383563 NCBI fileEvidenceIEA
GeneGpr27Authority14761Mapping file id14761 NCBI fileEvidenceIEA
GeneGpr31bAuthority436440Mapping file id436440 NCBI fileEvidenceIEA
GeneGpr37Authority14763Mapping file id14763 NCBI fileEvidenceIEA
GeneGpr37l1Authority171469Mapping file id171469 NCBI fileEvidenceIEA
GeneGpr39Authority71111Mapping file idENSMUSG00000026343 Ensembl fileEvidenceIEA
GeneGpr4Authority319197Mapping file id319197 NCBI fileEvidenceIEA
GeneGpr45Authority93690Mapping file id93690 NCBI fileEvidenceIEA
GeneGpr55Authority227326Mapping file id227326 NCBI fileEvidenceIEA
GeneGpr65Authority14744Mapping file id14744 NCBI fileEvidenceIEA
GeneGpr68Authority238377Mapping file id238377 NCBI fileEvidenceIEA
GeneGpr83Authority14608Mapping file id14608 NCBI fileEvidenceIEA
GeneGpr84Authority80910Mapping file id80910 NCBI fileEvidenceIEA
GeneGprc6aAuthority210198Mapping file id210198 NCBI fileEvidenceIEA
GeneGpsm1Authority67839Mapping file id67839 NCBI fileEvidenceIEA
GeneGpsm2Authority76123Mapping file id76123 NCBI fileEvidenceIEA
GeneGpsm3Authority106512Mapping file id106512 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrk2Authority110355Mapping file id110355 NCBI fileEvidenceIEA
GeneGrk3Authority320129Mapping file id320129 NCBI fileEvidenceIEA
GeneGrk5Authority14773Mapping file id14773 NCBI fileEvidenceIEA
GeneGrk6Authority26385Mapping file id26385 NCBI fileEvidenceIEA
GeneGrm1Authority14816Mapping file id14816 NCBI fileEvidenceIEA
GeneGrm2Authority108068Mapping file id108068 NCBI fileEvidenceIEA
GeneGrm3Authority108069Mapping file id108069 NCBI fileEvidenceIEA
GeneGrm4Authority268934Mapping file id268934 NCBI fileEvidenceIEA
GeneGrm5Authority108071Mapping file id108071 NCBI fileEvidenceIEA
GeneGrm6Authority108072Mapping file id108072 NCBI fileEvidenceIEA
GeneGrm7Authority108073Mapping file id108073 NCBI fileEvidenceIEA
GeneGrm8Authority14823Mapping file id14823 NCBI fileEvidenceIEA
GeneGrpAuthority225642Mapping file id225642 NCBI fileEvidenceIEA
GeneGrprAuthority14829Mapping file id14829 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHcAuthority15139Mapping file id15139 NCBI fileEvidenceIEA
GeneHcar1Authority243270Mapping file id243270 NCBI fileEvidenceIEA
GeneHcar2Authority80885Mapping file id80885 NCBI fileEvidenceIEA
GeneHcrtAuthority15171Mapping file id15171 NCBI fileEvidenceIEA
GeneHcrtr1Authority230777Mapping file id230777 NCBI fileEvidenceIEA
GeneHcrtr2Authority387285Mapping file id387285 NCBI fileEvidenceIEA
GeneHebp1Authority15199Mapping file id15199 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 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.