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.

Developmental Biology

R-MMU-1266738 in Reactome release 97: a top-level pathway, with 541 genes placed in it by the mapping files and 10 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-1266738 (human), R-RNO-1266738 (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 541 genes in this mouse pathway; showing 301 to 400, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 4 of 6
GeneKrtap4-13Authority69464Mapping file id69464 NCBI fileEvidenceIEA
GeneKrtap4-16Authority435285Mapping file id435285 NCBI fileEvidenceIEA
GeneKrtap4-2Authority68673Mapping file id68673 NCBI fileEvidenceIEA
GeneKrtap4-20Authority670482Mapping file id670482 NCBI fileEvidenceIEA
GeneKrtap4-21Authority670472Mapping file id670472 NCBI fileEvidenceIEA
GeneKrtap4-22Authority100040276Mapping file id100040276 NCBI fileEvidenceIEA
GeneKrtap4-23Authority670464Mapping file id670464 NCBI fileEvidenceIEA
GeneKrtap4-24Authority546511Mapping file idENSMUSG00000078130 Ensembl fileEvidenceIEA
GeneKrtap4-25Authority100040248Mapping file id100040248 NCBI fileEvidenceIEA
GeneKrtap4-26Authority670496Mapping file id670496 NCBI fileEvidenceIEA
GeneKrtap4-27Authority100502865Mapping file id100502865 NCBI fileEvidenceIEA
GeneKrtap4-6Authority68768Mapping file id68768 NCBI fileEvidenceIEA
GeneKrtap4-7Authority76444Mapping file id76444 NCBI fileEvidenceIEA
GeneKrtap4-8Authority665992Mapping file id665992 NCBI fileEvidenceIEA
GeneKrtap4-9Authority665998Mapping file id665998 NCBI fileEvidenceIEA
GeneKrtap5-1Authority50774Mapping file id50774 NCBI fileEvidenceIEA
GeneKrtap5-2Authority71623Mapping file id71623 NCBI fileEvidenceIEA
GeneKrtap5-20Authority100043627Mapping file id100043627 NCBI fileEvidenceIEA
GeneKrtap5-21Authority105243090Mapping file id105243090 NCBI fileEvidenceIEA
GeneKrtap5-22Authority101055862Mapping file idENSMUSG00000109655 Ensembl fileEvidenceIEA
GeneKrtap5-23Authority105243089Mapping file id105243089 NCBI fileEvidenceIEA
GeneKrtap5-24Authority105244938Mapping file idENSMUSG00000110324 Ensembl fileEvidenceIEA
GeneKrtap5-25Authority115486481Mapping file id115486481 NCBI fileEvidenceIEA
GeneKrtap5-26Authority108167466Mapping file id108167466 NCBI fileEvidenceIEA
GeneKrtap5-4Authority50775Mapping file id50775 NCBI fileEvidenceIEA
GeneKrtap5-5Authority114666Mapping file id114666 NCBI fileEvidenceIEA
GeneKrtap6-1Authority16700Mapping file id16700 NCBI fileEvidenceIEA
GeneKrtap6-3Authority100040201Mapping file id100040201 NCBI fileEvidenceIEA
GeneKrtap6-5Authority68484Mapping file id68484 NCBI fileEvidenceIEA
GeneKrtap6-6Authority68637Mapping file id68637 NCBI fileEvidenceIEA
GeneKrtap6-7Authority100040214Mapping file id100040214 NCBI fileEvidenceIEA
GeneKrtap8-1Authority16703Mapping file id16703 NCBI fileEvidenceIEA
GeneKrtap9-1Authority16705Mapping file id16705 NCBI fileEvidenceIEA
GeneKrtap9-20Authority100415785Mapping file id100415785 NCBI fileEvidenceIEA
GeneKrtap9-21Authority432600Mapping file id432600 NCBI fileEvidenceIEA
GeneKrtap9-22Authority670533Mapping file id670533 NCBI fileEvidenceIEA
GeneKrtap9-3Authority75586Mapping file id75586 NCBI fileEvidenceIEA
GeneKrtap9-5Authority435286Mapping file id435286 NCBI fileEvidenceIEA
GeneLars1Authority107045Mapping file id107045 NCBI fileEvidenceIEA
GeneLef1Authority16842Mapping file id16842 NCBI fileEvidenceIEA
GeneLgi1Authority56839Mapping file id56839 NCBI fileEvidenceIEA
GeneLgi2Authority246316Mapping file id246316 NCBI fileEvidenceIEA
GeneLgi3Authority213469Mapping file id213469 NCBI fileEvidenceIEA
GeneLgi4Authority243914Mapping file id243914 NCBI fileEvidenceIEA
GeneLimk1Authority16885Mapping file id16885 NCBI fileEvidenceIEA
GeneLipkAuthority240633Mapping file id240633 NCBI fileEvidenceIEA
GeneLipmAuthority78753Mapping file id78753 NCBI fileEvidenceIEA
GeneLipnAuthority70166Mapping file id70166 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 NCBI fileEvidenceIEA
GeneLypla2Authority26394Mapping file id26394 NCBI fileEvidenceIEA
GeneMap2k1Authority26395Mapping file id26395 NCBI fileEvidenceIEA
GeneMap2k2Authority26396Mapping file id26396 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk12Authority29857Mapping file id29857 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMark3Authority17169Mapping file id17169 NCBI fileEvidenceIEA
GeneMars1Authority216443Mapping file id216443 NCBI fileEvidenceIEA
GeneMef2cAuthority17260Mapping file id17260 NCBI fileEvidenceIEA
GeneMef2dAuthority17261Mapping file id17261 NCBI fileEvidenceIEA
GeneMetAuthority17295Mapping file idENSMUSG00000009376 Ensembl fileEvidenceIEA
GeneMitfAuthority17342Mapping file id17342 NCBI fileEvidenceIEA
GeneMlphAuthority171531Mapping file id171531 NCBI fileEvidenceIEA
GeneMmp2Authority17390Mapping file id17390 NCBI fileEvidenceIEA
GeneMmp9Authority17395Mapping file id17395 NCBI fileEvidenceIEA
GeneMsnAuthority17698Mapping file id17698 NCBI fileEvidenceIEA
GeneMyf5Authority17877Mapping file id17877 NCBI fileEvidenceIEA
GeneMyf6Authority17878Mapping file id17878 NCBI fileEvidenceIEA
GeneMyo5aAuthority17918Mapping file id17918 NCBI fileEvidenceIEA
GeneMyo9bAuthority17925Mapping file idENSMUSG00000004677 Ensembl fileEvidenceIEA
GeneMyod1Authority17927Mapping file id17927 NCBI fileEvidenceIEA
GeneMyogAuthority17928Mapping file id17928 NCBI fileEvidenceIEA
GeneMyripAuthority245049Mapping file id245049 NCBI fileEvidenceIEA
GeneNcam1Authority17967Mapping file id17967 NCBI fileEvidenceIEA
GeneNck1Authority17973Mapping file id17973 NCBI fileEvidenceIEA
GeneNck2Authority17974Mapping file id17974 NCBI fileEvidenceIEA
GeneNcor2Authority20602Mapping file id20602 NCBI fileEvidenceIEA
GeneNcstnAuthority59287Mapping file id59287 NCBI fileEvidenceIEA
GeneNfascAuthority269116Mapping file id269116 NCBI fileEvidenceIEA
GeneNgefAuthority53972Mapping file id53972 NCBI fileEvidenceIEA
GeneNrp1Authority18186Mapping file id18186 NCBI fileEvidenceIEA
GeneNrtnAuthority18188Mapping file id18188 NCBI fileEvidenceIEA
GeneNtn4Authority57764Mapping file id57764 NCBI fileEvidenceIEA
GeneNumbAuthority18222Mapping file id18222 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GenePak2Authority224105Mapping file id224105 NCBI fileEvidenceIEA
GenePak3Authority18481Mapping file id18481 NCBI fileEvidenceIEA
GenePdlim7Authority67399Mapping file id67399 NCBI fileEvidenceIEA
GenePerpAuthority64058Mapping file id64058 NCBI fileEvidenceIEA
GenePfn1Authority18643Mapping file id18643 NCBI fileEvidenceIEA
GenePfn2Authority18645Mapping file id18645 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3cbAuthority74769Mapping file id74769 NCBI fileEvidenceIEA
GenePik3cdAuthority18707Mapping file id18707 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePip5k1cAuthority18717Mapping file id18717 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.