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

Genes Reactome places in this mouse pathway, page 5 of 6
GeneSec22cAuthority215474Mapping file id215474 NCBI fileEvidenceIEA
GeneSec23aAuthority20334Mapping file id20334 NCBI fileEvidenceIEA
GeneSec23ipAuthority207352Mapping file idENSMUSG00000055319 Ensembl fileEvidenceIEA
GeneSec24aAuthority77371Mapping file id77371 NCBI fileEvidenceIEA
GeneSec24bAuthority99683Mapping file id99683 NCBI fileEvidenceIEA
GeneSec24cAuthority218811Mapping file id218811 NCBI fileEvidenceIEA
GeneSec24dAuthority69608Mapping file id69608 NCBI fileEvidenceIEA
GeneSec31aAuthority69162Mapping file id69162 NCBI fileEvidenceIEA
GeneSec31bAuthority240667Mapping file id240667 NCBI fileEvidenceIEA
GeneSerpina1cAuthority20702Mapping file id20702 NCBI fileEvidenceIEA
GeneSh3d19Authority27059Mapping file id27059 NCBI fileEvidenceIEA
GeneSh3gl1Authority20405Mapping file id20405 NCBI fileEvidenceIEA
GeneSh3gl2Authority20404Mapping file id20404 NCBI fileEvidenceIEA
GeneSh3gl3Authority20408Mapping file id20408 NCBI fileEvidenceIEA
GeneSh3kbp1Authority58194Mapping file id58194 NCBI fileEvidenceIEA
GeneSlc18a3Authority20508Mapping file idENSMUSG00000100241 Ensembl fileEvidenceIEA
GeneSlc2a8Authority56017Mapping file id56017 NCBI fileEvidenceIEA
GeneSnap23Authority20619Mapping file id20619 NCBI fileEvidenceIEA
GeneSnap29Authority67474Mapping file id67474 NCBI fileEvidenceIEA
GeneSnap91Authority20616Mapping file id20616 NCBI fileEvidenceIEA
GeneSnapinAuthority20615Mapping file id20615 NCBI fileEvidenceIEA
GeneSnf8Authority27681Mapping file id27681 NCBI fileEvidenceIEA
GeneSnx18Authority170625Mapping file idENSMUSG00000042364 Ensembl fileEvidenceIEA
GeneSnx2Authority67804Mapping file id67804 NCBI fileEvidenceIEA
GeneSnx5Authority69178Mapping file id69178 NCBI fileEvidenceIEA
GeneSnx9Authority66616Mapping file id66616 NCBI fileEvidenceIEA
GeneSort1Authority20661Mapping file id20661 NCBI fileEvidenceIEA
GeneSpta1Authority20739Mapping file id20739 NCBI fileEvidenceIEA
GeneSptan1Authority20740Mapping file id20740 NCBI fileEvidenceIEA
GeneSptbAuthority20741Mapping file idENSMUSG00000021061 Ensembl fileEvidenceIEA
GeneSptbn1Authority20742Mapping file id20742 NCBI fileEvidenceIEA
GeneSptbn2Authority20743Mapping file id20743 NCBI fileEvidenceIEA
GeneSptbn4Authority80297Mapping file id80297 NCBI fileEvidenceIEA
GeneSptbn5Authority640524Mapping file idENSMUSG00000074899 Ensembl fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneStamAuthority20844Mapping file id20844 NCBI fileEvidenceIEA
GeneStam2Authority56324Mapping file id56324 NCBI fileEvidenceIEA
GeneSton1Authority77057Mapping file id77057 NCBI fileEvidenceIEA
GeneSton2Authority108800Mapping file id108800 NCBI fileEvidenceIEA
GeneStx16Authority228960Mapping file id228960 NCBI fileEvidenceIEA
GeneStx17Authority67727Mapping file id67727 NCBI fileEvidenceIEA
GeneStx18Authority71116Mapping file id71116 NCBI fileEvidenceIEA
GeneStx4aAuthority20909Mapping file id20909 NCBI fileEvidenceIEA
GeneStx5aAuthority56389Mapping file id56389 NCBI fileEvidenceIEA
GeneStx6Authority58244Mapping file id58244 NCBI fileEvidenceIEA
GeneSurf4Authority20932Mapping file id20932 NCBI fileEvidenceIEA
GeneSynj1Authority104015Mapping file id104015 NCBI fileEvidenceIEA
GeneSynj2Authority20975Mapping file id20975 NCBI fileEvidenceIEA
GeneSys1Authority66460Mapping file id66460 NCBI fileEvidenceIEA
GeneSyt1Authority20979Mapping file id20979 NCBI fileEvidenceIEA
GeneSyt11Authority229521Mapping file id229521 NCBI fileEvidenceIEA
GeneSyt2Authority20980Mapping file id20980 NCBI fileEvidenceIEA
GeneSyt8Authority55925Mapping file id55925 NCBI fileEvidenceIEA
GeneSyt9Authority60510Mapping file id60510 NCBI fileEvidenceIEA
GeneSytl1Authority269589Mapping file idENSMUSG00000028860 Ensembl fileEvidenceIEA
GeneTacr1Authority21336Mapping file id21336 NCBI fileEvidenceIEA
GeneTbc1d10aAuthority103724Mapping file id103724 NCBI fileEvidenceIEA
GeneTbc1d10bAuthority68449Mapping file id68449 NCBI fileEvidenceIEA
GeneTbc1d10cAuthority108995Mapping file id108995 NCBI fileEvidenceIEA
GeneTbc1d13Authority70296Mapping file id70296 NCBI fileEvidenceIEA
GeneTbc1d14Authority100855Mapping file id100855 NCBI fileEvidenceIEA
GeneTbc1d15Authority66687Mapping file id66687 NCBI fileEvidenceIEA
GeneTbc1d16Authority207592Mapping file id207592 NCBI fileEvidenceIEA
GeneTbc1d17Authority233204Mapping file id233204 NCBI fileEvidenceIEA
GeneTbc1d2Authority381605Mapping file id381605 NCBI fileEvidenceIEA
GeneTbc1d20Authority67231Mapping file id67231 NCBI fileEvidenceIEA
GeneTbc1d24Authority224617Mapping file id224617 NCBI fileEvidenceIEA
GeneTbc1d25Authority209815Mapping file id209815 NCBI fileEvidenceIEA
GeneTbc1d7Authority67046Mapping file id67046 NCBI fileEvidenceIEA
GeneTbc1d8bAuthority245638Mapping file id245638 NCBI fileEvidenceIEA
GeneTfgAuthority21787Mapping file id21787 NCBI fileEvidenceIEA
GeneTfrcAuthority22042Mapping file id22042 NCBI fileEvidenceIEA
GeneTgfaAuthority21802Mapping file id21802 NCBI fileEvidenceIEA
GeneTgoln1Authority22134Mapping file id22134 NCBI fileEvidenceIEA
GeneTjp1Authority21872Mapping file id21872 NCBI fileEvidenceIEA
GeneTmed10Authority68581Mapping file id68581 NCBI fileEvidenceIEA
GeneTmed2Authority56334Mapping file id56334 NCBI fileEvidenceIEA
GeneTmed3Authority66111Mapping file id66111 NCBI fileEvidenceIEA
GeneTmed7Authority66676Mapping file id66676 NCBI fileEvidenceIEA
GeneTmed9Authority67511Mapping file id67511 NCBI fileEvidenceIEA
GeneTmem115Authority56395Mapping file id56395 NCBI fileEvidenceIEA
GeneTmf1Authority232286Mapping file id232286 NCBI fileEvidenceIEA
GeneTor1aAuthority30931Mapping file id30931 NCBI fileEvidenceIEA
GeneTor1bAuthority30934Mapping file id30934 NCBI fileEvidenceIEA
GeneTpd52Authority21985Mapping file id21985 NCBI fileEvidenceIEA
GeneTpd52l1Authority21987Mapping file id21987 NCBI fileEvidenceIEA
GeneTrappc1Authority245828Mapping file id245828 NCBI fileEvidenceIEA
GeneTrappc10Authority216131Mapping file id216131 NCBI fileEvidenceIEA
GeneTrappc11Authority320714Mapping file id320714 NCBI fileEvidenceIEA
GeneTrappc12Authority217449Mapping file id217449 NCBI fileEvidenceIEA
GeneTrappc13Authority66975Mapping file id66975 NCBI fileEvidenceIEA
GeneTrappc2Authority66226Mapping file id66226 NCBI fileEvidenceIEA
GeneTrappc2lAuthority59005Mapping file id59005 NCBI fileEvidenceIEA
GeneTrappc3Authority27096Mapping file id27096 NCBI fileEvidenceIEA
GeneTrappc4Authority60409Mapping file id60409 NCBI fileEvidenceIEA
GeneTrappc5Authority66682Mapping file id66682 NCBI fileEvidenceIEA
GeneTrappc6aAuthority67091Mapping file id67091 NCBI fileEvidenceIEA
GeneTrappc6bAuthority78232Mapping file id78232 NCBI fileEvidenceIEA
GeneTrappc8Authority75964Mapping file id75964 NCBI fileEvidenceIEA
GeneTrappc9Authority76510Mapping file id76510 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.