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.

O-linked glycosylation

R-MMU-5173105 in Reactome release 97: under Post-translational protein modification, with 119 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-5173105 (human), R-RNO-5173105 (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 119 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
GeneA4gntAuthority333424Mapping file id333424 NCBI fileEvidenceIEA
GeneAdamts1Authority11504Mapping file id11504 NCBI fileEvidenceIEA
GeneAdamts10Authority224697Mapping file id224697 NCBI fileEvidenceIEA
GeneAdamts12Authority239337Mapping file id239337 NCBI fileEvidenceIEA
GeneAdamts13Authority279028Mapping file id279028 NCBI fileEvidenceIEA
GeneAdamts14Authority237360Mapping file idENSMUSG00000059901 Ensembl fileEvidenceIEA
GeneAdamts15Authority235130Mapping file id235130 NCBI fileEvidenceIEA
GeneAdamts16Authority271127Mapping file id271127 NCBI fileEvidenceIEA
GeneAdamts17Authority233332Mapping file id233332 NCBI fileEvidenceIEA
GeneAdamts18Authority208936Mapping file id208936 NCBI fileEvidenceIEA
GeneAdamts19Authority240322Mapping file id240322 NCBI fileEvidenceIEA
GeneAdamts2Authority216725Mapping file id216725 NCBI fileEvidenceIEA
GeneAdamts20Authority223838Mapping file id223838 NCBI fileEvidenceIEA
GeneAdamts3Authority330119Mapping file id330119 NCBI fileEvidenceIEA
GeneAdamts4Authority240913Mapping file id240913 NCBI fileEvidenceIEA
GeneAdamts5Authority23794Mapping file id23794 NCBI fileEvidenceIEA
GeneAdamts6Authority108154Mapping file id108154 NCBI fileEvidenceIEA
GeneAdamts7Authority108153Mapping file id108153 NCBI fileEvidenceIEA
GeneAdamts8Authority30806Mapping file idENSMUSG00000031994 Ensembl fileEvidenceIEA
GeneAdamts9Authority101401Mapping file idENSMUSG00000030022 Ensembl fileEvidenceIEA
GeneAdamtsl1Authority77739Mapping file id77739 NCBI fileEvidenceIEA
GeneAdamtsl2Authority77794Mapping file id77794 NCBI fileEvidenceIEA
GeneAdamtsl3Authority269959Mapping file id269959 NCBI fileEvidenceIEA
GeneAdamtsl4Authority229595Mapping file id229595 NCBI fileEvidenceIEA
GeneAdamtsl5Authority66548Mapping file id66548 NCBI fileEvidenceIEA
GeneB3galnt2Authority97884Mapping file id97884 NCBI fileEvidenceIEA
GeneB3glctAuthority381694Mapping file id381694 NCBI fileEvidenceIEA
GeneB3gnt2Authority53625Mapping file id53625 NCBI fileEvidenceIEA
GeneB3gnt3Authority72297Mapping file id72297 NCBI fileEvidenceIEA
GeneB3gnt4Authority231727Mapping file id231727 NCBI fileEvidenceIEA
GeneB3gnt5Authority108105Mapping file id108105 NCBI fileEvidenceIEA
GeneB3gnt6Authority272411Mapping file id272411 NCBI fileEvidenceIEA
GeneB3gnt7Authority227327Mapping file id227327 NCBI fileEvidenceIEA
GeneB3gnt8Authority232984Mapping file id232984 NCBI fileEvidenceIEA
GeneB3gnt9Authority97440Mapping file id97440 NCBI fileEvidenceIEA
GeneB4galt5Authority56336Mapping file id56336 NCBI fileEvidenceIEA
GeneB4galt6Authority56386Mapping file id56386 NCBI fileEvidenceIEA
GeneB4gat1Authority108902Mapping file id108902 NCBI fileEvidenceIEA
GeneC1galt1Authority94192Mapping file id94192 NCBI fileEvidenceIEA
GeneC1galt1c1Authority59048Mapping file id59048 NCBI fileEvidenceIEA
GeneCfpAuthority18636Mapping file id18636 NCBI fileEvidenceIEA
GeneChst10Authority98388Mapping file id98388 NCBI fileEvidenceIEA
GeneChst4Authority26887Mapping file id26887 NCBI fileEvidenceIEA
GeneCrppaAuthority75847Mapping file id75847 NCBI fileEvidenceIEA
GeneDag1Authority13138Mapping file id13138 NCBI fileEvidenceIEA
GeneEmid1Authority140703Mapping file id140703 NCBI fileEvidenceIEA
GeneFkrpAuthority243853Mapping file id243853 NCBI fileEvidenceIEA
GeneFktnAuthority246179Mapping file id246179 NCBI fileEvidenceIEA
GeneGalnt1Authority14423Mapping file id14423 NCBI fileEvidenceIEA
GeneGalnt10Authority171212Mapping file id171212 NCBI fileEvidenceIEA
GeneGalnt11Authority231050Mapping file id231050 NCBI fileEvidenceIEA
GeneGalnt12Authority230145Mapping file id230145 NCBI fileEvidenceIEA
GeneGalnt13Authority271786Mapping file id271786 NCBI fileEvidenceIEA
GeneGalnt14Authority71685Mapping file id71685 NCBI fileEvidenceIEA
GeneGalnt15Authority78754Mapping file id78754 NCBI fileEvidenceIEA
GeneGalnt16Authority108760Mapping file id108760 NCBI fileEvidenceIEA
GeneGalnt17Authority212996Mapping file id212996 NCBI fileEvidenceIEA
GeneGalnt18Authority233733Mapping file id233733 NCBI fileEvidenceIEA
GeneGalnt2Authority108148Mapping file id108148 NCBI fileEvidenceIEA
GeneGalnt3Authority14425Mapping file id14425 NCBI fileEvidenceIEA
GeneGalnt4Authority14426Mapping file id14426 NCBI fileEvidenceIEA
GeneGalnt5Authority241391Mapping file id241391 NCBI fileEvidenceIEA
GeneGalnt6Authority207839Mapping file id207839 NCBI fileEvidenceIEA
GeneGalnt7Authority108150Mapping file id108150 NCBI fileEvidenceIEA
GeneGalnt9Authority231605Mapping file id231605 NCBI fileEvidenceIEA
GeneGalntl5Authority67909Mapping file id67909 NCBI fileEvidenceIEA
GeneGalntl6Authority270049Mapping file id270049 NCBI fileEvidenceIEA
GeneGcnt1Authority14537Mapping file id14537 NCBI fileEvidenceIEA
GeneGcnt3Authority72077Mapping file id72077 NCBI fileEvidenceIEA
GeneGcnt4Authority218476Mapping file id218476 NCBI fileEvidenceIEA
GeneGcnt7Authority654821Mapping file id654821 NCBI fileEvidenceIEA
GeneLarge1Authority16795Mapping file id16795 NCBI fileEvidenceIEA
GeneLarge2Authority228366Mapping file id228366 NCBI fileEvidenceIEA
GeneMgat5bAuthority268510Mapping file id268510 NCBI fileEvidenceIEA
GeneMmrn1Authority70945Mapping file id70945 NCBI fileEvidenceIEA
GeneMmrn2Authority105450Mapping file id105450 NCBI fileEvidenceIEA
GeneMuc1Authority17829Mapping file id17829 NCBI fileEvidenceIEA
GeneMuc13Authority17063Mapping file id17063 NCBI fileEvidenceIEA
GeneMuc15Authority269328Mapping file id269328 NCBI fileEvidenceIEA
GeneMuc16Authority73732Mapping file idENSMUSG00000109564 Ensembl fileEvidenceIEA
GeneMuc17Authority666339Mapping file id666339 NCBI fileEvidenceIEA
GeneMuc19Authority239611Mapping file id239611 NCBI fileEvidenceIEA
GeneMuc20Authority224116Mapping file id224116 NCBI fileEvidenceIEA
GeneMuc4Authority140474Mapping file id140474 NCBI fileEvidenceIEA
GeneMuc5acAuthority17833Mapping file idENSMUSG00000037974 Ensembl fileEvidenceIEA
GeneMuc5bAuthority74180Mapping file id74180 NCBI fileEvidenceIEA
GeneMuc6Authority353328Mapping file idENSMUSG00000118661 Ensembl fileEvidenceIEA
GenePofut2Authority80294Mapping file id80294 NCBI fileEvidenceIEA
GenePofut3Authority171167Mapping file id171167 NCBI fileEvidenceIEA
GenePofut4Authority73068Mapping file id73068 NCBI fileEvidenceIEA
GenePomgnt1Authority68273Mapping file id68273 NCBI fileEvidenceIEA
GenePomgnt2Authority215494Mapping file id215494 NCBI fileEvidenceIEA
GenePomkAuthority74653Mapping file id74653 NCBI fileEvidenceIEA
GenePomt1Authority99011Mapping file id99011 NCBI fileEvidenceIEA
GenePomt2Authority217734Mapping file id217734 NCBI fileEvidenceIEA
GeneQtgalAuthority210004Mapping file id210004 NCBI fileEvidenceIEA
GeneRxylt1Authority216395Mapping file id216395 NCBI fileEvidenceIEA
GeneSbsponAuthority226866Mapping file id226866 NCBI fileEvidenceIEA
GeneSema5aAuthority20356Mapping file idENSMUSG00000022231 Ensembl fileEvidenceIEA
GeneSema5bAuthority20357Mapping file id20357 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.