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

Genes Reactome places in this mouse pathway, page 4 of 7
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
GeneIl7rAuthority16197Mapping file id16197 NCBI fileEvidenceIEA
GeneIns1Authority16333Mapping file id16333 NCBI fileEvidenceIEA
GeneIns2Authority16334Mapping file id16334 NCBI fileEvidenceIEA
GeneItsn1Authority16443Mapping file id16443 NCBI fileEvidenceIEA
GeneItsn2Authority20403Mapping file idENSMUSG00000020640 Ensembl fileEvidenceIEA
GeneJchainAuthority16069Mapping file id16069 NCBI fileEvidenceIEA
GeneKdelr1Authority68137Mapping file id68137 NCBI fileEvidenceIEA
GeneKdelr2Authority66913Mapping file id66913 NCBI fileEvidenceIEA
GeneKdelr3Authority105785Mapping file id105785 NCBI fileEvidenceIEA
GeneKif11Authority16551Mapping file id16551 NCBI fileEvidenceIEA
GeneKif12Authority16552Mapping file id16552 NCBI fileEvidenceIEA
GeneKif13bAuthority16554Mapping file id16554 NCBI fileEvidenceIEA
GeneKif15Authority209737Mapping file id209737 NCBI fileEvidenceIEA
GeneKif16bAuthority16558Mapping file id16558 NCBI fileEvidenceIEA
GeneKif18aAuthority228421Mapping file id228421 NCBI fileEvidenceIEA
GeneKif18bAuthority70218Mapping file id70218 NCBI fileEvidenceIEA
GeneKif19aAuthority286942Mapping file id286942 NCBI fileEvidenceIEA
GeneKif1aAuthority16560Mapping file idENSMUSG00000014602 Ensembl fileEvidenceIEA
GeneKif1bAuthority16561Mapping file id16561 NCBI fileEvidenceIEA
GeneKif1cAuthority16562Mapping file id16562 NCBI fileEvidenceIEA
GeneKif20aAuthority19348Mapping file id19348 NCBI fileEvidenceIEA
GeneKif20bAuthority240641Mapping file id240641 NCBI fileEvidenceIEA
GeneKif21aAuthority16564Mapping file id16564 NCBI fileEvidenceIEA
GeneKif21bAuthority16565Mapping file id16565 NCBI fileEvidenceIEA
GeneKif22Authority110033Mapping file id110033 NCBI fileEvidenceIEA
GeneKif23Authority71819Mapping file id71819 NCBI fileEvidenceIEA
GeneKif26aAuthority668303Mapping file id668303 NCBI fileEvidenceIEA
GeneKif26bAuthority269152Mapping file id269152 NCBI fileEvidenceIEA
GeneKif27Authority75050Mapping file id75050 NCBI fileEvidenceIEA
GeneKif28Authority383592Mapping file idENSMUSG00000087236 Ensembl fileEvidenceIEA
GeneKif2aAuthority16563Mapping file id16563 NCBI fileEvidenceIEA
GeneKif2bAuthority73470Mapping file id73470 NCBI fileEvidenceIEA
GeneKif2cAuthority73804Mapping file id73804 NCBI fileEvidenceIEA
GeneKif3aAuthority16568Mapping file id16568 NCBI fileEvidenceIEA
GeneKif3bAuthority16569Mapping file id16569 NCBI fileEvidenceIEA
GeneKif3cAuthority16570Mapping file id16570 NCBI fileEvidenceIEA
GeneKif4Authority16571Mapping file id16571 NCBI fileEvidenceIEA
GeneKif5aAuthority16572Mapping file id16572 NCBI fileEvidenceIEA
GeneKif5bAuthority16573Mapping file id16573 NCBI fileEvidenceIEA
GeneKif6Authority319991Mapping file id319991 NCBI fileEvidenceIEA
GeneKif9Authority16578Mapping file id16578 NCBI fileEvidenceIEA
GeneKifap3Authority16579Mapping file id16579 NCBI fileEvidenceIEA
GeneKifc1Authority100502766Mapping file id100502766 NCBI fileEvidenceIEA
GeneKifc2Authority16581Mapping file idENSMUSG00000004187 Ensembl fileEvidenceIEA
GeneKifc5bAuthority16580Mapping file id16580 NCBI fileEvidenceIEA
GeneKlc1Authority16593Mapping file idENSMUSG00000021288 Ensembl fileEvidenceIEA
GeneKlc2Authority16594Mapping file idENSMUSG00000024862 Ensembl fileEvidenceIEA
GeneKlc3Authority232943Mapping file id232943 NCBI fileEvidenceIEA
GeneKlc4Authority74764Mapping file id74764 NCBI fileEvidenceIEA
GeneLdlrAuthority16835Mapping file id16835 NCBI fileEvidenceIEA
GeneLdlrap1Authority100017Mapping file id100017 NCBI fileEvidenceIEA
GeneLman1Authority70361Mapping file id70361 NCBI fileEvidenceIEA
GeneLman1lAuthority235416Mapping file id235416 NCBI fileEvidenceIEA
GeneLman2Authority66890Mapping file id66890 NCBI fileEvidenceIEA
GeneLman2lAuthority214895Mapping file id214895 NCBI fileEvidenceIEA
GeneLrp1Authority16971Mapping file id16971 NCBI fileEvidenceIEA
GeneLrp2Authority14725Mapping file id14725 NCBI fileEvidenceIEA
GeneM6prAuthority17113Mapping file id17113 NCBI fileEvidenceIEA
GeneMaddAuthority228355Mapping file id228355 NCBI fileEvidenceIEA
GeneMap1lc3bAuthority67443Mapping file id67443 NCBI fileEvidenceIEA
GeneMasp1Authority17174Mapping file id17174 NCBI fileEvidenceIEA
GeneMcfd2Authority193813Mapping file id193813 NCBI fileEvidenceIEA
GeneMia2Authority338320Mapping file id338320 NCBI fileEvidenceIEA
GeneMia3Authority338366Mapping file id338366 NCBI fileEvidenceIEA
GeneMon1aAuthority72825Mapping file id72825 NCBI fileEvidenceIEA
GeneMon1bAuthority270096Mapping file id270096 NCBI fileEvidenceIEA
GeneMsr1Authority20288Mapping file id20288 NCBI fileEvidenceIEA
GeneMvb12aAuthority73711Mapping file id73711 NCBI fileEvidenceIEA
GeneMvb12bAuthority72543Mapping file id72543 NCBI fileEvidenceIEA
GeneMyo6Authority17920Mapping file id17920 NCBI fileEvidenceIEA
GeneNapaAuthority108124Mapping file id108124 NCBI fileEvidenceIEA
GeneNapbAuthority17957Mapping file id17957 NCBI fileEvidenceIEA
GeneNapgAuthority108123Mapping file id108123 NCBI fileEvidenceIEA
GeneNbasAuthority71169Mapping file id71169 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.