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.

Chemokine receptors bind chemokines

R-MMU-380108 in Reactome release 97: under Peptide ligand-binding receptors, with 55 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-380108 (human), R-RNO-380108 (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 55 genes in this mouse pathway; showing 1 to 55, 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
GeneAckr2Authority59289Mapping file id59289 NCBI fileEvidenceIEA
GeneAckr3Authority12778Mapping file id12778 NCBI fileEvidenceIEA
GeneAckr4Authority252837Mapping file id252837 NCBI fileEvidenceIEA
GeneCcl1Authority20290Mapping file id20290 NCBI fileEvidenceIEA
GeneCcl11Authority20292Mapping file id20292 NCBI fileEvidenceIEA
GeneCcl12Authority20293Mapping file id20293 NCBI fileEvidenceIEA
GeneCcl17Authority20295Mapping file id20295 NCBI fileEvidenceIEA
GeneCcl19Authority24047Mapping file id24047 NCBI fileEvidenceIEA
GeneCcl20Authority20297Mapping file id20297 NCBI fileEvidenceIEA
GeneCcl21aAuthority18829Mapping file id18829 NCBI fileEvidenceIEA
GeneCcl21bAuthority100042493Mapping file id100042493 NCBI fileEvidenceIEA
GeneCcl21dAuthority100862177Mapping file id100862177 NCBI fileEvidenceIEA
GeneCcl21eAuthority100504239Mapping file id100504239 NCBI fileEvidenceIEA
GeneCcl21fAuthority100504346Mapping file id100504346 NCBI fileEvidenceIEA
GeneCcl22Authority20299Mapping file id20299 NCBI fileEvidenceIEA
GeneCcl25Authority20300Mapping file id20300 NCBI fileEvidenceIEA
GeneCcl27aAuthority20301Mapping file id20301 NCBI fileEvidenceIEA
GeneCcl27alAuthority100039863Mapping file idENSMUSG00000073877 Ensembl fileEvidenceIEA
GeneCcl27bAuthority100040048Mapping file idENSMUSG00000096826 Ensembl fileEvidenceIEA
GeneCcl28Authority56838Mapping file id56838 NCBI fileEvidenceIEA
GeneCcl3Authority20302Mapping file id20302 NCBI fileEvidenceIEA
GeneCcl4Authority20303Mapping file id20303 NCBI fileEvidenceIEA
GeneCcl5Authority20304Mapping file id20304 NCBI fileEvidenceIEA
GeneCcl7Authority20306Mapping file id20306 NCBI fileEvidenceIEA
GeneCcr10Authority12777Mapping file id12777 NCBI fileEvidenceIEA
GeneCcr3Authority12771Mapping file id12771 NCBI fileEvidenceIEA
GeneCcr4Authority12773Mapping file id12773 NCBI fileEvidenceIEA
GeneCcr5Authority12774Mapping file id12774 NCBI fileEvidenceIEA
GeneCcr6Authority12458Mapping file id12458 NCBI fileEvidenceIEA
GeneCcr7Authority12775Mapping file id12775 NCBI fileEvidenceIEA
GeneCcr8Authority12776Mapping file id12776 NCBI fileEvidenceIEA
GeneCcr9Authority12769Mapping file id12769 NCBI fileEvidenceIEA
GeneCcrl2Authority54199Mapping file id54199 NCBI fileEvidenceIEA
GeneCx3cl1Authority20312Mapping file id20312 NCBI fileEvidenceIEA
GeneCx3cr1Authority13051Mapping file id13051 NCBI fileEvidenceIEA
GeneCxcl1Authority14825Mapping file id14825 NCBI fileEvidenceIEA
GeneCxcl10Authority15945Mapping file id15945 NCBI fileEvidenceIEA
GeneCxcl11Authority56066Mapping file id56066 NCBI fileEvidenceIEA
GeneCxcl12Authority20315Mapping file id20315 NCBI fileEvidenceIEA
GeneCxcl13Authority55985Mapping file id55985 NCBI fileEvidenceIEA
GeneCxcl16Authority66102Mapping file id66102 NCBI fileEvidenceIEA
GeneCxcl2Authority20310Mapping file id20310 NCBI fileEvidenceIEA
GeneCxcl3Authority330122Mapping file id330122 NCBI fileEvidenceIEA
GeneCxcl5Authority20311Mapping file id20311 NCBI fileEvidenceIEA
GeneCxcl9Authority17329Mapping file id17329 NCBI fileEvidenceIEA
GeneCxcr1Authority227288Mapping file id227288 NCBI fileEvidenceIEA
GeneCxcr2Authority12765Mapping file id12765 NCBI fileEvidenceIEA
GeneCxcr3Authority12766Mapping file id12766 NCBI fileEvidenceIEA
GeneCxcr4Authority12767Mapping file id12767 NCBI fileEvidenceIEA
GeneCxcr5Authority12145Mapping file id12145 NCBI fileEvidenceIEA
GeneCxcr6Authority80901Mapping file id80901 NCBI fileEvidenceIEA
GenePf4Authority56744Mapping file id56744 NCBI fileEvidenceIEA
GenePpbpAuthority57349Mapping file id57349 NCBI fileEvidenceIEA
GeneXcl1Authority16963Mapping file id16963 NCBI fileEvidenceIEA
GeneXcr1Authority23832Mapping file id23832 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.