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 (q) signalling events

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

Genes Reactome places in this mouse pathway, page 1 of 3
GeneAbhd12Authority76192Mapping file id76192 NCBI fileEvidenceIEA
GeneAbhd6Authority66082Mapping file id66082 NCBI fileEvidenceIEA
GeneAdra1aAuthority11549Mapping file id11549 NCBI fileEvidenceIEA
GeneAdra1bAuthority11548Mapping file idENSMUSG00000050541 Ensembl fileEvidenceIEA
GeneAdra1dAuthority11550Mapping file idENSMUSG00000027335 Ensembl fileEvidenceIEA
GeneAgtr1aAuthority11607Mapping file id11607 NCBI fileEvidenceIEA
GeneAnxa1Authority16952Mapping file id16952 NCBI fileEvidenceIEA
GeneAppAuthority11820Mapping file id11820 NCBI fileEvidenceIEA
GeneArhgef25Authority52666Mapping file id52666 NCBI fileEvidenceIEA
GeneAvpAuthority11998Mapping file id11998 NCBI fileEvidenceIEA
GeneAvpr1aAuthority54140Mapping file id54140 NCBI fileEvidenceIEA
GeneAvpr1bAuthority26361Mapping file id26361 NCBI fileEvidenceIEA
GeneBdkrb1Authority12061Mapping file id12061 NCBI fileEvidenceIEA
GeneBdkrb2Authority12062Mapping file id12062 NCBI fileEvidenceIEA
GeneBrs3Authority12209Mapping file id12209 NCBI fileEvidenceIEA
GeneBtkAuthority12229Mapping file id12229 NCBI fileEvidenceIEA
GeneCasrAuthority12374Mapping file id12374 NCBI fileEvidenceIEA
GeneCckAuthority12424Mapping file id12424 NCBI fileEvidenceIEA
GeneCckarAuthority12425Mapping file id12425 NCBI fileEvidenceIEA
GeneCckbrAuthority12426Mapping file id12426 NCBI fileEvidenceIEA
GeneCcl6Authority20305Mapping file id20305 NCBI fileEvidenceIEA
GeneCcl9Authority20308Mapping file id20308 NCBI fileEvidenceIEA
GeneChrm1Authority12669Mapping file id12669 NCBI fileEvidenceIEA
GeneChrm3Authority12671Mapping file id12671 NCBI fileEvidenceIEA
GeneChrm5Authority213788Mapping file id213788 NCBI fileEvidenceIEA
GeneCreb1Authority12912Mapping file id12912 NCBI fileEvidenceIEA
GeneCysltr1Authority58861Mapping file id58861 NCBI fileEvidenceIEA
GeneCysltr2Authority70086Mapping file id70086 NCBI fileEvidenceIEA
GeneDaglaAuthority269060Mapping file id269060 NCBI fileEvidenceIEA
GeneDaglbAuthority231871Mapping file id231871 NCBI fileEvidenceIEA
GeneDgkaAuthority13139Mapping file id13139 NCBI fileEvidenceIEA
GeneDgkbAuthority217480Mapping file id217480 NCBI fileEvidenceIEA
GeneDgkdAuthority227333Mapping file id227333 NCBI fileEvidenceIEA
GeneDgkeAuthority56077Mapping file id56077 NCBI fileEvidenceIEA
GeneDgkgAuthority110197Mapping file id110197 NCBI fileEvidenceIEA
GeneDgkhAuthority380921Mapping file id380921 NCBI fileEvidenceIEA
GeneDgkiAuthority320127Mapping file id320127 NCBI fileEvidenceIEA
GeneDgkkAuthority331374Mapping file idENSMUSG00000062393 Ensembl fileEvidenceIEA
GeneDgkqAuthority110524Mapping file id110524 NCBI fileEvidenceIEA
GeneDgkzAuthority104418Mapping file id104418 NCBI fileEvidenceIEA
GeneEdn1Authority13614Mapping file id13614 NCBI fileEvidenceIEA
GeneEdn2Authority13615Mapping file id13615 NCBI fileEvidenceIEA
GeneEdn3Authority13616Mapping file id13616 NCBI fileEvidenceIEA
GeneEdnraAuthority13617Mapping file id13617 NCBI fileEvidenceIEA
GeneEdnrbAuthority13618Mapping file id13618 NCBI fileEvidenceIEA
GeneEgfrAuthority13649Mapping file id13649 NCBI fileEvidenceIEA
GeneF2Authority14061Mapping file id14061 NCBI fileEvidenceIEA
GeneF2rAuthority14062Mapping file id14062 NCBI fileEvidenceIEA
GeneF2rl1Authority14063Mapping file id14063 NCBI fileEvidenceIEA
GeneF2rl2Authority14064Mapping file id14064 NCBI fileEvidenceIEA
GeneF2rl3Authority14065Mapping file id14065 NCBI fileEvidenceIEA
GeneFfar1Authority233081Mapping file id233081 NCBI fileEvidenceIEA
GeneFfar2Authority233079Mapping file id233079 NCBI fileEvidenceIEA
GeneFfar3Authority233080Mapping file id233080 NCBI fileEvidenceIEA
GeneFfar4Authority107221Mapping file id107221 NCBI fileEvidenceIEA
GeneFpr2Authority14289Mapping file id14289 NCBI fileEvidenceIEA
GeneGastAuthority14459Mapping file id14459 NCBI fileEvidenceIEA
GeneGcgAuthority14526Mapping file id14526 NCBI fileEvidenceIEA
GeneGcgrAuthority14527Mapping file id14527 NCBI fileEvidenceIEA
GeneGhrlAuthority58991Mapping file id58991 NCBI fileEvidenceIEA
GeneGhsrAuthority208188Mapping file id208188 NCBI fileEvidenceIEA
GeneGna11Authority14672Mapping file id14672 NCBI fileEvidenceIEA
GeneGna14Authority14675Mapping file id14675 NCBI fileEvidenceIEA
GeneGnaqAuthority14682Mapping file id14682 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
GeneGpr132Authority56696Mapping file id56696 NCBI fileEvidenceIEA
GeneGpr143Authority18241Mapping file id18241 NCBI fileEvidenceIEA
GeneGpr17Authority574402Mapping file id574402 NCBI fileEvidenceIEA
GeneGpr39Authority71111Mapping file idENSMUSG00000026343 Ensembl fileEvidenceIEA
GeneGpr4Authority319197Mapping file id319197 NCBI fileEvidenceIEA
GeneGpr65Authority14744Mapping file id14744 NCBI fileEvidenceIEA
GeneGpr68Authority238377Mapping file id238377 NCBI fileEvidenceIEA
GeneGprc6aAuthority210198Mapping file id210198 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrk2Authority110355Mapping file id110355 NCBI fileEvidenceIEA
GeneGrm1Authority14816Mapping file id14816 NCBI fileEvidenceIEA
GeneGrm5Authority108071Mapping file id108071 NCBI fileEvidenceIEA
GeneGrpAuthority225642Mapping file id225642 NCBI fileEvidenceIEA
GeneGrprAuthority14829Mapping file id14829 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHcrtAuthority15171Mapping file id15171 NCBI fileEvidenceIEA
GeneHcrtr1Authority230777Mapping file id230777 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.