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.

SLC-mediated transmembrane transport

R-MMU-425407 in Reactome release 97: under Transport of small molecules, with 230 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-425407 (human), 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.

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 230 genes in this mouse pathway; showing 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 3
GeneSlc2a1Authority20525Mapping file id20525 NCBI fileEvidenceIEA
GeneSlc2a10Authority170441Mapping file id170441 NCBI fileEvidenceIEA
GeneSlc2a12Authority353169Mapping file id353169 NCBI fileEvidenceIEA
GeneSlc2a13Authority239606Mapping file id239606 NCBI fileEvidenceIEA
GeneSlc2a2Authority20526Mapping file id20526 NCBI fileEvidenceIEA
GeneSlc2a3Authority20527Mapping file id20527 NCBI fileEvidenceIEA
GeneSlc2a4Authority20528Mapping file id20528 NCBI fileEvidenceIEA
GeneSlc2a6Authority227659Mapping file id227659 NCBI fileEvidenceIEA
GeneSlc2a7Authority435818Mapping file idENSMUSG00000062064 Ensembl fileEvidenceIEA
GeneSlc2a8Authority56017Mapping file id56017 NCBI fileEvidenceIEA
GeneSlc2a9Authority117591Mapping file id117591 NCBI fileEvidenceIEA
GeneSlc30a1Authority22782Mapping file id22782 NCBI fileEvidenceIEA
GeneSlc30a10Authority226781Mapping file id226781 NCBI fileEvidenceIEA
GeneSlc30a5Authority69048Mapping file id69048 NCBI fileEvidenceIEA
GeneSlc30a8Authority239436Mapping file id239436 NCBI fileEvidenceIEA
GeneSlc31a1Authority20529Mapping file id20529 NCBI fileEvidenceIEA
GeneSlc32a1Authority22348Mapping file id22348 NCBI fileEvidenceIEA
GeneSlc33a1Authority11416Mapping file id11416 NCBI fileEvidenceIEA
GeneSlc34a1Authority20505Mapping file idENSMUSG00000021490 Ensembl fileEvidenceIEA
GeneSlc34a2Authority20531Mapping file id20531 NCBI fileEvidenceIEA
GeneSlc34a3Authority142681Mapping file id142681 NCBI fileEvidenceIEA
GeneSlc35a1Authority24060Mapping file id24060 NCBI fileEvidenceIEA
GeneSlc35a2Authority22232Mapping file id22232 NCBI fileEvidenceIEA
GeneSlc35a3Authority229782Mapping file id229782 NCBI fileEvidenceIEA
GeneSlc35b2Authority73836Mapping file id73836 NCBI fileEvidenceIEA
GeneSlc35b3Authority108652Mapping file id108652 NCBI fileEvidenceIEA
GeneSlc35b4Authority58246Mapping file id58246 NCBI fileEvidenceIEA
GeneSlc35c1Authority228368Mapping file id228368 NCBI fileEvidenceIEA
GeneSlc35d1Authority242585Mapping file id242585 NCBI fileEvidenceIEA
GeneSlc35d2Authority70484Mapping file id70484 NCBI fileEvidenceIEA
GeneSlc36a1Authority215335Mapping file id215335 NCBI fileEvidenceIEA
GeneSlc36a2Authority246049Mapping file id246049 NCBI fileEvidenceIEA
GeneSlc36a4Authority234967Mapping file id234967 NCBI fileEvidenceIEA
GeneSlc38a1Authority105727Mapping file id105727 NCBI fileEvidenceIEA
GeneSlc38a2Authority67760Mapping file id67760 NCBI fileEvidenceIEA
GeneSlc38a3Authority76257Mapping file id76257 NCBI fileEvidenceIEA
GeneSlc38a4Authority69354Mapping file id69354 NCBI fileEvidenceIEA
GeneSlc38a5Authority209837Mapping file id209837 NCBI fileEvidenceIEA
GeneSlc39a1Authority30791Mapping file id30791 NCBI fileEvidenceIEA
GeneSlc39a14Authority213053Mapping file id213053 NCBI fileEvidenceIEA
GeneSlc39a2Authority214922Mapping file id214922 NCBI fileEvidenceIEA
GeneSlc39a3Authority106947Mapping file id106947 NCBI fileEvidenceIEA
GeneSlc39a4Authority72027Mapping file id72027 NCBI fileEvidenceIEA
GeneSlc39a6Authority106957Mapping file id106957 NCBI fileEvidenceIEA
GeneSlc39a7Authority14977Mapping file id14977 NCBI fileEvidenceIEA
GeneSlc39a8Authority67547Mapping file id67547 NCBI fileEvidenceIEA
GeneSlc3a1Authority20532Mapping file id20532 NCBI fileEvidenceIEA
GeneSlc3a2Authority17254Mapping file id17254 NCBI fileEvidenceIEA
GeneSlc40a1Authority53945Mapping file id53945 NCBI fileEvidenceIEA
GeneSlc41a1Authority98396Mapping file id98396 NCBI fileEvidenceIEA
GeneSlc41a2Authority338365Mapping file id338365 NCBI fileEvidenceIEA
GeneSlc43a1Authority72401Mapping file id72401 NCBI fileEvidenceIEA
GeneSlc43a2Authority215113Mapping file id215113 NCBI fileEvidenceIEA
GeneSlc44a1Authority100434Mapping file id100434 NCBI fileEvidenceIEA
GeneSlc44a2Authority68682Mapping file id68682 NCBI fileEvidenceIEA
GeneSlc44a3Authority213603Mapping file id213603 NCBI fileEvidenceIEA
GeneSlc44a4Authority70129Mapping file id70129 NCBI fileEvidenceIEA
GeneSlc44a5Authority242259Mapping file id242259 NCBI fileEvidenceIEA
GeneSlc45a3Authority212980Mapping file id212980 NCBI fileEvidenceIEA
GeneSlc47a1Authority67473Mapping file id67473 NCBI fileEvidenceIEA
GeneSlc4a1Authority20533Mapping file id20533 NCBI fileEvidenceIEA
GeneSlc4a10Authority94229Mapping file id94229 NCBI fileEvidenceIEA
GeneSlc4a2Authority20535Mapping file id20535 NCBI fileEvidenceIEA
GeneSlc4a3Authority20536Mapping file id20536 NCBI fileEvidenceIEA
GeneSlc4a4Authority54403Mapping file id54403 NCBI fileEvidenceIEA
GeneSlc4a5Authority232156Mapping file idENSMUSG00000068323 Ensembl fileEvidenceIEA
GeneSlc4a7Authority218756Mapping file idENSMUSG00000021733 Ensembl fileEvidenceIEA
GeneSlc4a8Authority59033Mapping file id59033 NCBI fileEvidenceIEA
GeneSlc4a9Authority240215Mapping file id240215 NCBI fileEvidenceIEA
GeneSlc50a1Authority19729Mapping file id19729 NCBI fileEvidenceIEA
GeneSlc5a1Authority20537Mapping file id20537 NCBI fileEvidenceIEA
GeneSlc5a10Authority109342Mapping file id109342 NCBI fileEvidenceIEA
GeneSlc5a11Authority233836Mapping file id233836 NCBI fileEvidenceIEA
GeneSlc5a12Authority241612Mapping file id241612 NCBI fileEvidenceIEA
GeneSlc5a2Authority246787Mapping file id246787 NCBI fileEvidenceIEA
GeneSlc5a3Authority53881Mapping file id53881 NCBI fileEvidenceIEA
GeneSlc5a4aAuthority64452Mapping file id64452 NCBI fileEvidenceIEA
GeneSlc5a5Authority114479Mapping file idENSMUSG00000000792 Ensembl fileEvidenceIEA
GeneSlc5a6Authority330064Mapping file id330064 NCBI fileEvidenceIEA
GeneSlc5a7Authority63993Mapping file id63993 NCBI fileEvidenceIEA
GeneSlc5a8Authority216225Mapping file id216225 NCBI fileEvidenceIEA
GeneSlc5a9Authority230612Mapping file id230612 NCBI fileEvidenceIEA
GeneSlc60a2bAuthority213332Mapping file id213332 NCBI fileEvidenceIEA
GeneSlc67a1Authority18400Mapping file id18400 NCBI fileEvidenceIEA
GeneSlc6a1Authority232333Mapping file id232333 NCBI fileEvidenceIEA
GeneSlc6a11Authority243616Mapping file id243616 NCBI fileEvidenceIEA
GeneSlc6a12Authority14411Mapping file idENSMUSG00000030109 Ensembl fileEvidenceIEA
GeneSlc6a13Authority14412Mapping file id14412 NCBI fileEvidenceIEA
GeneSlc6a14Authority56774Mapping file id56774 NCBI fileEvidenceIEA
GeneSlc6a15Authority103098Mapping file id103098 NCBI fileEvidenceIEA
GeneSlc6a19Authority74338Mapping file id74338 NCBI fileEvidenceIEA
GeneSlc6a2Authority20538Mapping file id20538 NCBI fileEvidenceIEA
GeneSlc6a20aAuthority102680Mapping file id102680 NCBI fileEvidenceIEA
GeneSlc6a3Authority13162Mapping file id13162 NCBI fileEvidenceIEA
GeneSlc6a4Authority15567Mapping file id15567 NCBI fileEvidenceIEA
GeneSlc6a5Authority104245Mapping file idENSMUSG00000039728 Ensembl fileEvidenceIEA
GeneSlc6a6Authority21366Mapping file id21366 NCBI fileEvidenceIEA
GeneSlc6a7Authority240332Mapping file id240332 NCBI fileEvidenceIEA
GeneSlc6a9Authority14664Mapping file id14664 NCBI fileEvidenceIEA
GeneSlc7a1Authority11987Mapping file id11987 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.