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.

Membrane Trafficking

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

Genes Reactome places in this mouse pathway, page 1 of 6
GeneAak1Authority269774Mapping file id269774 NCBI fileEvidenceIEA
GeneAcbd3Authority170760Mapping file id170760 NCBI fileEvidenceIEA
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneActr10Authority56444Mapping file id56444 NCBI fileEvidenceIEA
GeneActr1aAuthority54130Mapping file id54130 NCBI fileEvidenceIEA
GeneActr2Authority66713Mapping file id66713 NCBI fileEvidenceIEA
GeneActr3Authority74117Mapping file id74117 NCBI fileEvidenceIEA
GeneAdrb2Authority11555Mapping file id11555 NCBI fileEvidenceIEA
GeneAgfg1Authority15463Mapping file id15463 NCBI fileEvidenceIEA
GeneAgpat3Authority28169Mapping file id28169 NCBI fileEvidenceIEA
GeneAgtr1aAuthority11607Mapping file id11607 NCBI fileEvidenceIEA
GeneAkp3Authority11648Mapping file idENSMUSG00000036500 Ensembl fileEvidenceIEA
GeneAkt1Authority11651Mapping file id11651 NCBI fileEvidenceIEA
GeneAkt2Authority11652Mapping file id11652 NCBI fileEvidenceIEA
GeneAkt3Authority23797Mapping file id23797 NCBI fileEvidenceIEA
GeneAlpiAuthority76768Mapping file id76768 NCBI fileEvidenceIEA
GeneAlppl2Authority11650Mapping file id11650 NCBI fileEvidenceIEA
GeneAls2Authority74018Mapping file id74018 NCBI fileEvidenceIEA
GeneAls2clAuthority235633Mapping file id235633 NCBI fileEvidenceIEA
GeneAmphAuthority218038Mapping file id218038 NCBI fileEvidenceIEA
GeneAnk1Authority11733Mapping file id11733 NCBI fileEvidenceIEA
GeneAnkrd27Authority245886Mapping file id245886 NCBI fileEvidenceIEA
GeneAnkrd28Authority105522Mapping file id105522 NCBI fileEvidenceIEA
GeneAp1b1Authority11764Mapping file id11764 NCBI fileEvidenceIEA
GeneAp1g1Authority11765Mapping file id11765 NCBI fileEvidenceIEA
GeneAp1g2Authority11766Mapping file id11766 NCBI fileEvidenceIEA
GeneAp1m1Authority11767Mapping file id11767 NCBI fileEvidenceIEA
GeneAp1m2Authority11768Mapping file id11768 NCBI fileEvidenceIEA
GeneAp1s1Authority11769Mapping file id11769 NCBI fileEvidenceIEA
GeneAp1s2Authority108012Mapping file id108012 NCBI fileEvidenceIEA
GeneAp1s3Authority252903Mapping file id252903 NCBI fileEvidenceIEA
GeneAp2a1Authority11771Mapping file id11771 NCBI fileEvidenceIEA
GeneAp2a2Authority11772Mapping file id11772 NCBI fileEvidenceIEA
GeneAp2b1Authority71770Mapping file id71770 NCBI fileEvidenceIEA
GeneAp2m1Authority11773Mapping file id11773 NCBI fileEvidenceIEA
GeneAp2s1Authority232910Mapping file id232910 NCBI fileEvidenceIEA
GeneAp3b1Authority11774Mapping file id11774 NCBI fileEvidenceIEA
GeneAp3s1Authority11777Mapping file id11777 NCBI fileEvidenceIEA
GeneAp4b1Authority67489Mapping file id67489 NCBI fileEvidenceIEA
GeneAp4e1Authority108011Mapping file id108011 NCBI fileEvidenceIEA
GeneAp4m1Authority11781Mapping file id11781 NCBI fileEvidenceIEA
GeneAp4s1Authority11782Mapping file id11782 NCBI fileEvidenceIEA
GeneApobAuthority238055Mapping file id238055 NCBI fileEvidenceIEA
GeneAppAuthority11820Mapping file id11820 NCBI fileEvidenceIEA
GeneArcn1Authority213827Mapping file id213827 NCBI fileEvidenceIEA
GeneAregAuthority11839Mapping file id11839 NCBI fileEvidenceIEA
GeneArf1Authority11840Mapping file id11840 NCBI fileEvidenceIEA
GeneArf3Authority11842Mapping file id11842 NCBI fileEvidenceIEA
GeneArf4Authority11843Mapping file id11843 NCBI fileEvidenceIEA
GeneArf5Authority11844Mapping file id11844 NCBI fileEvidenceIEA
GeneArf6Authority11845Mapping file id11845 NCBI fileEvidenceIEA
GeneArfgap1Authority228998Mapping file id228998 NCBI fileEvidenceIEA
GeneArfgap2Authority77038Mapping file id77038 NCBI fileEvidenceIEA
GeneArfgap3Authority66251Mapping file id66251 NCBI fileEvidenceIEA
GeneArfip2Authority76932Mapping file id76932 NCBI fileEvidenceIEA
GeneArfrp1Authority76688Mapping file id76688 NCBI fileEvidenceIEA
GeneArl1Authority104303Mapping file id104303 NCBI fileEvidenceIEA
GeneArpc1aAuthority56443Mapping file id56443 NCBI fileEvidenceIEA
GeneArpc2Authority76709Mapping file id76709 NCBI fileEvidenceIEA
GeneArpc3Authority56378Mapping file id56378 NCBI fileEvidenceIEA
GeneArpc4Authority68089Mapping file id68089 NCBI fileEvidenceIEA
GeneArpc5Authority67771Mapping file id67771 NCBI fileEvidenceIEA
GeneArrb1Authority109689Mapping file id109689 NCBI fileEvidenceIEA
GeneArrb2Authority216869Mapping file id216869 NCBI fileEvidenceIEA
GeneAvpAuthority11998Mapping file id11998 NCBI fileEvidenceIEA
GeneAvpr2Authority12000Mapping file id12000 NCBI fileEvidenceIEA
GeneBet1Authority12068Mapping file id12068 NCBI fileEvidenceIEA
GeneBet1lAuthority54399Mapping file id54399 NCBI fileEvidenceIEA
GeneBicd1Authority12121Mapping file id12121 NCBI fileEvidenceIEA
GeneBicd2Authority76895Mapping file id76895 NCBI fileEvidenceIEA
GeneBin1Authority30948Mapping file id30948 NCBI fileEvidenceIEA
GeneBloc1s1Authority14533Mapping file id14533 NCBI fileEvidenceIEA
GeneBloc1s3Authority232946Mapping file id232946 NCBI fileEvidenceIEA
GeneBloc1s4Authority117197Mapping file id117197 NCBI fileEvidenceIEA
GeneBloc1s6Authority18457Mapping file id18457 NCBI fileEvidenceIEA
GeneBnip1Authority224630Mapping file id224630 NCBI fileEvidenceIEA
GeneBtcAuthority12223Mapping file id12223 NCBI fileEvidenceIEA
GeneCblAuthority12402Mapping file id12402 NCBI fileEvidenceIEA
GeneCcz1Authority231874Mapping file id231874 NCBI fileEvidenceIEA
GeneCd3dAuthority12500Mapping file id12500 NCBI fileEvidenceIEA
GeneCd3gAuthority12502Mapping file id12502 NCBI fileEvidenceIEA
GeneCd4Authority12504Mapping file id12504 NCBI fileEvidenceIEA
GeneCd55Authority13136Mapping file id13136 NCBI fileEvidenceIEA
GeneCd59bAuthority333883Mapping file id333883 NCBI fileEvidenceIEA
GeneCenpeAuthority229841Mapping file id229841 NCBI fileEvidenceIEA
GeneCftrAuthority12638Mapping file id12638 NCBI fileEvidenceIEA
GeneChmAuthority12662Mapping file idENSMUSG00000025531 Ensembl fileEvidenceIEA
GeneChmlAuthority12663Mapping file id12663 NCBI fileEvidenceIEA
GeneChmp2aAuthority68953Mapping file id68953 NCBI fileEvidenceIEA
GeneChmp2bAuthority68942Mapping file id68942 NCBI fileEvidenceIEA
GeneChmp3Authority66700Mapping file id66700 NCBI fileEvidenceIEA
GeneChmp4bAuthority75608Mapping file id75608 NCBI fileEvidenceIEA
GeneChmp4cAuthority66371Mapping file id66371 NCBI fileEvidenceIEA
GeneChmp5Authority76959Mapping file id76959 NCBI fileEvidenceIEA
GeneChmp6Authority208092Mapping file id208092 NCBI fileEvidenceIEA
GeneChmp7Authority105513Mapping file id105513 NCBI fileEvidenceIEA
GeneChrm2Authority243764Mapping file id243764 NCBI fileEvidenceIEA
GeneClint1Authority216705Mapping file idENSMUSG00000006169 Ensembl fileEvidenceIEA
GeneCltaAuthority12757Mapping file idENSMUSG00000028478 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.