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.

Transcriptional regulation by RUNX1

R-MMU-8878171 in Reactome release 97: under Generic Transcription Pathway, with 183 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-8878171 (human), R-RNO-8878171 (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 183 genes in this mouse pathway; showing 101 to 183, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 2
GeneHdac1Authority433759Mapping file id433759 NCBI fileEvidenceIEA
GeneHipk2Authority15258Mapping file id15258 NCBI fileEvidenceIEA
GeneItchAuthority16396Mapping file id16396 NCBI fileEvidenceIEA
GeneKat2bAuthority18519Mapping file id18519 NCBI fileEvidenceIEA
GeneKmt2aAuthority214162Mapping file idENSMUSG00000002028 Ensembl fileEvidenceIEA
GeneKmt2bAuthority75410Mapping file id75410 NCBI fileEvidenceIEA
GeneKmt2dAuthority381022Mapping file idENSMUSG00000048154 Ensembl fileEvidenceIEA
GeneLdb1Authority16825Mapping file id16825 NCBI fileEvidenceIEA
GeneLmo1Authority109594Mapping file id109594 NCBI fileEvidenceIEA
GeneLmo2Authority16909Mapping file id16909 NCBI fileEvidenceIEA
GeneMnat1Authority17420Mapping file id17420 NCBI fileEvidenceIEA
GenePax5Authority18507Mapping file id18507 NCBI fileEvidenceIEA
GenePbrm1Authority66923Mapping file idENSMUSG00000042323 Ensembl fileEvidenceIEA
GenePcgf5Authority76073Mapping file id76073 NCBI fileEvidenceIEA
GenePhc1Authority13619Mapping file id13619 NCBI fileEvidenceIEA
GenePhc2Authority54383Mapping file id54383 NCBI fileEvidenceIEA
GenePhc3Authority241915Mapping file id241915 NCBI fileEvidenceIEA
GenePmlAuthority18854Mapping file id18854 NCBI fileEvidenceIEA
GenePrmt1Authority15469Mapping file id15469 NCBI fileEvidenceIEA
GenePrmt6Authority99890Mapping file id99890 NCBI fileEvidenceIEA
GenePsma1Authority26440Mapping file id26440 NCBI fileEvidenceIEA
GenePsma2Authority19166Mapping file id19166 NCBI fileEvidenceIEA
GenePsma3Authority19167Mapping file id19167 NCBI fileEvidenceIEA
GenePsma4Authority26441Mapping file id26441 NCBI fileEvidenceIEA
GenePsma5Authority26442Mapping file id26442 NCBI fileEvidenceIEA
GenePsma6Authority26443Mapping file id26443 NCBI fileEvidenceIEA
GenePsma7Authority26444Mapping file id26444 NCBI fileEvidenceIEA
GenePsmb1Authority19170Mapping file id19170 NCBI fileEvidenceIEA
GenePsmb2Authority26445Mapping file id26445 NCBI fileEvidenceIEA
GenePsmb3Authority26446Mapping file id26446 NCBI fileEvidenceIEA
GenePsmb4Authority19172Mapping file id19172 NCBI fileEvidenceIEA
GenePsmb5Authority19173Mapping file id19173 NCBI fileEvidenceIEA
GenePsmb6Authority19175Mapping file id19175 NCBI fileEvidenceIEA
GenePsmb7Authority19177Mapping file id19177 NCBI fileEvidenceIEA
GenePsmc1Authority19179Mapping file id19179 NCBI fileEvidenceIEA
GenePsmc2Authority19181Mapping file id19181 NCBI fileEvidenceIEA
GenePsmc3Authority19182Mapping file id19182 NCBI fileEvidenceIEA
GenePsmc4Authority23996Mapping file id23996 NCBI fileEvidenceIEA
GenePsmc5Authority19184Mapping file id19184 NCBI fileEvidenceIEA
GenePsmc6Authority67089Mapping file id67089 NCBI fileEvidenceIEA
GenePsmd1Authority70247Mapping file id70247 NCBI fileEvidenceIEA
GenePsmd11Authority69077Mapping file id69077 NCBI fileEvidenceIEA
GenePsmd12Authority66997Mapping file id66997 NCBI fileEvidenceIEA
GenePsmd13Authority23997Mapping file id23997 NCBI fileEvidenceIEA
GenePsmd14Authority59029Mapping file id59029 NCBI fileEvidenceIEA
GenePsmd2Authority21762Mapping file id21762 NCBI fileEvidenceIEA
GenePsmd3Authority22123Mapping file id22123 NCBI fileEvidenceIEA
GenePsmd6Authority66413Mapping file id66413 NCBI fileEvidenceIEA
GenePsmd7Authority17463Mapping file id17463 NCBI fileEvidenceIEA
GenePsmd8Authority57296Mapping file id57296 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GeneRbbp5Authority213464Mapping file id213464 NCBI fileEvidenceIEA
GeneRing1Authority19763Mapping file id19763 NCBI fileEvidenceIEA
GeneRnf2Authority19821Mapping file id19821 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRybpAuthority56353Mapping file id56353 NCBI fileEvidenceIEA
GeneScmh1Authority29871Mapping file id29871 NCBI fileEvidenceIEA
GeneSerpinb13Authority241196Mapping file id241196 NCBI fileEvidenceIEA
GeneSetd1aAuthority233904Mapping file id233904 NCBI fileEvidenceIEA
GeneSetd1bAuthority208043Mapping file id208043 NCBI fileEvidenceIEA
GeneSin3aAuthority20466Mapping file id20466 NCBI fileEvidenceIEA
GeneSin3bAuthority20467Mapping file id20467 NCBI fileEvidenceIEA
GeneSmarca2Authority67155Mapping file id67155 NCBI fileEvidenceIEA
GeneSmarca4Authority20586Mapping file id20586 NCBI fileEvidenceIEA
GeneSmarcb1Authority20587Mapping file id20587 NCBI fileEvidenceIEA
GeneSmarcc1Authority20588Mapping file id20588 NCBI fileEvidenceIEA
GeneSmarcc2Authority68094Mapping file id68094 NCBI fileEvidenceIEA
GeneSmarcd1Authority83797Mapping file id83797 NCBI fileEvidenceIEA
GeneSmarcd2Authority83796Mapping file id83796 NCBI fileEvidenceIEA
GeneSmarcd3Authority66993Mapping file id66993 NCBI fileEvidenceIEA
GeneSmarce1Authority57376Mapping file id57376 NCBI fileEvidenceIEA
GeneTal1Authority21349Mapping file id21349 NCBI fileEvidenceIEA
GeneTcf12Authority21406Mapping file id21406 NCBI fileEvidenceIEA
GeneTcf3Authority21423Mapping file id21423 NCBI fileEvidenceIEA
GeneTrp73Authority22062Mapping file id22062 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneWdr5Authority140858Mapping file id140858 NCBI fileEvidenceIEA
GeneYaf2Authority67057Mapping file id67057 NCBI fileEvidenceIEA
GeneYap1Authority22601Mapping file id22601 NCBI fileEvidenceIEA
GeneZfpm1Authority22761Mapping file id22761 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.