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.

Creation of C4 and C2 activators

R-MMU-166786 in Reactome release 97: under Initial triggering of complement, with 71 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-166786 (human), R-RNO-166786 (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 71 genes in this mouse pathway; showing 1 to 71, 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
GeneC1qaAuthority12259Mapping file id12259 NCBI fileEvidenceIEA
GeneC1qbAuthority12260Mapping file id12260 NCBI fileEvidenceIEA
GeneC1qcAuthority12262Mapping file id12262 NCBI fileEvidenceIEA
GeneC1raAuthority50909Mapping file id50909 NCBI fileEvidenceIEA
GeneC1s2Authority317677Mapping file id317677 NCBI fileEvidenceIEA
GeneColec10Authority239447Mapping file id239447 NCBI fileEvidenceIEA
GeneColec11Authority71693Mapping file id71693 NCBI fileEvidenceIEA
GeneCrpAuthority12944Mapping file id12944 NCBI fileEvidenceIEA
GeneFcnaAuthority14133Mapping file id14133 NCBI fileEvidenceIEA
GeneFcnbAuthority14134Mapping file id14134 NCBI fileEvidenceIEA
GeneIghg2cAuthority404711Mapping file idENSMUSG00000076612 Ensembl fileEvidenceIEA
GeneIghg3Authority380795Mapping file idENSMUSG00000076615 Ensembl fileEvidenceIEA
GeneIghv1-12Authority629860Mapping file idENSMUSG00000095416 Ensembl fileEvidenceIEA
GeneIghv1-16Authority629866Mapping file idENSMUSG00000095554 Ensembl fileEvidenceIEA
GeneIghv1-24Authority780885Mapping file idENSMUSG00000094241 Ensembl fileEvidenceIEA
GeneIghv1-31Authority629893Mapping file idENSMUSG00000096649 Ensembl fileEvidenceIEA
GeneIghv1-42Authority629906Mapping file idENSMUSG00000094652 Ensembl fileEvidenceIEA
GeneIghv1-43Authority629908Mapping file idENSMUSG00000095859 Ensembl fileEvidenceIEA
GeneIghv1-47Authority629915Mapping file idENSMUSG00000076709 Ensembl fileEvidenceIEA
GeneIghv1-49Authority629925Mapping file idENSMUSG00000076710 Ensembl fileEvidenceIEA
GeneIghv1-5Authority668469Mapping file idENSMUSG00000096499 Ensembl fileEvidenceIEA
GeneIghv1-53Authority780931Mapping file idENSMUSG00000093894 Ensembl fileEvidenceIEA
GeneIghv1-55Authority780932Mapping file idENSMUSG00000095589 Ensembl fileEvidenceIEA
GeneIghv1-56Authority382695Mapping file idENSMUSG00000094862 Ensembl fileEvidenceIEA
GeneIghv1-58Authority780939Mapping file idENSMUSG00000095889 Ensembl fileEvidenceIEA
GeneIghv1-62-2Authority238448Mapping file idENSMUSG00000096078 Ensembl fileEvidenceIEA
GeneIghv1-62-3Authority668549Mapping file idENSMUSG00000096767 Ensembl fileEvidenceIEA
GeneIghv1-63Authority780956Mapping file idENSMUSG00000096672 Ensembl fileEvidenceIEA
GeneIghv1-64Authority380823Mapping file idENSMUSG00000094088 Ensembl fileEvidenceIEA
GeneIghv1-67Authority435328Mapping file idENSMUSG00000095863 Ensembl fileEvidenceIEA
GeneIghv1-69Authority619833Mapping file idENSMUSG00000094502 Ensembl fileEvidenceIEA
GeneIghv1-71Authority619886Mapping file idENSMUSG00000096577 Ensembl fileEvidenceIEA
GeneIghv1-74Authority100775173Mapping file idENSMUSG00000094124 Ensembl fileEvidenceIEA
GeneIghv1-76Authority100775174Mapping file idENSMUSG00000093896 Ensembl fileEvidenceIEA
GeneIghv1-77Authority619994Mapping file idENSMUSG00000096452 Ensembl fileEvidenceIEA
GeneIghv1-78Authority213570Mapping file idENSMUSG00000096326 Ensembl fileEvidenceIEA
GeneIghv1-82Authority100775175Mapping file idENSMUSG00000095127 Ensembl fileEvidenceIEA
GeneIghv1-84Authority434609Mapping file idENSMUSG00000094940 Ensembl fileEvidenceIEA
GeneIghv11-2Authority780818Mapping file idENSMUSG00000096108 Ensembl fileEvidenceIEA
GeneIghv14-2Authority668421Mapping file idENSMUSG00000095583 Ensembl fileEvidenceIEA
GeneIghv14-3Authority238418Mapping file idENSMUSG00000095642 Ensembl fileEvidenceIEA
GeneIghv14-4Authority629826Mapping file idENSMUSG00000076666 Ensembl fileEvidenceIEA
GeneIghv3-3Authority668438Mapping file idENSMUSG00000094029 Ensembl fileEvidenceIEA
GeneIghv3-5Authority633457Mapping file idENSMUSG00000076670 Ensembl fileEvidenceIEA
GeneIghv5-2Authority777685Mapping file idENSMUSG00000076633 Ensembl fileEvidenceIEA
GeneIghv5-9Authority544896Mapping file idENSMUSG00000095285 Ensembl fileEvidenceIEA
GeneIghv8-13Authority100775172Mapping file idENSMUSG00000076733 Ensembl fileEvidenceIEA
GeneIghv8-4Authority629919Mapping file idENSMUSG00000096355 Ensembl fileEvidenceIEA
GeneIghv8-6Authority629930Mapping file idENSMUSG00000094505 Ensembl fileEvidenceIEA
GeneIghv8-9Authority432709Mapping file idENSMUSG00000095117 Ensembl fileEvidenceIEA
GeneIgkv1-131Authority628056Mapping file idENSMUSG00000076505 Ensembl fileEvidenceIEA
GeneIgkv1-132Authority243423Mapping file idENSMUSG00000096580 Ensembl fileEvidenceIEA
GeneIgkv1-133Authority628027Mapping file idENSMUSG00000094491 Ensembl fileEvidenceIEA
GeneIgkv1-135Authority243420Mapping file idENSMUSG00000096336 Ensembl fileEvidenceIEA
GeneIgkv1-35Authority620105Mapping file idENSMUSG00000076573 Ensembl fileEvidenceIEA
GeneIgkv11-125Authority243428Mapping file idENSMUSG00000095737 Ensembl fileEvidenceIEA
GeneIgkv12-98Authority435900Mapping file idENSMUSG00000076526 Ensembl fileEvidenceIEA
GeneIgkv13-84Authority692152Mapping file idENSMUSG00000076538 Ensembl fileEvidenceIEA
GeneIgkv13-85Authority434036Mapping file idENSMUSG00000079543 Ensembl fileEvidenceIEA
GeneIgkv15-103Authority692169Mapping file idENSMUSG00000076523 Ensembl fileEvidenceIEA
GeneIgkv17-121Authority667435Mapping file idENSMUSG00000076514 Ensembl fileEvidenceIEA
GeneIgkv18-36Authority620088Mapping file idENSMUSG00000076572 Ensembl fileEvidenceIEA
GeneIgkv2-109Authority628268Mapping file idENSMUSG00000105606 Ensembl fileEvidenceIEA
GeneIgkv2-137Authority692187Mapping file idENSMUSG00000076501 Ensembl fileEvidenceIEA
GeneIgkv8-21Authority620400Mapping file idENSMUSG00000076586 Ensembl fileEvidenceIEA
GeneIglc1Authority110785Mapping file idENSMUSG00000105906 Ensembl fileEvidenceIEA
GeneIglc2Authority110786Mapping file idENSMUSG00000076937 Ensembl fileEvidenceIEA
GeneIgll1Authority16136Mapping file id16136 NCBI fileEvidenceIEA
GeneMasp1Authority17174Mapping file id17174 NCBI fileEvidenceIEA
GeneMasp2Authority17175Mapping file id17175 NCBI fileEvidenceIEA
GeneMbl2Authority17195Mapping file id17195 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.