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.

Signaling by TGF-beta Receptor Complex

R-MMU-170834 in Reactome release 97: under Signaling by TGFB family members, with 77 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-170834 (human), R-RNO-170834 (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 77 genes in this mouse pathway; showing 1 to 77, 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
GeneArhgef18Authority102098Mapping file id102098 NCBI fileEvidenceIEA
GeneAtp1b4Authority67821Mapping file id67821 NCBI fileEvidenceIEA
GeneBambiAuthority68010Mapping file id68010 NCBI fileEvidenceIEA
GeneCblAuthority12402Mapping file id12402 NCBI fileEvidenceIEA
GeneCcncAuthority51813Mapping file id51813 NCBI fileEvidenceIEA
GeneCcnt1Authority12455Mapping file id12455 NCBI fileEvidenceIEA
GeneCcnt2Authority72949Mapping file id72949 NCBI fileEvidenceIEA
GeneCdk8Authority264064Mapping file id264064 NCBI fileEvidenceIEA
GeneCdk9Authority107951Mapping file id107951 NCBI fileEvidenceIEA
GeneCgnAuthority70737Mapping file idENSMUSG00000068876 Ensembl fileEvidenceIEA
GeneE2f4Authority104394Mapping file id104394 NCBI fileEvidenceIEA
GeneE2f5Authority13559Mapping file id13559 NCBI fileEvidenceIEA
GeneF11rAuthority16456Mapping file id16456 NCBI fileEvidenceIEA
GeneFbn1Authority14118Mapping file id14118 NCBI fileEvidenceIEA
GeneFkbp1aAuthority14225Mapping file id14225 NCBI fileEvidenceIEA
GeneFurinAuthority18550Mapping file id18550 NCBI fileEvidenceIEA
GeneHdac1Authority433759Mapping file id433759 NCBI fileEvidenceIEA
GeneItga8Authority241226Mapping file id241226 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneItgb5Authority16419Mapping file id16419 NCBI fileEvidenceIEA
GeneItgb6Authority16420Mapping file id16420 NCBI fileEvidenceIEA
GeneItgb8Authority320910Mapping file id320910 NCBI fileEvidenceIEA
GeneLtbp1Authority268977Mapping file id268977 NCBI fileEvidenceIEA
GeneLtbp2Authority16997Mapping file id16997 NCBI fileEvidenceIEA
GeneLtbp3Authority16998Mapping file id16998 NCBI fileEvidenceIEA
GeneLtbp4Authority108075Mapping file id108075 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMen1Authority17283Mapping file id17283 NCBI fileEvidenceIEA
GeneMtmr4Authority170749Mapping file id170749 NCBI fileEvidenceIEA
GeneNcor2Authority20602Mapping file id20602 NCBI fileEvidenceIEA
GeneNedd4lAuthority83814Mapping file idENSMUSG00000024589 Ensembl fileEvidenceIEA
GeneNedd8Authority18002Mapping file id18002 NCBI fileEvidenceIEA
GenePard3Authority93742Mapping file id93742 NCBI fileEvidenceIEA
GenePard6aAuthority56513Mapping file id56513 NCBI fileEvidenceIEA
GeneParp1Authority11545Mapping file idENSMUSG00000026496 Ensembl fileEvidenceIEA
GenePmepa1Authority65112Mapping file idENSMUSG00000038400 Ensembl fileEvidenceIEA
GenePpm1aAuthority19042Mapping file id19042 NCBI fileEvidenceIEA
GenePrkczAuthority18762Mapping file id18762 NCBI fileEvidenceIEA
GeneRbl1Authority19650Mapping file id19650 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRnf111Authority93836Mapping file id93836 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneSkiAuthority20481Mapping file idENSMUSG00000029050 Ensembl fileEvidenceIEA
GeneSkilAuthority20482Mapping file id20482 NCBI fileEvidenceIEA
GeneSmad2Authority17126Mapping file id17126 NCBI fileEvidenceIEA
GeneSmad3Authority17127Mapping file id17127 NCBI fileEvidenceIEA
GeneSmad4Authority17128Mapping file id17128 NCBI fileEvidenceIEA
GeneSmad7Authority17131Mapping file id17131 NCBI fileEvidenceIEA
GeneSmurf1Authority75788Mapping file id75788 NCBI fileEvidenceIEA
GeneSmurf2Authority66313Mapping file id66313 NCBI fileEvidenceIEA
GeneSnw1Authority66354Mapping file id66354 NCBI fileEvidenceIEA
GeneSp1Authority20683Mapping file id20683 NCBI fileEvidenceIEA
GeneStrapAuthority20901Mapping file id20901 NCBI fileEvidenceIEA
GeneStub1Authority56424Mapping file id56424 NCBI fileEvidenceIEA
GeneTfdp1Authority21781Mapping file id21781 NCBI fileEvidenceIEA
GeneTgfb1Authority21803Mapping file id21803 NCBI fileEvidenceIEA
GeneTgfb2Authority21808Mapping file id21808 NCBI fileEvidenceIEA
GeneTgfb3Authority21809Mapping file idENSMUSG00000021253 Ensembl fileEvidenceIEA
GeneTgfbr1Authority21812Mapping file id21812 NCBI fileEvidenceIEA
GeneTgfbr2Authority21813Mapping file id21813 NCBI fileEvidenceIEA
GeneTgfbr3Authority21814Mapping file id21814 NCBI fileEvidenceIEA
GeneTgif1Authority21815Mapping file id21815 NCBI fileEvidenceIEA
GeneTgif2Authority228839Mapping file id228839 NCBI fileEvidenceIEA
GeneTrim33Authority94093Mapping file id94093 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUbe2d1Authority216080Mapping file id216080 NCBI fileEvidenceIEA
GeneUbe2d3Authority66105Mapping file id66105 NCBI fileEvidenceIEA
GeneUbe2mAuthority22192Mapping file id22192 NCBI fileEvidenceIEA
GeneUsp9xAuthority22284Mapping file id22284 NCBI fileEvidenceIEA
GeneWwtr1Authority97064Mapping file id97064 NCBI fileEvidenceIEA
GeneZfyve9Authority230597Mapping file id230597 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.