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 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 3
GeneHcrtr2Authority387285Mapping file id387285 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneHrh1Authority15465Mapping file id15465 NCBI fileEvidenceIEA
GeneHtr2aAuthority15558Mapping file id15558 NCBI fileEvidenceIEA
GeneHtr2bAuthority15559Mapping file id15559 NCBI fileEvidenceIEA
GeneHtr2cAuthority15560Mapping file id15560 NCBI fileEvidenceIEA
GeneItpr1Authority16438Mapping file id16438 NCBI fileEvidenceIEA
GeneItpr2Authority16439Mapping file id16439 NCBI fileEvidenceIEA
GeneItpr3Authority16440Mapping file id16440 NCBI fileEvidenceIEA
GeneKalrnAuthority545156Mapping file id545156 NCBI fileEvidenceIEA
GeneKiss1Authority280287Mapping file id280287 NCBI fileEvidenceIEA
GeneKiss1rAuthority114229Mapping file id114229 NCBI fileEvidenceIEA
GeneKng2Authority385643Mapping file id385643 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneLpar1Authority14745Mapping file id14745 NCBI fileEvidenceIEA
GeneLpar2Authority53978Mapping file id53978 NCBI fileEvidenceIEA
GeneLpar3Authority65086Mapping file id65086 NCBI fileEvidenceIEA
GeneLpar4Authority78134Mapping file id78134 NCBI fileEvidenceIEA
GeneLpar5Authority381810Mapping file id381810 NCBI fileEvidenceIEA
GeneLpar6Authority67168Mapping file id67168 NCBI fileEvidenceIEA
GeneLtb4r1Authority16995Mapping file id16995 NCBI fileEvidenceIEA
GeneLtb4r2Authority57260Mapping file id57260 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMchr1Authority207911Mapping file id207911 NCBI fileEvidenceIEA
GeneMgllAuthority23945Mapping file id23945 NCBI fileEvidenceIEA
GeneMmp3Authority17392Mapping file id17392 NCBI fileEvidenceIEA
GeneNmbAuthority68039Mapping file id68039 NCBI fileEvidenceIEA
GeneNmbrAuthority18101Mapping file id18101 NCBI fileEvidenceIEA
GeneNmsAuthority433292Mapping file id433292 NCBI fileEvidenceIEA
GeneNmuAuthority56183Mapping file id56183 NCBI fileEvidenceIEA
GeneNmur1Authority14767Mapping file id14767 NCBI fileEvidenceIEA
GeneNmur2Authority216749Mapping file id216749 NCBI fileEvidenceIEA
GeneNpffAuthority54615Mapping file id54615 NCBI fileEvidenceIEA
GeneNpffr1Authority237362Mapping file id237362 NCBI fileEvidenceIEA
GeneNpffr2Authority104443Mapping file id104443 NCBI fileEvidenceIEA
GeneNpsAuthority100043254Mapping file id100043254 NCBI fileEvidenceIEA
GeneNpsr1Authority319239Mapping file id319239 NCBI fileEvidenceIEA
GeneNtsAuthority67405Mapping file id67405 NCBI fileEvidenceIEA
GeneNtsr1Authority18216Mapping file id18216 NCBI fileEvidenceIEA
GeneNtsr2Authority18217Mapping file id18217 NCBI fileEvidenceIEA
GeneOpn4Authority30044Mapping file id30044 NCBI fileEvidenceIEA
GeneOxtAuthority18429Mapping file id18429 NCBI fileEvidenceIEA
GeneOxtrAuthority18430Mapping file id18430 NCBI fileEvidenceIEA
GeneP2ry1Authority18441Mapping file id18441 NCBI fileEvidenceIEA
GeneP2ry10Authority78826Mapping file id78826 NCBI fileEvidenceIEA
GeneP2ry2Authority18442Mapping file id18442 NCBI fileEvidenceIEA
GeneP2ry6Authority233571Mapping file id233571 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePlcb1Authority18795Mapping file id18795 NCBI fileEvidenceIEA
GenePlcb2Authority18796Mapping file id18796 NCBI fileEvidenceIEA
GenePlcb3Authority18797Mapping file id18797 NCBI fileEvidenceIEA
GenePlcb4Authority18798Mapping file id18798 NCBI fileEvidenceIEA
GenePmchAuthority110312Mapping file id110312 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GenePrkcdAuthority18753Mapping file id18753 NCBI fileEvidenceIEA
GenePrkceAuthority18754Mapping file id18754 NCBI fileEvidenceIEA
GenePrkchAuthority18755Mapping file id18755 NCBI fileEvidenceIEA
GenePrkcqAuthority18761Mapping file id18761 NCBI fileEvidenceIEA
GeneProk1Authority246691Mapping file id246691 NCBI fileEvidenceIEA
GeneProk2Authority50501Mapping file id50501 NCBI fileEvidenceIEA
GeneProkr1Authority58182Mapping file id58182 NCBI fileEvidenceIEA
GeneProkr2Authority246313Mapping file id246313 NCBI fileEvidenceIEA
GenePtafrAuthority19204Mapping file id19204 NCBI fileEvidenceIEA
GenePtger1Authority19216Mapping file id19216 NCBI fileEvidenceIEA
GenePtgfrAuthority19220Mapping file id19220 NCBI fileEvidenceIEA
GeneQrfpAuthority227717Mapping file id227717 NCBI fileEvidenceIEA
GeneQrfprAuthority229214Mapping file id229214 NCBI fileEvidenceIEA
GeneQrfprlAuthority243407Mapping file id243407 NCBI fileEvidenceIEA
GeneRgs1Authority50778Mapping file id50778 NCBI fileEvidenceIEA
GeneRgs13Authority246709Mapping file id246709 NCBI fileEvidenceIEA
GeneRgs16Authority19734Mapping file id19734 NCBI fileEvidenceIEA
GeneRgs17Authority56533Mapping file id56533 NCBI fileEvidenceIEA
GeneRgs18Authority64214Mapping file id64214 NCBI fileEvidenceIEA
GeneRgs19Authority56470Mapping file id56470 NCBI fileEvidenceIEA
GeneRgs2Authority19735Mapping file id19735 NCBI fileEvidenceIEA
GeneRgs21Authority624910Mapping file id624910 NCBI fileEvidenceIEA
GeneRgs3Authority50780Mapping file id50780 NCBI fileEvidenceIEA
GeneRgs4Authority19736Mapping file id19736 NCBI fileEvidenceIEA
GeneRgs5Authority19737Mapping file id19737 NCBI fileEvidenceIEA
GeneRgsl1Authority240816Mapping file id240816 NCBI fileEvidenceIEA
GeneRps6ka1Authority20111Mapping file id20111 NCBI fileEvidenceIEA
GeneRps6ka2Authority20112Mapping file id20112 NCBI fileEvidenceIEA
GeneRps6ka3Authority110651Mapping file id110651 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneTac1Authority21333Mapping file id21333 NCBI fileEvidenceIEA
GeneTac2Authority21334Mapping file id21334 NCBI fileEvidenceIEA
GeneTacr1Authority21336Mapping file id21336 NCBI fileEvidenceIEA
GeneTacr2Authority21337Mapping file id21337 NCBI fileEvidenceIEA
GeneTacr3Authority21338Mapping file id21338 NCBI fileEvidenceIEA
GeneTbxa2rAuthority21390Mapping file id21390 NCBI fileEvidenceIEA
GeneTrhAuthority22044Mapping file id22044 NCBI fileEvidenceIEA
GeneTrhrAuthority22045Mapping file id22045 NCBI fileEvidenceIEA
GeneTrioAuthority223435Mapping file id223435 NCBI fileEvidenceIEA
GeneTrpc3Authority22065Mapping file id22065 NCBI fileEvidenceIEA
GeneTrpc6Authority22068Mapping file id22068 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.