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.

ER to Golgi Anterograde Transport

R-MMU-199977 in Reactome release 97: under 2 parents, with 146 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-199977 (human), R-RNO-199977 (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 146 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 2
GeneActr10Authority56444Mapping file id56444 NCBI fileEvidenceIEA
GeneActr1aAuthority54130Mapping file id54130 NCBI fileEvidenceIEA
GeneAnk1Authority11733Mapping file id11733 NCBI fileEvidenceIEA
GeneAnkrd28Authority105522Mapping file id105522 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
GeneArfgap1Authority228998Mapping file id228998 NCBI fileEvidenceIEA
GeneArfgap2Authority77038Mapping file id77038 NCBI fileEvidenceIEA
GeneArfgap3Authority66251Mapping file id66251 NCBI fileEvidenceIEA
GeneBet1Authority12068Mapping file id12068 NCBI fileEvidenceIEA
GeneBet1lAuthority54399Mapping file id54399 NCBI fileEvidenceIEA
GeneCd55Authority13136Mapping file id13136 NCBI fileEvidenceIEA
GeneCd59bAuthority333883Mapping file id333883 NCBI fileEvidenceIEA
GeneCnih1Authority12793Mapping file id12793 NCBI fileEvidenceIEA
GeneCnih2Authority12794Mapping file id12794 NCBI fileEvidenceIEA
GeneCnih3Authority72978Mapping file id72978 NCBI fileEvidenceIEA
GeneCog1Authority16834Mapping file id16834 NCBI fileEvidenceIEA
GeneCog2Authority76332Mapping file id76332 NCBI fileEvidenceIEA
GeneCog3Authority338337Mapping file idENSMUSG00000034893 Ensembl fileEvidenceIEA
GeneCog4Authority102339Mapping file id102339 NCBI fileEvidenceIEA
GeneCog5Authority238123Mapping file id238123 NCBI fileEvidenceIEA
GeneCog6Authority67542Mapping file id67542 NCBI fileEvidenceIEA
GeneCog7Authority233824Mapping file id233824 NCBI fileEvidenceIEA
GeneCog8Authority97484Mapping file id97484 NCBI fileEvidenceIEA
GeneCol7a1Authority12836Mapping file id12836 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
GeneCsnk1dAuthority104318Mapping file id104318 NCBI fileEvidenceIEA
GeneCtscAuthority13032Mapping file id13032 NCBI fileEvidenceIEA
GeneCtszAuthority64138Mapping file id64138 NCBI fileEvidenceIEA
GeneDctn1Authority13191Mapping file id13191 NCBI fileEvidenceIEA
GeneDctn2Authority69654Mapping file id69654 NCBI fileEvidenceIEA
GeneDctn3Authority53598Mapping file id53598 NCBI fileEvidenceIEA
GeneDctn4Authority67665Mapping file id67665 NCBI fileEvidenceIEA
GeneDctn5Authority59288Mapping file id59288 NCBI fileEvidenceIEA
GeneDctn6Authority22428Mapping file id22428 NCBI fileEvidenceIEA
GeneDync1h1Authority13424Mapping file id13424 NCBI fileEvidenceIEA
GeneDync1i1Authority13426Mapping file id13426 NCBI fileEvidenceIEA
GeneDync1i2Authority13427Mapping file id13427 NCBI fileEvidenceIEA
GeneDync1li1Authority235661Mapping file id235661 NCBI fileEvidenceIEA
GeneDync1li2Authority234663Mapping file id234663 NCBI fileEvidenceIEA
GeneDynll1Authority56455Mapping file id56455 NCBI fileEvidenceIEA
GeneDynll2Authority68097Mapping file id68097 NCBI fileEvidenceIEA
GeneF5Authority14067Mapping file id14067 NCBI fileEvidenceIEA
GeneF8Authority14069Mapping file id14069 NCBI fileEvidenceIEA
GeneFolr1Authority14275Mapping file id14275 NCBI fileEvidenceIEA
GeneGbf1Authority107338Mapping file id107338 NCBI fileEvidenceIEA
GeneGolga2Authority99412Mapping file id99412 NCBI fileEvidenceIEA
GeneGolgb1Authority224139Mapping file id224139 NCBI fileEvidenceIEA
GeneGorasp1Authority74498Mapping file id74498 NCBI fileEvidenceIEA
GeneGosr1Authority53334Mapping file id53334 NCBI fileEvidenceIEA
GeneGosr2Authority56494Mapping file id56494 NCBI fileEvidenceIEA
GeneGria1Authority14799Mapping file id14799 NCBI fileEvidenceIEA
GeneIns1Authority16333Mapping file id16333 NCBI fileEvidenceIEA
GeneIns2Authority16334Mapping file id16334 NCBI fileEvidenceIEA
GeneKdelr1Authority68137Mapping file id68137 NCBI fileEvidenceIEA
GeneKdelr2Authority66913Mapping file id66913 NCBI fileEvidenceIEA
GeneKdelr3Authority105785Mapping file id105785 NCBI fileEvidenceIEA
GeneLman1Authority70361Mapping file id70361 NCBI fileEvidenceIEA
GeneLman1lAuthority235416Mapping file id235416 NCBI fileEvidenceIEA
GeneLman2Authority66890Mapping file id66890 NCBI fileEvidenceIEA
GeneLman2lAuthority214895Mapping file id214895 NCBI fileEvidenceIEA
GeneMcfd2Authority193813Mapping file id193813 NCBI fileEvidenceIEA
GeneMia2Authority338320Mapping file id338320 NCBI fileEvidenceIEA
GeneMia3Authority338366Mapping file id338366 NCBI fileEvidenceIEA
GeneNapaAuthority108124Mapping file id108124 NCBI fileEvidenceIEA
GeneNapbAuthority17957Mapping file id17957 NCBI fileEvidenceIEA
GeneNapgAuthority108123Mapping file id108123 NCBI fileEvidenceIEA
GeneNsfAuthority18195Mapping file id18195 NCBI fileEvidenceIEA
GenePpp6cAuthority67857Mapping file id67857 NCBI fileEvidenceIEA
GenePpp6r1Authority243819Mapping file id243819 NCBI fileEvidenceIEA
GenePpp6r3Authority52036Mapping file id52036 NCBI fileEvidenceIEA
GenePrebAuthority50907Mapping file id50907 NCBI fileEvidenceIEA
GeneRab1aAuthority19324Mapping file id19324 NCBI fileEvidenceIEA
GeneRab1bAuthority76308Mapping file id76308 NCBI fileEvidenceIEA
GeneSar1bAuthority66397Mapping file id66397 NCBI fileEvidenceIEA
GeneScfd1Authority76983Mapping file id76983 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSec16aAuthority227648Mapping file id227648 NCBI fileEvidenceIEA
GeneSec16bAuthority89867Mapping file id89867 NCBI fileEvidenceIEA
GeneSec22aAuthority317717Mapping file id317717 NCBI fileEvidenceIEA
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

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.