Skip to content
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.

Biosynthesis of the N-glycan precursor (dolichol lipid-linked oligosaccharide, LLO) and transfer to a nascent protein

R-MMU-446193 in Reactome release 97: under Asparagine N-linked glycosylation, with 75 genes placed in it by the mapping files and 1 child pathway 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-446193 (human), R-RNO-446193 (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 75 genes in this mouse pathway; showing 1 to 75, 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
GeneAlg1Authority208211Mapping file id208211 NCBI fileEvidenceIEA
GeneAlg12Authority223774Mapping file id223774 NCBI fileEvidenceIEA
GeneAlg14Authority66789Mapping file id66789 NCBI fileEvidenceIEA
GeneAlg2Authority56737Mapping file id56737 NCBI fileEvidenceIEA
GeneAlg3Authority208624Mapping file id208624 NCBI fileEvidenceIEA
GeneAlg5Authority66248Mapping file id66248 NCBI fileEvidenceIEA
GeneAlg6Authority320438Mapping file id320438 NCBI fileEvidenceIEA
GeneAlg8Authority381903Mapping file id381903 NCBI fileEvidenceIEA
GeneAlg9Authority102580Mapping file id102580 NCBI fileEvidenceIEA
GeneAmdhd2Authority245847Mapping file id245847 NCBI fileEvidenceIEA
GeneCmasAuthority12764Mapping file id12764 NCBI fileEvidenceIEA
GeneCtsaAuthority19025Mapping file id19025 NCBI fileEvidenceIEA
GeneDhddsAuthority67422Mapping file id67422 NCBI fileEvidenceIEA
GeneDhrsxAuthority236082Mapping file idENSMUSG00000144291 Ensembl fileEvidenceIEA
GeneDolkAuthority227697Mapping file id227697 NCBI fileEvidenceIEA
GeneDolpp1Authority57170Mapping file id57170 NCBI fileEvidenceIEA
GeneDpagt1Authority13478Mapping file id13478 NCBI fileEvidenceIEA
GeneDpm1Authority13480Mapping file id13480 NCBI fileEvidenceIEA
GeneDpm2Authority13481Mapping file id13481 NCBI fileEvidenceIEA
GeneDpm3Authority68563Mapping file id68563 NCBI fileEvidenceIEA
GeneFcskAuthority234730Mapping file id234730 NCBI fileEvidenceIEA
GeneFpgtAuthority75540Mapping file id75540 NCBI fileEvidenceIEA
GeneFuomAuthority69064Mapping file id69064 NCBI fileEvidenceIEA
GeneGfpt1Authority14583Mapping file id14583 NCBI fileEvidenceIEA
GeneGfpt2Authority14584Mapping file id14584 NCBI fileEvidenceIEA
GeneGfusAuthority22122Mapping file id22122 NCBI fileEvidenceIEA
GeneGlb1Authority12091Mapping file id12091 NCBI fileEvidenceIEA
GeneGlt28d2Authority320302Mapping file id320302 NCBI fileEvidenceIEA
GeneGmdsAuthority218138Mapping file id218138 NCBI fileEvidenceIEA
GeneGmppaAuthority69080Mapping file id69080 NCBI fileEvidenceIEA
GeneGmppbAuthority331026Mapping file id331026 NCBI fileEvidenceIEA
GeneGneAuthority50798Mapping file id50798 NCBI fileEvidenceIEA
GeneGnpnat1Authority54342Mapping file id54342 NCBI fileEvidenceIEA
GeneMpdu1Authority24070Mapping file idENSMUSG00000018761 Ensembl fileEvidenceIEA
GeneMpiAuthority110119Mapping file id110119 NCBI fileEvidenceIEA
GeneMvdAuthority192156Mapping file id192156 NCBI fileEvidenceIEA
GeneNagkAuthority56174Mapping file id56174 NCBI fileEvidenceIEA
GeneNanpAuthority67311Mapping file id67311 NCBI fileEvidenceIEA
GeneNansAuthority94181Mapping file id94181 NCBI fileEvidenceIEA
GeneNeu1Authority18010Mapping file id18010 NCBI fileEvidenceIEA
GeneNeu2Authority23956Mapping file id23956 NCBI fileEvidenceIEA
GeneNeu3Authority50877Mapping file id50877 NCBI fileEvidenceIEA
GeneNeu4Authority241159Mapping file id241159 NCBI fileEvidenceIEA
GeneNplAuthority74091Mapping file id74091 NCBI fileEvidenceIEA
GeneNudt14Authority66174Mapping file id66174 NCBI fileEvidenceIEA
GeneNus1Authority52014Mapping file id52014 NCBI fileEvidenceIEA
GenePgm3Authority109785Mapping file id109785 NCBI fileEvidenceIEA
GenePmm1Authority29858Mapping file id29858 NCBI fileEvidenceIEA
GenePmm2Authority54128Mapping file id54128 NCBI fileEvidenceIEA
GeneRenbpAuthority19703Mapping file id19703 NCBI fileEvidenceIEA
GeneSlc17a5Authority235504Mapping file id235504 NCBI fileEvidenceIEA
GeneSlc35a1Authority24060Mapping file id24060 NCBI fileEvidenceIEA
GeneSlc35c1Authority228368Mapping file id228368 NCBI fileEvidenceIEA
GeneSrd5a3Authority57357Mapping file id57357 NCBI fileEvidenceIEA
GeneSt3gal1Authority20442Mapping file id20442 NCBI fileEvidenceIEA
GeneSt3gal2Authority20444Mapping file id20444 NCBI fileEvidenceIEA
GeneSt3gal3Authority20441Mapping file id20441 NCBI fileEvidenceIEA
GeneSt3gal4Authority20443Mapping file id20443 NCBI fileEvidenceIEA
GeneSt3gal5Authority20454Mapping file id20454 NCBI fileEvidenceIEA
GeneSt3gal6Authority54613Mapping file id54613 NCBI fileEvidenceIEA
GeneSt6gal1Authority20440Mapping file id20440 NCBI fileEvidenceIEA
GeneSt6gal2Authority240119Mapping file id240119 NCBI fileEvidenceIEA
GeneSt6galnac1Authority20445Mapping file id20445 NCBI fileEvidenceIEA
GeneSt6galnac2Authority20446Mapping file id20446 NCBI fileEvidenceIEA
GeneSt6galnac3Authority20447Mapping file id20447 NCBI fileEvidenceIEA
GeneSt6galnac4Authority20448Mapping file id20448 NCBI fileEvidenceIEA
GeneSt6galnac5Authority26938Mapping file id26938 NCBI fileEvidenceIEA
GeneSt6galnac6Authority50935Mapping file id50935 NCBI fileEvidenceIEA
GeneSt8sia1Authority20449Mapping file id20449 NCBI fileEvidenceIEA
GeneSt8sia2Authority20450Mapping file id20450 NCBI fileEvidenceIEA
GeneSt8sia3Authority20451Mapping file id20451 NCBI fileEvidenceIEA
GeneSt8sia4Authority20452Mapping file id20452 NCBI fileEvidenceIEA
GeneSt8sia5Authority225742Mapping file id225742 NCBI fileEvidenceIEA
GeneSt8sia6Authority241230Mapping file id241230 NCBI fileEvidenceIEA
GeneUap1Authority107652Mapping file id107652 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.