Skip to content
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 (12/13) signalling events

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

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAbrAuthority109934Mapping file id109934 NCBI fileEvidenceIEA
GeneAdra1aAuthority11549Mapping file id11549 NCBI fileEvidenceIEA
GeneAdra1bAuthority11548Mapping file idENSMUSG00000050541 Ensembl fileEvidenceIEA
GeneAdra1dAuthority11550Mapping file idENSMUSG00000027335 Ensembl fileEvidenceIEA
GeneAkap13Authority75547Mapping file id75547 NCBI fileEvidenceIEA
GeneArhgef1Authority16801Mapping file id16801 NCBI fileEvidenceIEA
GeneArhgef10Authority234094Mapping file id234094 NCBI fileEvidenceIEA
GeneArhgef10lAuthority72754Mapping file id72754 NCBI fileEvidenceIEA
GeneArhgef11Authority213498Mapping file id213498 NCBI fileEvidenceIEA
GeneArhgef12Authority69632Mapping file id69632 NCBI fileEvidenceIEA
GeneArhgef15Authority442801Mapping file id442801 NCBI fileEvidenceIEA
GeneArhgef16Authority230972Mapping file id230972 NCBI fileEvidenceIEA
GeneArhgef17Authority207212Mapping file id207212 NCBI fileEvidenceIEA
GeneArhgef18Authority102098Mapping file id102098 NCBI fileEvidenceIEA
GeneArhgef19Authority213649Mapping file id213649 NCBI fileEvidenceIEA
GeneArhgef2Authority16800Mapping file id16800 NCBI fileEvidenceIEA
GeneArhgef25Authority52666Mapping file id52666 NCBI fileEvidenceIEA
GeneArhgef26Authority622434Mapping file id622434 NCBI fileEvidenceIEA
GeneArhgef3Authority71704Mapping file id71704 NCBI fileEvidenceIEA
GeneArhgef33Authority381112Mapping file id381112 NCBI fileEvidenceIEA
GeneArhgef37Authority328967Mapping file id328967 NCBI fileEvidenceIEA
GeneArhgef38Authority77669Mapping file id77669 NCBI fileEvidenceIEA
GeneArhgef39Authority230098Mapping file id230098 NCBI fileEvidenceIEA
GeneArhgef5Authority54324Mapping file id54324 NCBI fileEvidenceIEA
GeneArhgef6Authority73341Mapping file id73341 NCBI fileEvidenceIEA
GeneArhgef7Authority54126Mapping file id54126 NCBI fileEvidenceIEA
GeneArhgef9Authority236915Mapping file id236915 NCBI fileEvidenceIEA
GeneBtkAuthority12229Mapping file id12229 NCBI fileEvidenceIEA
GeneEct2Authority13605Mapping file id13605 NCBI fileEvidenceIEA
GeneFgd1Authority14163Mapping file id14163 NCBI fileEvidenceIEA
GeneFgd2Authority26382Mapping file id26382 NCBI fileEvidenceIEA
GeneFgd3Authority30938Mapping file idENSMUSG00000037946 Ensembl fileEvidenceIEA
GeneFgd4Authority224014Mapping file id224014 NCBI fileEvidenceIEA
GeneGna12Authority14673Mapping file id14673 NCBI fileEvidenceIEA
GeneGna13Authority14674Mapping file id14674 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
GeneItsn1Authority16443Mapping file id16443 NCBI fileEvidenceIEA
GeneKalrnAuthority545156Mapping file id545156 NCBI fileEvidenceIEA
GeneMcf2Authority109904Mapping file id109904 NCBI fileEvidenceIEA
GeneMcf2lAuthority17207Mapping file idENSMUSG00000031442 Ensembl fileEvidenceIEA
GeneNet1Authority56349Mapping file id56349 NCBI fileEvidenceIEA
GeneNgefAuthority53972Mapping file id53972 NCBI fileEvidenceIEA
GeneObscnAuthority380698Mapping file idENSMUSG00000061462 Ensembl fileEvidenceIEA
GenePlekhg2Authority101497Mapping file id101497 NCBI fileEvidenceIEA
GenePlekhg5Authority269608Mapping file id269608 NCBI fileEvidenceIEA
GenePlxnb1Authority235611Mapping file id235611 NCBI fileEvidenceIEA
GenePrex1Authority277360Mapping file id277360 NCBI fileEvidenceIEA
GeneRasgrf2Authority19418Mapping file id19418 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRhobAuthority11852Mapping file id11852 NCBI fileEvidenceIEA
GeneRhocAuthority11853Mapping file id11853 NCBI fileEvidenceIEA
GeneRock1Authority19877Mapping file id19877 NCBI fileEvidenceIEA
GeneRock2Authority19878Mapping file id19878 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneSos2Authority20663Mapping file id20663 NCBI fileEvidenceIEA
GeneTbxa2rAuthority21390Mapping file id21390 NCBI fileEvidenceIEA
GeneTiam2Authority24001Mapping file id24001 NCBI fileEvidenceIEA
GeneTrioAuthority223435Mapping file id223435 NCBI fileEvidenceIEA
GeneVav1Authority22324Mapping file id22324 NCBI fileEvidenceIEA
GeneVav2Authority22325Mapping file id22325 NCBI fileEvidenceIEA
GeneVav3Authority57257Mapping file id57257 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

Children

None: no pathway of this release's list names this one as a parent.

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.