Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

TNFs bind their physiological receptors

R-HSA-5669034 in Reactome release 97: under TNFR2 non-canonical NF-kB pathway, with 29 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-MMU-5669034 (mouse), R-RNO-5669034 (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.

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. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [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 human pathway

The mapping files place 29 genes in this human pathway; showing 1 to 29, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneCD27AuthorityHGNC:11922Mapping file id939 NCBI fileEvidenceTAS
GeneCD70AuthorityHGNC:11937Mapping file id970 NCBI fileEvidenceTAS
GeneEDAAuthorityHGNC:3157Mapping file id1896 NCBI fileEvidenceTAS
GeneEDA2RAuthorityHGNC:17756Mapping file id60401 NCBI fileEvidenceTAS
GeneEDARAuthorityHGNC:2895Mapping file id10913 NCBI fileEvidenceTAS
GeneEDARADDAuthorityHGNC:14341Mapping file id128178 NCBI fileEvidenceTAS
GeneFASLGAuthorityHGNC:11936Mapping file id356 NCBI fileEvidenceTAS
GeneLTAAuthorityHGNC:6709Mapping file id4049 NCBI fileEvidenceTAS
GeneTNFRSF11BAuthorityHGNC:11909Mapping file id4982 NCBI fileEvidenceTAS
GeneTNFRSF13BAuthorityHGNC:18153Mapping file id23495 NCBI fileEvidenceTAS
GeneTNFRSF14AuthorityHGNC:11912Mapping file id8764 NCBI fileEvidenceTAS
GeneTNFRSF17AuthorityHGNC:11913Mapping file id608 NCBI fileEvidenceTAS
GeneTNFRSF18AuthorityHGNC:11914Mapping file id8784 NCBI fileEvidenceTAS
GeneTNFRSF1AAuthorityHGNC:11916Mapping file id7132 NCBI fileEvidenceTAS
GeneTNFRSF1BAuthorityHGNC:11917Mapping file id7133 NCBI fileEvidenceTAS
GeneTNFRSF25AuthorityHGNC:11910Mapping file id8718 NCBI fileEvidenceTAS
GeneTNFRSF4AuthorityHGNC:11918Mapping file id7293 NCBI fileEvidenceTAS
GeneTNFRSF6BAuthorityHGNC:11921Mapping file id8771 NCBI fileEvidenceTAS
GeneTNFRSF8AuthorityHGNC:11923Mapping file id943 NCBI fileEvidenceTAS
GeneTNFRSF9AuthorityHGNC:11924Mapping file id3604 NCBI fileEvidenceTAS
GeneTNFSF11AuthorityHGNC:11926Mapping file id8600 NCBI fileEvidenceTAS
GeneTNFSF13AuthorityHGNC:11928Mapping file id8741 NCBI fileEvidenceTAS
GeneTNFSF13BAuthorityHGNC:11929Mapping file id10673 NCBI fileEvidenceTAS
GeneTNFSF14AuthorityHGNC:11930Mapping file id8740 NCBI fileEvidenceTAS
GeneTNFSF15AuthorityHGNC:11931Mapping file id9966 NCBI fileEvidenceTAS
GeneTNFSF18AuthorityHGNC:11932Mapping file id8995 NCBI fileEvidenceTAS
GeneTNFSF4AuthorityHGNC:11934Mapping file id7292 NCBI fileEvidenceTAS
GeneTNFSF8AuthorityHGNC:11938Mapping file id944 NCBI fileEvidenceTAS
GeneTNFSF9AuthorityHGNC:11939Mapping file id8744 NCBI fileEvidenceTAS

Evidence codes on this page: TAS, 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: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human 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 human 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.