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.

Vesicle-mediated transport

R-MMU-5653656 in Reactome release 97: a top-level pathway, with 652 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-5653656 (human), R-RNO-5653656 (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 652 genes in this mouse pathway; showing 201 to 300, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 3 of 7
GeneEpn2Authority13855Mapping file id13855 NCBI fileEvidenceIEA
GeneEps15Authority13858Mapping file id13858 NCBI fileEvidenceIEA
GeneEps15l1Authority13859Mapping file id13859 NCBI fileEvidenceIEA
GeneEregAuthority13874Mapping file id13874 NCBI fileEvidenceIEA
GeneF5Authority14067Mapping file id14067 NCBI fileEvidenceIEA
GeneF8Authority14069Mapping file id14069 NCBI fileEvidenceIEA
GeneFcho1Authority74015Mapping file id74015 NCBI fileEvidenceIEA
GeneFcho2Authority218503Mapping file id218503 NCBI fileEvidenceIEA
GeneFnbp1Authority14269Mapping file id14269 NCBI fileEvidenceIEA
GeneFnbp1lAuthority214459Mapping file idENSMUSG00000039735 Ensembl fileEvidenceIEA
GeneFolr1Authority14275Mapping file id14275 NCBI fileEvidenceIEA
GeneFth1Authority14319Mapping file id14319 NCBI fileEvidenceIEA
GeneFzd4Authority14366Mapping file id14366 NCBI fileEvidenceIEA
GeneGabarapAuthority56486Mapping file id56486 NCBI fileEvidenceIEA
GeneGabarapl2Authority93739Mapping file id93739 NCBI fileEvidenceIEA
GeneGakAuthority231580Mapping file id231580 NCBI fileEvidenceIEA
GeneGalnt1Authority14423Mapping file id14423 NCBI fileEvidenceIEA
GeneGalnt2Authority108148Mapping file id108148 NCBI fileEvidenceIEA
GeneGapvd1Authority66691Mapping file id66691 NCBI fileEvidenceIEA
GeneGbf1Authority107338Mapping file id107338 NCBI fileEvidenceIEA
GeneGcc1Authority74375Mapping file id74375 NCBI fileEvidenceIEA
GeneGcc2Authority70297Mapping file id70297 NCBI fileEvidenceIEA
GeneGdi1Authority14567Mapping file id14567 NCBI fileEvidenceIEA
GeneGdi2Authority14569Mapping file id14569 NCBI fileEvidenceIEA
GeneGja1Authority14609Mapping file id14609 NCBI fileEvidenceIEA
GeneGja10Authority14610Mapping file idENSMUSG00000051056 Ensembl fileEvidenceIEA
GeneGja3Authority14611Mapping file id14611 NCBI fileEvidenceIEA
GeneGja4Authority14612Mapping file id14612 NCBI fileEvidenceIEA
GeneGja5Authority14613Mapping file id14613 NCBI fileEvidenceIEA
GeneGja8Authority14616Mapping file id14616 NCBI fileEvidenceIEA
GeneGjb1Authority14618Mapping file id14618 NCBI fileEvidenceIEA
GeneGjb2Authority14619Mapping file id14619 NCBI fileEvidenceIEA
GeneGjb3Authority14620Mapping file id14620 NCBI fileEvidenceIEA
GeneGjb4Authority14621Mapping file id14621 NCBI fileEvidenceIEA
GeneGjb5Authority14622Mapping file id14622 NCBI fileEvidenceIEA
GeneGjb6Authority14623Mapping file id14623 NCBI fileEvidenceIEA
GeneGjc1Authority14615Mapping file id14615 NCBI fileEvidenceIEA
GeneGjc2Authority118454Mapping file id118454 NCBI fileEvidenceIEA
GeneGjd2Authority14617Mapping file id14617 NCBI fileEvidenceIEA
GeneGjd3Authority353155Mapping file id353155 NCBI fileEvidenceIEA
GeneGjd4Authority225152Mapping file id225152 NCBI fileEvidenceIEA
GeneGnsAuthority75612Mapping file id75612 NCBI fileEvidenceIEA
GeneGolga1Authority76899Mapping file id76899 NCBI fileEvidenceIEA
GeneGolga2Authority99412Mapping file id99412 NCBI fileEvidenceIEA
GeneGolga4Authority54214Mapping file id54214 NCBI fileEvidenceIEA
GeneGolgb1Authority224139Mapping file id224139 NCBI fileEvidenceIEA
GeneGorasp1Authority74498Mapping file id74498 NCBI fileEvidenceIEA
GeneGosr1Authority53334Mapping file id53334 NCBI fileEvidenceIEA
GeneGosr2Authority56494Mapping file id56494 NCBI fileEvidenceIEA
GeneGps1Authority209318Mapping file idENSMUSG00000025156 Ensembl fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGria1Authority14799Mapping file id14799 NCBI fileEvidenceIEA
GeneGrk2Authority110355Mapping file id110355 NCBI fileEvidenceIEA
GeneGrk3Authority320129Mapping file id320129 NCBI fileEvidenceIEA
GeneHba-a1Authority15122Mapping file idENSMUSG00000069919 Ensembl fileEvidenceIEA
GeneHbb-bsAuthority100503605Mapping file id100503605 NCBI fileEvidenceIEA
GeneHbb-btAuthority101488143Mapping file id101488143 NCBI fileEvidenceIEA
GeneHbegfAuthority15200Mapping file id15200 NCBI fileEvidenceIEA
GeneHgsAuthority15239Mapping file id15239 NCBI fileEvidenceIEA
GeneHip1Authority215114Mapping file id215114 NCBI fileEvidenceIEA
GeneHip1rAuthority29816Mapping file id29816 NCBI fileEvidenceIEA
GeneHmgb1Authority15289Mapping file id15289 NCBI fileEvidenceIEA
GeneHpAuthority15439Mapping file id15439 NCBI fileEvidenceIEA
GeneHps1Authority192236Mapping file id192236 NCBI fileEvidenceIEA
GeneHps4Authority192232Mapping file id192232 NCBI fileEvidenceIEA
GeneHpxAuthority15458Mapping file id15458 NCBI fileEvidenceIEA
GeneHsp90b1Authority22027Mapping file id22027 NCBI fileEvidenceIEA
GeneHspa8Authority15481Mapping file id15481 NCBI fileEvidenceIEA
GeneIgf2rAuthority16004Mapping file id16004 NCBI fileEvidenceIEA
GeneIghaAuthority238447Mapping file idENSMUSG00000095079 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

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.