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.

COPI-dependent Golgi-to-ER retrograde traffic

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

Genes Reactome places in this mouse pathway, page 1 of 1
GeneArcn1Authority213827Mapping file id213827 NCBI fileEvidenceIEA
GeneArf1Authority11840Mapping file id11840 NCBI fileEvidenceIEA
GeneArf3Authority11842Mapping file id11842 NCBI fileEvidenceIEA
GeneArf4Authority11843Mapping file id11843 NCBI fileEvidenceIEA
GeneArf5Authority11844Mapping file id11844 NCBI fileEvidenceIEA
GeneArfgap1Authority228998Mapping file id228998 NCBI fileEvidenceIEA
GeneArfgap2Authority77038Mapping file id77038 NCBI fileEvidenceIEA
GeneArfgap3Authority66251Mapping file id66251 NCBI fileEvidenceIEA
GeneBnip1Authority224630Mapping file id224630 NCBI fileEvidenceIEA
GeneCenpeAuthority229841Mapping file id229841 NCBI fileEvidenceIEA
GeneCopaAuthority12847Mapping file id12847 NCBI fileEvidenceIEA
GeneCopb1Authority70349Mapping file id70349 NCBI fileEvidenceIEA
GeneCopb2Authority50797Mapping file id50797 NCBI fileEvidenceIEA
GeneCopeAuthority59042Mapping file id59042 NCBI fileEvidenceIEA
GeneCopg1Authority54161Mapping file id54161 NCBI fileEvidenceIEA
GeneCopg2Authority54160Mapping file id54160 NCBI fileEvidenceIEA
GeneCopz1Authority56447Mapping file id56447 NCBI fileEvidenceIEA
GeneCopz2Authority56358Mapping file id56358 NCBI fileEvidenceIEA
GeneGbf1Authority107338Mapping file id107338 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
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
GeneRab1aAuthority19324Mapping file id19324 NCBI fileEvidenceIEA
GeneRab1bAuthority76308Mapping file id76308 NCBI fileEvidenceIEA
GeneRacgap1Authority26934Mapping file id26934 NCBI fileEvidenceIEA
GeneRint1Authority72772Mapping file id72772 NCBI fileEvidenceIEA
GeneStx18Authority71116Mapping file id71116 NCBI fileEvidenceIEA
GeneSurf4Authority20932Mapping file id20932 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
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
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

Children

None: no pathway of this release's list names this one as a parent.

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.