Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

SLC-mediated transmembrane transport

R-HSA-425407 in Reactome release 97: under Transport of small molecules, with 245 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-MMU-425407 (mouse), R-RNO-425407 (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 245 genes in this human pathway; showing 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 2 of 3
GeneSLC28A3AuthorityHGNC:16484Mapping file id64078 NCBI fileEvidenceTAS
GeneSLC29A1AuthorityHGNC:11003Mapping file id2030 NCBI fileEvidenceTAS
GeneSLC29A2AuthorityHGNC:11004Mapping file id3177 NCBI fileEvidenceTAS
GeneSLC29A3AuthorityHGNC:23096Mapping file id55315 NCBI fileEvidenceTAS
GeneSLC29A4AuthorityHGNC:23097Mapping file id222962 NCBI fileEvidenceTAS
GeneSLC2A1AuthorityHGNC:11005Mapping file id6513 NCBI fileEvidenceTAS
GeneSLC2A10AuthorityHGNC:13444Mapping file id81031 NCBI fileEvidenceTAS
GeneSLC2A11AuthorityHGNC:14239Mapping file id66035 NCBI fileEvidenceTAS
GeneSLC2A12AuthorityHGNC:18067Mapping file id154091 NCBI fileEvidenceTAS
GeneSLC2A13AuthorityHGNC:15956Mapping file id114134 NCBI fileEvidenceTAS
GeneSLC2A14AuthorityHGNC:18301Mapping file id144195 NCBI fileEvidenceTAS
GeneSLC2A2AuthorityHGNC:11006Mapping file id6514 NCBI fileEvidenceTAS
GeneSLC2A3AuthorityHGNC:11007Mapping file id6515 NCBI fileEvidenceTAS
GeneSLC2A4AuthorityHGNC:11009Mapping file id6517 NCBI fileEvidenceTAS
GeneSLC2A6AuthorityHGNC:11011Mapping file id11182 NCBI fileEvidenceTAS
GeneSLC2A7AuthorityHGNC:13445Mapping file id155184 NCBI fileEvidenceTAS
GeneSLC2A8AuthorityHGNC:13812Mapping file id29988 NCBI fileEvidenceTAS
GeneSLC2A9AuthorityHGNC:13446Mapping file id56606 NCBI fileEvidenceTAS
GeneSLC30A1AuthorityHGNC:11012Mapping file id7779 NCBI fileEvidenceTAS
GeneSLC30A10AuthorityHGNC:25355Mapping file id55532 NCBI fileEvidenceTAS
GeneSLC30A2AuthorityHGNC:11013Mapping file id7780 NCBI fileEvidenceIEA
GeneSLC30A3AuthorityHGNC:11014Mapping file id7781 NCBI fileEvidenceIEA
GeneSLC30A5AuthorityHGNC:19089Mapping file id64924 NCBI fileEvidenceTAS
GeneSLC30A8AuthorityHGNC:20303Mapping file id169026 NCBI fileEvidenceTAS
GeneSLC31A1AuthorityHGNC:11016Mapping file id1317 NCBI fileEvidenceTAS
GeneSLC32A1AuthorityHGNC:11018Mapping file id140679 NCBI fileEvidenceTAS
GeneSLC33A1AuthorityHGNC:95Mapping file id9197 NCBI fileEvidenceTAS
GeneSLC34A1AuthorityHGNC:11019Mapping file id6569 NCBI fileEvidenceTAS
GeneSLC34A2AuthorityHGNC:11020Mapping file id10568 NCBI fileEvidenceTAS
GeneSLC34A3AuthorityHGNC:20305Mapping file id142680 NCBI fileEvidenceTAS
GeneSLC35A1AuthorityHGNC:11021Mapping file id10559 NCBI fileEvidenceTAS
GeneSLC35A2AuthorityHGNC:11022Mapping file id7355 NCBI fileEvidenceTAS
GeneSLC35A3AuthorityHGNC:11023Mapping file id23443 NCBI fileEvidenceTAS
GeneSLC35B2AuthorityHGNC:16872Mapping file id347734 NCBI fileEvidenceTAS
GeneSLC35B3AuthorityHGNC:21601Mapping file id51000 NCBI fileEvidenceTAS
GeneSLC35B4AuthorityHGNC:20584Mapping file id84912 NCBI fileEvidenceTAS
GeneSLC35C1AuthorityHGNC:20197Mapping file id55343 NCBI fileEvidenceTAS
GeneSLC35D1AuthorityHGNC:20800Mapping file id23169 NCBI fileEvidenceTAS
GeneSLC35D2AuthorityHGNC:20799Mapping file id11046 NCBI fileEvidenceIEA, TAS
GeneSLC36A1AuthorityHGNC:18761Mapping file id206358 NCBI fileEvidenceTAS
GeneSLC36A2AuthorityHGNC:18762Mapping file id153201 NCBI fileEvidenceTAS
GeneSLC36A4AuthorityHGNC:19660Mapping file id120103 NCBI fileEvidenceTAS
GeneSLC38A1AuthorityHGNC:13447Mapping file id81539 NCBI fileEvidenceTAS
GeneSLC38A2AuthorityHGNC:13448Mapping file id54407 NCBI fileEvidenceTAS
GeneSLC38A3AuthorityHGNC:18044Mapping file id10991 NCBI fileEvidenceTAS
GeneSLC38A4AuthorityHGNC:14679Mapping file id55089 NCBI fileEvidenceTAS
GeneSLC38A5AuthorityHGNC:18070Mapping file id92745 NCBI fileEvidenceTAS
GeneSLC39A1AuthorityHGNC:12876Mapping file id27173 NCBI fileEvidenceTAS
GeneSLC39A10AuthorityHGNC:20861Mapping file id57181 NCBI fileEvidenceIEA
GeneSLC39A14AuthorityHGNC:20858Mapping file id23516 NCBI fileEvidenceTAS
GeneSLC39A2AuthorityHGNC:17127Mapping file id29986 NCBI fileEvidenceTAS
GeneSLC39A3AuthorityHGNC:17128Mapping file id29985 NCBI fileEvidenceTAS
GeneSLC39A4AuthorityHGNC:17129Mapping file id55630 NCBI fileEvidenceTAS
GeneSLC39A5AuthorityHGNC:20502Mapping file id283375 NCBI fileEvidenceIEA
GeneSLC39A6AuthorityHGNC:18607Mapping file id25800 NCBI fileEvidenceTAS
GeneSLC39A7AuthorityHGNC:4927Mapping file id7922 NCBI fileEvidenceTAS
GeneSLC39A8AuthorityHGNC:20862Mapping file id64116 NCBI fileEvidenceTAS
GeneSLC3A1AuthorityHGNC:11025Mapping file id6519 NCBI fileEvidenceTAS
GeneSLC3A2AuthorityHGNC:11026Mapping file id6520 NCBI fileEvidenceTAS
GeneSLC40A1AuthorityHGNC:10909Mapping file id30061 NCBI fileEvidenceTAS
GeneSLC41A1AuthorityHGNC:19429Mapping file id254428 NCBI fileEvidenceTAS
GeneSLC41A2AuthorityHGNC:31045Mapping file id84102 NCBI fileEvidenceTAS
GeneSLC43A1AuthorityHGNC:9225Mapping file id8501 NCBI fileEvidenceTAS
GeneSLC43A2AuthorityHGNC:23087Mapping file id124935 NCBI fileEvidenceTAS
GeneSLC44A1AuthorityHGNC:18798Mapping file id23446 NCBI fileEvidenceTAS
GeneSLC44A2AuthorityHGNC:17292Mapping file id57153 NCBI fileEvidenceTAS
GeneSLC44A3AuthorityHGNC:28689Mapping file id126969 NCBI fileEvidenceTAS
GeneSLC44A4AuthorityHGNC:13941Mapping file id80736 NCBI fileEvidenceTAS
GeneSLC44A5AuthorityHGNC:28524Mapping file id204962 NCBI fileEvidenceTAS
GeneSLC45A3AuthorityHGNC:8642Mapping file id85414 NCBI fileEvidenceTAS
GeneSLC47A1AuthorityHGNC:25588Mapping file id55244 NCBI fileEvidenceTAS
GeneSLC47A2AuthorityHGNC:26439Mapping file id146802 NCBI fileEvidenceTAS
GeneSLC4A1AuthorityHGNC:11027Mapping file id6521 NCBI fileEvidenceTAS
GeneSLC4A10AuthorityHGNC:13811Mapping file id57282 NCBI fileEvidenceTAS
GeneSLC4A2AuthorityHGNC:11028Mapping file id6522 NCBI fileEvidenceTAS
GeneSLC4A3AuthorityHGNC:11029Mapping file id6508 NCBI fileEvidenceTAS
GeneSLC4A4AuthorityHGNC:11030Mapping file id8671 NCBI fileEvidenceTAS
GeneSLC4A5AuthorityHGNC:18168Mapping file id57835 NCBI fileEvidenceTAS
GeneSLC4A7AuthorityHGNC:11033Mapping file id9497 NCBI fileEvidenceTAS
GeneSLC4A8AuthorityHGNC:11034Mapping file id9498 NCBI fileEvidenceTAS
GeneSLC4A9AuthorityHGNC:11035Mapping file id83697 NCBI fileEvidenceTAS
GeneSLC50A1AuthorityHGNC:30657Mapping file id55974 NCBI fileEvidenceTAS
GeneSLC5A1AuthorityHGNC:11036Mapping file id6523 NCBI fileEvidenceTAS
GeneSLC5A10AuthorityHGNC:23155Mapping file id125206 NCBI fileEvidenceTAS
GeneSLC5A11AuthorityHGNC:23091Mapping file id115584 NCBI fileEvidenceTAS
GeneSLC5A12AuthorityHGNC:28750Mapping file id159963 NCBI fileEvidenceTAS
GeneSLC5A2AuthorityHGNC:11037Mapping file id6524 NCBI fileEvidenceTAS
GeneSLC5A3AuthorityHGNC:11038Mapping file id6526 NCBI fileEvidenceTAS
GeneSLC5A4AuthorityHGNC:11039Mapping file id6527 NCBI fileEvidenceTAS
GeneSLC5A5AuthorityHGNC:11040Mapping file id6528 NCBI fileEvidenceTAS
GeneSLC5A6AuthorityHGNC:11041Mapping file id8884 NCBI fileEvidenceTAS
GeneSLC5A7AuthorityHGNC:14025Mapping file id60482 NCBI fileEvidenceTAS
GeneSLC5A8AuthorityHGNC:19119Mapping file id160728 NCBI fileEvidenceTAS
GeneSLC5A9AuthorityHGNC:22146Mapping file id200010 NCBI fileEvidenceTAS
GeneSLC60A2AuthorityHGNC:21053Mapping file id91749 NCBI fileEvidenceTAS
GeneSLC67A1AuthorityHGNC:10964Mapping file id5002 NCBI fileEvidenceTAS
GeneSLC6A1AuthorityHGNC:11042Mapping file id6529 NCBI fileEvidenceTAS
GeneSLC6A11AuthorityHGNC:11044Mapping file id6538 NCBI fileEvidenceTAS
GeneSLC6A12AuthorityHGNC:11045Mapping file id6539 NCBI fileEvidenceTAS
GeneSLC6A13AuthorityHGNC:11046Mapping file id6540 NCBI fileEvidenceTAS

Evidence codes on this page: IEA, 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

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.