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 201 to 300, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 3 of 6
GeneKrt16Authority16666Mapping file id16666 NCBI fileEvidenceIEA
GeneKrt17Authority16667Mapping file id16667 NCBI fileEvidenceIEA
GeneKrt18Authority16668Mapping file id16668 NCBI fileEvidenceIEA
GeneKrt19Authority16669Mapping file id16669 NCBI fileEvidenceIEA
GeneKrt2Authority16681Mapping file id16681 NCBI fileEvidenceIEA
GeneKrt20Authority66809Mapping file id66809 NCBI fileEvidenceIEA
GeneKrt23Authority94179Mapping file id94179 NCBI fileEvidenceIEA
GeneKrt24Authority75706Mapping file id75706 NCBI fileEvidenceIEA
GeneKrt25Authority70810Mapping file id70810 NCBI fileEvidenceIEA
GeneKrt26Authority320864Mapping file id320864 NCBI fileEvidenceIEA
GeneKrt27Authority16675Mapping file id16675 NCBI fileEvidenceIEA
GeneKrt28Authority70843Mapping file id70843 NCBI fileEvidenceIEA
GeneKrt31Authority16660Mapping file id16660 NCBI fileEvidenceIEA
GeneKrt32Authority16670Mapping file id16670 NCBI fileEvidenceIEA
GeneKrt33aAuthority71888Mapping file id71888 NCBI fileEvidenceIEA
GeneKrt33bAuthority16671Mapping file id16671 NCBI fileEvidenceIEA
GeneKrt34Authority16672Mapping file id16672 NCBI fileEvidenceIEA
GeneKrt35Authority53617Mapping file id53617 NCBI fileEvidenceIEA
GeneKrt36Authority16673Mapping file id16673 NCBI fileEvidenceIEA
GeneKrt39Authority237934Mapping file id237934 NCBI fileEvidenceIEA
GeneKrt4Authority16682Mapping file id16682 NCBI fileEvidenceIEA
GeneKrt40Authority406221Mapping file id406221 NCBI fileEvidenceIEA
GeneKrt5Authority110308Mapping file id110308 NCBI fileEvidenceIEA
GeneKrt6aAuthority16687Mapping file id16687 NCBI fileEvidenceIEA
GeneKrt6bAuthority16688Mapping file idENSMUSG00000023041 Ensembl fileEvidenceIEA
GeneKrt7Authority110310Mapping file id110310 NCBI fileEvidenceIEA
GeneKrt71Authority56735Mapping file id56735 NCBI fileEvidenceIEA
GeneKrt72Authority105866Mapping file id105866 NCBI fileEvidenceIEA
GeneKrt73Authority223915Mapping file id223915 NCBI fileEvidenceIEA
GeneKrt75Authority109052Mapping file id109052 NCBI fileEvidenceIEA
GeneKrt76Authority77055Mapping file id77055 NCBI fileEvidenceIEA
GeneKrt77Authority406220Mapping file id406220 NCBI fileEvidenceIEA
GeneKrt78Authority332131Mapping file id332131 NCBI fileEvidenceIEA
GeneKrt79Authority223917Mapping file id223917 NCBI fileEvidenceIEA
GeneKrt8Authority16691Mapping file id16691 NCBI fileEvidenceIEA
GeneKrt80Authority74127Mapping file id74127 NCBI fileEvidenceIEA
GeneKrt81Authority64818Mapping file id64818 NCBI fileEvidenceIEA
GeneKrt82Authority114566Mapping file id114566 NCBI fileEvidenceIEA
GeneKrt83Authority100126226Mapping file id100126226 NCBI fileEvidenceIEA
GeneKrt84Authority16680Mapping file id16680 NCBI fileEvidenceIEA
GeneKrt85Authority53622Mapping file id53622 NCBI fileEvidenceIEA
GeneKrt86Authority16679Mapping file id16679 NCBI fileEvidenceIEA
GeneKrt87Authority406219Mapping file id406219 NCBI fileEvidenceIEA
GeneKrt9Authority107656Mapping file id107656 NCBI fileEvidenceIEA
GeneKrtap1-3Authority435273Mapping file id435273 NCBI fileEvidenceIEA
GeneKrtap1-4Authority629873Mapping file id629873 NCBI fileEvidenceIEA
GeneKrtap1-5Authority69664Mapping file id69664 NCBI fileEvidenceIEA
GeneKrtap10-10Authority544710Mapping file id544710 NCBI fileEvidenceIEA
GeneKrtap10-21Authority100041250Mapping file id100041250 NCBI fileEvidenceIEA
GeneKrtap10-22Authority100041261Mapping file id100041261 NCBI fileEvidenceIEA
GeneKrtap10-23Authority100041281Mapping file id100041281 NCBI fileEvidenceIEA
GeneKrtap10-24Authority100041351Mapping file id100041351 NCBI fileEvidenceIEA
GeneKrtap10-25Authority634504Mapping file id634504 NCBI fileEvidenceIEA
GeneKrtap10-26Authority102640500Mapping file id102640500 NCBI fileEvidenceIEA
GeneKrtap10-27Authority670880Mapping file id670880 NCBI fileEvidenceIEA
GeneKrtap10-28Authority670895Mapping file id670895 NCBI fileEvidenceIEA
GeneKrtap10-29Authority675294Mapping file id675294 NCBI fileEvidenceIEA
GeneKrtap10-30Authority77763Mapping file id77763 NCBI fileEvidenceIEA
GeneKrtap10-31Authority622629Mapping file id622629 NCBI fileEvidenceIEA
GeneKrtap10-33Authority100502831Mapping file id100502831 NCBI fileEvidenceIEA
GeneKrtap10-34Authority100503388Mapping file id100503388 NCBI fileEvidenceIEA
GeneKrtap10-4Authority100191037Mapping file id100191037 NCBI fileEvidenceIEA
GeneKrtap11-1Authority16693Mapping file id16693 NCBI fileEvidenceIEA
GeneKrtap12-1Authority16694Mapping file id16694 NCBI fileEvidenceIEA
GeneKrtap12-20Authority100502953Mapping file id100502953 NCBI fileEvidenceIEA
GeneKrtap12-21Authority100502921Mapping file id100502921 NCBI fileEvidenceIEA
GeneKrtap12-22Authority100009614Mapping file id100009614 NCBI fileEvidenceIEA
GeneKrtap12-23Authority16697Mapping file id16697 NCBI fileEvidenceIEA
GeneKrtap13Authority16699Mapping file id16699 NCBI fileEvidenceIEA
GeneKrtap13-1Authority268905Mapping file id268905 NCBI fileEvidenceIEA
GeneKrtap13-20Authority117172Mapping file id117172 NCBI fileEvidenceIEA
GeneKrtap13-21Authority69696Mapping file id69696 NCBI fileEvidenceIEA
GeneKrtap13-22Authority69661Mapping file id69661 NCBI fileEvidenceIEA
GeneKrtap13-23Authority546672Mapping file idENSMUSG00000009047 Ensembl fileEvidenceIEA
GeneKrtap16-1Authority100504183Mapping file id100504183 NCBI fileEvidenceIEA
GeneKrtap16-3Authority71369Mapping file id71369 NCBI fileEvidenceIEA
GeneKrtap19-1Authority170657Mapping file idENSMUSG00000060691 Ensembl fileEvidenceIEA
GeneKrtap19-2Authority170651Mapping file id170651 NCBI fileEvidenceIEA
GeneKrtap19-3Authority77918Mapping file id77918 NCBI fileEvidenceIEA
GeneKrtap19-4Authority170654Mapping file id170654 NCBI fileEvidenceIEA
GeneKrtap19-5Authority16704Mapping file id16704 NCBI fileEvidenceIEA
GeneKrtap2-20Authority100502803Mapping file id100502803 NCBI fileEvidenceIEA
GeneKrtap2-21Authority100041488Mapping file id100041488 NCBI fileEvidenceIEA
GeneKrtap2-22Authority100041412Mapping file id100041412 NCBI fileEvidenceIEA
GeneKrtap2-4Authority71453Mapping file id71453 NCBI fileEvidenceIEA
GeneKrtap20-1Authority100040249Mapping file id100040249 NCBI fileEvidenceIEA
GeneKrtap20-2Authority622935Mapping file id622935 NCBI fileEvidenceIEA
GeneKrtap20-20Authority102637192Mapping file id102637192 NCBI fileEvidenceIEA
GeneKrtap20-21Authority640627Mapping file id640627 NCBI fileEvidenceIEA
GeneKrtap20-22Authority102637417Mapping file id102637417 NCBI fileEvidenceIEA
GeneKrtap20-23Authority102637070Mapping file idENSMUSG00000068071 Ensembl fileEvidenceIEA
GeneKrtap24-1Authority239932Mapping file id239932 NCBI fileEvidenceIEA
GeneKrtap29-1Authority100462664Mapping file id100462664 NCBI fileEvidenceIEA
GeneKrtap3-1Authority69473Mapping file id69473 NCBI fileEvidenceIEA
GeneKrtap3-2Authority66708Mapping file id66708 NCBI fileEvidenceIEA
GeneKrtap3-3Authority66380Mapping file id66380 NCBI fileEvidenceIEA
GeneKrtap31-1Authority70831Mapping file id70831 NCBI fileEvidenceIEA
GeneKrtap31-2Authority432602Mapping file id432602 NCBI fileEvidenceIEA
GeneKrtap31-3Authority670550Mapping file id670550 NCBI fileEvidenceIEA
GeneKrtap4-1Authority665891Mapping file id665891 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.