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.

Nuclear Receptor transcription pathway

R-MMU-383280 in Reactome release 97: under Generic Transcription Pathway, with 51 genes placed in it by the mapping files and 0 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-383280 (human), R-RNO-383280 (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 51 genes in this mouse pathway; showing 1 to 51, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneArAuthority11835Mapping file id11835 NCBI fileEvidenceIEA
GeneEsr1Authority13982Mapping file id13982 NCBI fileEvidenceIEA
GeneEsr2Authority13983Mapping file id13983 NCBI fileEvidenceIEA
GeneEsrraAuthority26379Mapping file id26379 NCBI fileEvidenceIEA
GeneEsrrbAuthority26380Mapping file id26380 NCBI fileEvidenceIEA
GeneEsrrgAuthority26381Mapping file id26381 NCBI fileEvidenceIEA
GeneHnf4aAuthority15378Mapping file id15378 NCBI fileEvidenceIEA
GeneHnf4gAuthority30942Mapping file id30942 NCBI fileEvidenceIEA
GeneMed1Authority19014Mapping file id19014 NCBI fileEvidenceIEA
GeneNcor2Authority20602Mapping file id20602 NCBI fileEvidenceIEA
GeneNek4Authority23955Mapping file id23955 NCBI fileEvidenceIEA
GeneNr0b1Authority11614Mapping file id11614 NCBI fileEvidenceIEA
GeneNr0b2Authority23957Mapping file id23957 NCBI fileEvidenceIEA
GeneNr1d1Authority217166Mapping file id217166 NCBI fileEvidenceIEA
GeneNr1d2Authority353187Mapping file id353187 NCBI fileEvidenceIEA
GeneNr1h2Authority22260Mapping file id22260 NCBI fileEvidenceIEA
GeneNr1h3Authority22259Mapping file id22259 NCBI fileEvidenceIEA
GeneNr1h4Authority20186Mapping file id20186 NCBI fileEvidenceIEA
GeneNr1i2Authority18171Mapping file id18171 NCBI fileEvidenceIEA
GeneNr1i3Authority12355Mapping file id12355 NCBI fileEvidenceIEA
GeneNr2c1Authority22025Mapping file id22025 NCBI fileEvidenceIEA
GeneNr2c2Authority22026Mapping file id22026 NCBI fileEvidenceIEA
GeneNr2e1Authority21907Mapping file id21907 NCBI fileEvidenceIEA
GeneNr2e3Authority23958Mapping file id23958 NCBI fileEvidenceIEA
GeneNr2f1Authority13865Mapping file id13865 NCBI fileEvidenceIEA
GeneNr2f6Authority13864Mapping file id13864 NCBI fileEvidenceIEA
GeneNr3c1Authority14815Mapping file id14815 NCBI fileEvidenceIEA
GeneNr3c2Authority110784Mapping file idENSMUSG00000031618 Ensembl fileEvidenceIEA
GeneNr4a1Authority15370Mapping file id15370 NCBI fileEvidenceIEA
GeneNr4a2Authority18227Mapping file id18227 NCBI fileEvidenceIEA
GeneNr4a3Authority18124Mapping file id18124 NCBI fileEvidenceIEA
GeneNr5a1Authority26423Mapping file id26423 NCBI fileEvidenceIEA
GeneNr5a2Authority26424Mapping file id26424 NCBI fileEvidenceIEA
GeneNr6a1Authority14536Mapping file id14536 NCBI fileEvidenceIEA
GeneNrbf2Authority641340Mapping file id641340 NCBI fileEvidenceIEA
GenePgrAuthority18667Mapping file id18667 NCBI fileEvidenceIEA
GenePparaAuthority19013Mapping file id19013 NCBI fileEvidenceIEA
GenePpardAuthority19015Mapping file id19015 NCBI fileEvidenceIEA
GenePpargAuthority19016Mapping file id19016 NCBI fileEvidenceIEA
GeneRaraAuthority19401Mapping file id19401 NCBI fileEvidenceIEA
GeneRarbAuthority218772Mapping file id218772 NCBI fileEvidenceIEA
GeneRargAuthority19411Mapping file id19411 NCBI fileEvidenceIEA
GeneRoraAuthority19883Mapping file id19883 NCBI fileEvidenceIEA
GeneRorbAuthority225998Mapping file id225998 NCBI fileEvidenceIEA
GeneRorcAuthority19885Mapping file id19885 NCBI fileEvidenceIEA
GeneRxraAuthority20181Mapping file id20181 NCBI fileEvidenceIEA
GeneRxrbAuthority20182Mapping file id20182 NCBI fileEvidenceIEA
GeneRxrgAuthority20183Mapping file id20183 NCBI fileEvidenceIEA
GeneThraAuthority21833Mapping file id21833 NCBI fileEvidenceIEA
GeneThrbAuthority21834Mapping file id21834 NCBI fileEvidenceIEA
GeneVdrAuthority22337Mapping file id22337 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

Children

None: no pathway of this release's list names this one as a parent.

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.