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.

Asparagine N-linked glycosylation

R-MMU-446203 in Reactome release 97: under Post-translational protein modification, with 266 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-446203 (human), R-RNO-446203 (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 266 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 3
GeneActr10Authority56444Mapping file id56444 NCBI fileEvidenceIEA
GeneActr1aAuthority54130Mapping file id54130 NCBI fileEvidenceIEA
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
GeneAmfrAuthority23802Mapping file id23802 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
GeneAsgr1Authority11889Mapping file id11889 NCBI fileEvidenceIEA
GeneAsgr2Authority11890Mapping file id11890 NCBI fileEvidenceIEA
GeneB4galnt2Authority14422Mapping file id14422 NCBI fileEvidenceIEA
GeneB4galt1Authority14595Mapping file id14595 NCBI fileEvidenceIEA
GeneB4galt2Authority53418Mapping file id53418 NCBI fileEvidenceIEA
GeneB4galt3Authority57370Mapping file id57370 NCBI fileEvidenceIEA
GeneB4galt4Authority56375Mapping file id56375 NCBI fileEvidenceIEA
GeneB4galt5Authority56336Mapping file id56336 NCBI fileEvidenceIEA
GeneB4galt6Authority56386Mapping file id56386 NCBI fileEvidenceIEA
GeneBet1Authority12068Mapping file id12068 NCBI fileEvidenceIEA
GeneBet1lAuthority54399Mapping file id54399 NCBI fileEvidenceIEA
GeneCalrAuthority12317Mapping file id12317 NCBI fileEvidenceIEA
GeneCanxAuthority12330Mapping file id12330 NCBI fileEvidenceIEA
GeneCd55Authority13136Mapping file id13136 NCBI fileEvidenceIEA
GeneCd59bAuthority333883Mapping file id333883 NCBI fileEvidenceIEA
GeneCgaAuthority12640Mapping file id12640 NCBI fileEvidenceIEA
GeneChst10Authority98388Mapping file id98388 NCBI fileEvidenceIEA
GeneChst8Authority68947Mapping file id68947 NCBI fileEvidenceIEA
GeneCmasAuthority12764Mapping file id12764 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
GeneCtsaAuthority19025Mapping file id19025 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
GeneDerl1Authority67819Mapping file id67819 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
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
GeneEngaseAuthority217364Mapping file id217364 NCBI fileEvidenceIEA
GeneF5Authority14067Mapping file id14067 NCBI fileEvidenceIEA
GeneF8Authority14069Mapping file id14069 NCBI fileEvidenceIEA
GeneFcskAuthority234730Mapping file id234730 NCBI fileEvidenceIEA
GeneFolr1Authority14275Mapping file id14275 NCBI fileEvidenceIEA
GeneFpgtAuthority75540Mapping file id75540 NCBI fileEvidenceIEA
GeneFuca1Authority71665Mapping file id71665 NCBI fileEvidenceIEA
GeneFuomAuthority69064Mapping file id69064 NCBI fileEvidenceIEA
GeneFut8Authority53618Mapping file id53618 NCBI fileEvidenceIEA
GeneGbf1Authority107338Mapping file id107338 NCBI fileEvidenceIEA
GeneGfpt1Authority14583Mapping file id14583 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.