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.

L1CAM interactions

R-MMU-373760 in Reactome release 97: under Axon guidance, with 68 genes placed in it by the mapping files and 4 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-373760 (human), R-RNO-373760 (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 68 genes in this mouse pathway; showing 1 to 68, 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
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneAnk1Authority11733Mapping file id11733 NCBI fileEvidenceIEA
GeneAp2a1Authority11771Mapping file id11771 NCBI fileEvidenceIEA
GeneAp2a2Authority11772Mapping file id11772 NCBI fileEvidenceIEA
GeneAp2b1Authority71770Mapping file id71770 NCBI fileEvidenceIEA
GeneAp2m1Authority11773Mapping file id11773 NCBI fileEvidenceIEA
GeneAp2s1Authority232910Mapping file id232910 NCBI fileEvidenceIEA
GeneCltaAuthority12757Mapping file idENSMUSG00000028478 Ensembl fileEvidenceIEA
GeneCltcAuthority67300Mapping file id67300 NCBI fileEvidenceIEA
GeneCsnk2a1Authority12995Mapping file id12995 NCBI fileEvidenceIEA
GeneCsnk2a2Authority13000Mapping file id13000 NCBI fileEvidenceIEA
GeneCsnk2bAuthority13001Mapping file id13001 NCBI fileEvidenceIEA
GeneDnm1Authority13429Mapping file id13429 NCBI fileEvidenceIEA
GeneDnm2Authority13430Mapping file id13430 NCBI fileEvidenceIEA
GeneDnm3Authority103967Mapping file id103967 NCBI fileEvidenceIEA
GeneDpysl2Authority12934Mapping file id12934 NCBI fileEvidenceIEA
GeneEgfrAuthority13649Mapping file id13649 NCBI fileEvidenceIEA
GeneEzrAuthority22350Mapping file id22350 NCBI fileEvidenceIEA
GeneFgfr1Authority14182Mapping file id14182 NCBI fileEvidenceIEA
GeneGap43Authority14432Mapping file id14432 NCBI fileEvidenceIEA
GeneItga2bAuthority16399Mapping file id16399 NCBI fileEvidenceIEA
GeneItga5Authority16402Mapping file id16402 NCBI fileEvidenceIEA
GeneItga9Authority104099Mapping file id104099 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneKif4Authority16571Mapping file id16571 NCBI fileEvidenceIEA
GeneLypla2Authority26394Mapping file id26394 NCBI fileEvidenceIEA
GeneMap2k1Authority26395Mapping file id26395 NCBI fileEvidenceIEA
GeneMap2k2Authority26396Mapping file id26396 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMsnAuthority17698Mapping file id17698 NCBI fileEvidenceIEA
GeneNcam1Authority17967Mapping file id17967 NCBI fileEvidenceIEA
GeneNfascAuthority269116Mapping file id269116 NCBI fileEvidenceIEA
GeneNrp1Authority18186Mapping file id18186 NCBI fileEvidenceIEA
GeneNumbAuthority18222Mapping file id18222 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 NCBI fileEvidenceIEA
GeneRanbp9Authority56705Mapping file id56705 NCBI fileEvidenceIEA
GeneRdxAuthority19684Mapping file id19684 NCBI fileEvidenceIEA
GeneSdcbpAuthority53378Mapping file id53378 NCBI fileEvidenceIEA
GeneSh3gl2Authority20404Mapping file id20404 NCBI fileEvidenceIEA
GeneSpta1Authority20739Mapping file id20739 NCBI fileEvidenceIEA
GeneSptan1Authority20740Mapping file id20740 NCBI fileEvidenceIEA
GeneSptbAuthority20741Mapping file idENSMUSG00000021061 Ensembl fileEvidenceIEA
GeneSptbn1Authority20742Mapping file id20742 NCBI fileEvidenceIEA
GeneSptbn2Authority20743Mapping file id20743 NCBI fileEvidenceIEA
GeneSptbn4Authority80297Mapping file id80297 NCBI fileEvidenceIEA
GeneSptbn5Authority640524Mapping file idENSMUSG00000074899 Ensembl fileEvidenceIEA
GeneSrcAuthority20779Mapping file id20779 NCBI fileEvidenceIEA
GeneTuba1aAuthority22142Mapping file id22142 NCBI fileEvidenceIEA
GeneTuba1bAuthority22143Mapping file id22143 NCBI fileEvidenceIEA
GeneTuba1cAuthority22146Mapping file id22146 NCBI fileEvidenceIEA
GeneTuba3aAuthority22144Mapping file id22144 NCBI fileEvidenceIEA
GeneTuba3bAuthority22147Mapping file id22147 NCBI fileEvidenceIEA
GeneTuba4aAuthority22145Mapping file id22145 NCBI fileEvidenceIEA
GeneTuba8Authority53857Mapping file id53857 NCBI fileEvidenceIEA
GeneTubal3Authority238463Mapping file id238463 NCBI fileEvidenceIEA
GeneTubb1Authority545486Mapping file id545486 NCBI fileEvidenceIEA
GeneTubb2aAuthority22151Mapping file id22151 NCBI fileEvidenceIEA
GeneTubb2bAuthority73710Mapping file id73710 NCBI fileEvidenceIEA
GeneTubb3Authority22152Mapping file id22152 NCBI fileEvidenceIEA
GeneTubb4aAuthority22153Mapping file id22153 NCBI fileEvidenceIEA
GeneTubb4bAuthority227613Mapping file id227613 NCBI fileEvidenceIEA
GeneTubb6Authority67951Mapping file id67951 NCBI fileEvidenceIEA
GeneVav2Authority22325Mapping file id22325 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.