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.

Intra-Golgi and retrograde Golgi-to-ER traffic

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

Genes Reactome places in this mouse pathway, page 2 of 2
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
GeneM6prAuthority17113Mapping file id17113 NCBI fileEvidenceIEA
GeneNapaAuthority108124Mapping file id108124 NCBI fileEvidenceIEA
GeneNapbAuthority17957Mapping file id17957 NCBI fileEvidenceIEA
GeneNapgAuthority108123Mapping file id108123 NCBI fileEvidenceIEA
GeneNbasAuthority71169Mapping file id71169 NCBI fileEvidenceIEA
GeneNsfAuthority18195Mapping file id18195 NCBI fileEvidenceIEA
GenePafah1b1Authority18472Mapping file id18472 NCBI fileEvidenceIEA
GenePafah1b2Authority18475Mapping file id18475 NCBI fileEvidenceIEA
GenePafah1b3Authority18476Mapping file id18476 NCBI fileEvidenceIEA
GenePla2g4aAuthority18783Mapping file id18783 NCBI fileEvidenceIEA
GenePla2g6Authority53357Mapping file id53357 NCBI fileEvidenceIEA
GenePlin3Authority66905Mapping file id66905 NCBI fileEvidenceIEA
GeneRab18Authority19330Mapping file id19330 NCBI fileEvidenceIEA
GeneRab1aAuthority19324Mapping file id19324 NCBI fileEvidenceIEA
GeneRab1bAuthority76308Mapping file id76308 NCBI fileEvidenceIEA
GeneRab30Authority75985Mapping file id75985 NCBI fileEvidenceIEA
GeneRab33bAuthority19338Mapping file id19338 NCBI fileEvidenceIEA
GeneRab36Authority76877Mapping file id76877 NCBI fileEvidenceIEA
GeneRab39aAuthority270160Mapping file id270160 NCBI fileEvidenceIEA
GeneRab3gap1Authority226407Mapping file id226407 NCBI fileEvidenceIEA
GeneRab3gap2Authority98732Mapping file id98732 NCBI fileEvidenceIEA
GeneRab43Authority69834Mapping file id69834 NCBI fileEvidenceIEA
GeneRab6aAuthority19346Mapping file id19346 NCBI fileEvidenceIEA
GeneRab6bAuthority270192Mapping file id270192 NCBI fileEvidenceIEA
GeneRab9Authority56382Mapping file id56382 NCBI fileEvidenceIEA
GeneRab9bAuthority319642Mapping file id319642 NCBI fileEvidenceIEA
GeneRabepkAuthority227746Mapping file id227746 NCBI fileEvidenceIEA
GeneRacgap1Authority26934Mapping file id26934 NCBI fileEvidenceIEA
GeneRgp1Authority242406Mapping file id242406 NCBI fileEvidenceIEA
GeneRhobtb3Authority73296Mapping file id73296 NCBI fileEvidenceIEA
GeneRic1Authority226089Mapping file idENSMUSG00000038658 Ensembl fileEvidenceIEA
GeneRint1Authority72772Mapping file id72772 NCBI fileEvidenceIEA
GeneScocAuthority56367Mapping file id56367 NCBI fileEvidenceIEA
GeneSnap29Authority67474Mapping file id67474 NCBI fileEvidenceIEA
GeneStx16Authority228960Mapping file id228960 NCBI fileEvidenceIEA
GeneStx18Authority71116Mapping file id71116 NCBI fileEvidenceIEA
GeneStx5aAuthority56389Mapping file id56389 NCBI fileEvidenceIEA
GeneStx6Authority58244Mapping file id58244 NCBI fileEvidenceIEA
GeneSurf4Authority20932Mapping file id20932 NCBI fileEvidenceIEA
GeneSys1Authority66460Mapping file id66460 NCBI fileEvidenceIEA
GeneTgoln1Authority22134Mapping file id22134 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
GeneTmf1Authority232286Mapping file id232286 NCBI fileEvidenceIEA
GeneTrip11Authority109181Mapping file id109181 NCBI fileEvidenceIEA
GeneTuba1aAuthority22142Mapping file id22142 NCBI fileEvidenceIEA
GeneTuba1bAuthority22143Mapping file id22143 NCBI fileEvidenceIEA
GeneTuba1cAuthority22146Mapping file id22146 NCBI fileEvidenceIEA
GeneTuba3aAuthority22144Mapping file id22144 NCBI fileEvidenceIEA
GeneTuba3bAuthority22147Mapping file id22147 NCBI fileEvidenceIEA
GeneTuba4aAuthority22145Mapping file id22145 NCBI fileEvidenceIEA
GeneTuba8Authority53857Mapping file id53857 NCBI fileEvidenceIEA
GeneTubal3Authority238463Mapping file id238463 NCBI fileEvidenceIEA
GeneTubb1Authority545486Mapping file id545486 NCBI fileEvidenceIEA
GeneTubb2aAuthority22151Mapping file id22151 NCBI fileEvidenceIEA
GeneTubb2bAuthority73710Mapping file id73710 NCBI fileEvidenceIEA
GeneTubb3Authority22152Mapping file id22152 NCBI fileEvidenceIEA
GeneTubb4aAuthority22153Mapping file id22153 NCBI fileEvidenceIEA
GeneTubb4bAuthority227613Mapping file id227613 NCBI fileEvidenceIEA
GeneTubb6Authority67951Mapping file id67951 NCBI fileEvidenceIEA
GeneUse1Authority67023Mapping file id67023 NCBI fileEvidenceIEA
GeneUsp6nlAuthority98910Mapping file id98910 NCBI fileEvidenceIEA
GeneVamp3Authority22319Mapping file id22319 NCBI fileEvidenceIEA
GeneVamp4Authority53330Mapping file id53330 NCBI fileEvidenceIEA
GeneVps45Authority22365Mapping file id22365 NCBI fileEvidenceIEA
GeneVps51Authority68505Mapping file id68505 NCBI fileEvidenceIEA
GeneVps52Authority224705Mapping file id224705 NCBI fileEvidenceIEA
GeneVps53Authority68299Mapping file id68299 NCBI fileEvidenceIEA
GeneVps54Authority245944Mapping file id245944 NCBI fileEvidenceIEA
GeneVti1aAuthority53611Mapping file id53611 NCBI fileEvidenceIEA
GeneYkt6Authority56418Mapping file id56418 NCBI fileEvidenceIEA
GeneZw10Authority26951Mapping file id26951 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.