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.

Axon guidance

R-MMU-422475 in Reactome release 97: under Nervous system development, with 262 genes placed in it by the mapping files and 8 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-422475 (human), R-RNO-422475 (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 262 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
GeneFrs2Authority327826Mapping file id327826 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneGab1Authority14388Mapping file id14388 NCBI fileEvidenceIEA
GeneGap43Authority14432Mapping file id14432 NCBI fileEvidenceIEA
GeneGdnfAuthority14573Mapping file id14573 NCBI fileEvidenceIEA
GeneGfra1Authority14585Mapping file id14585 NCBI fileEvidenceIEA
GeneGfra2Authority14586Mapping file id14586 NCBI fileEvidenceIEA
GeneGfra3Authority14587Mapping file id14587 NCBI fileEvidenceIEA
GeneGfra4Authority14588Mapping file id14588 NCBI fileEvidenceIEA
GeneGit1Authority216963Mapping file id216963 NCBI fileEvidenceIEA
GeneGpc1Authority14733Mapping file id14733 NCBI fileEvidenceIEA
GeneGrb10Authority14783Mapping file id14783 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrb7Authority14786Mapping file id14786 NCBI fileEvidenceIEA
GeneGrin1Authority14810Mapping file id14810 NCBI fileEvidenceIEA
GeneGrin2bAuthority14812Mapping file id14812 NCBI fileEvidenceIEA
GeneGsk3bAuthority56637Mapping file id56637 NCBI fileEvidenceIEA
GeneHrasAuthority15461Mapping file id15461 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneHsp90ab1Authority15516Mapping file id15516 NCBI fileEvidenceIEA
GeneIrs2Authority384783Mapping file id384783 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
GeneItsn1Authority16443Mapping file id16443 NCBI fileEvidenceIEA
GeneKalrnAuthority545156Mapping file id545156 NCBI fileEvidenceIEA
GeneKif4Authority16571Mapping file id16571 NCBI fileEvidenceIEA
GeneKrasAuthority16653Mapping file id16653 NCBI fileEvidenceIEA
GeneLimk1Authority16885Mapping file id16885 NCBI fileEvidenceIEA
GeneLynAuthority17096Mapping file id17096 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
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMetAuthority17295Mapping file idENSMUSG00000009376 Ensembl fileEvidenceIEA
GeneMmp2Authority17390Mapping file id17390 NCBI fileEvidenceIEA
GeneMmp9Authority17395Mapping file id17395 NCBI fileEvidenceIEA
GeneMsnAuthority17698Mapping file id17698 NCBI fileEvidenceIEA
GeneMyo9bAuthority17925Mapping file idENSMUSG00000004677 Ensembl fileEvidenceIEA
GeneNcam1Authority17967Mapping file id17967 NCBI fileEvidenceIEA
GeneNck1Authority17973Mapping file id17973 NCBI fileEvidenceIEA
GeneNck2Authority17974Mapping file id17974 NCBI fileEvidenceIEA
GeneNcstnAuthority59287Mapping file id59287 NCBI fileEvidenceIEA
GeneNfascAuthority269116Mapping file id269116 NCBI fileEvidenceIEA
GeneNgefAuthority53972Mapping file id53972 NCBI fileEvidenceIEA
GeneNrp1Authority18186Mapping file id18186 NCBI fileEvidenceIEA
GeneNrtnAuthority18188Mapping file id18188 NCBI fileEvidenceIEA
GeneNtn4Authority57764Mapping file id57764 NCBI fileEvidenceIEA
GeneNumbAuthority18222Mapping file id18222 NCBI fileEvidenceIEA
GenePak1Authority18479Mapping file idENSMUSG00000030774 Ensembl fileEvidenceIEA
GenePak2Authority224105Mapping file id224105 NCBI fileEvidenceIEA
GenePak3Authority18481Mapping file id18481 NCBI fileEvidenceIEA
GenePdlim7Authority67399Mapping file id67399 NCBI fileEvidenceIEA
GenePfn1Authority18643Mapping file id18643 NCBI fileEvidenceIEA
GenePfn2Authority18645Mapping file id18645 NCBI fileEvidenceIEA
GenePik3caAuthority18706Mapping file id18706 NCBI fileEvidenceIEA
GenePik3cbAuthority74769Mapping file id74769 NCBI fileEvidenceIEA
GenePik3cdAuthority18707Mapping file id18707 NCBI fileEvidenceIEA
GenePik3r1Authority18708Mapping file id18708 NCBI fileEvidenceIEA
GenePik3r2Authority18709Mapping file id18709 NCBI fileEvidenceIEA
GenePik3r3Authority18710Mapping file id18710 NCBI fileEvidenceIEA
GenePip5k1cAuthority18717Mapping file id18717 NCBI fileEvidenceIEA
GenePlcg1Authority18803Mapping file id18803 NCBI fileEvidenceIEA
GenePlxna1Authority18844Mapping file id18844 NCBI fileEvidenceIEA
GenePlxna2Authority18845Mapping file id18845 NCBI fileEvidenceIEA
GenePlxna3Authority18846Mapping file id18846 NCBI fileEvidenceIEA
GenePlxna4Authority243743Mapping file id243743 NCBI fileEvidenceIEA
GenePlxnb1Authority235611Mapping file id235611 NCBI fileEvidenceIEA
GenePlxnb3Authority140571Mapping file id140571 NCBI fileEvidenceIEA
GenePlxnc1Authority54712Mapping file id54712 NCBI fileEvidenceIEA
GenePlxnd1Authority67784Mapping file id67784 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkacbAuthority18749Mapping file id18749 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GenePrkcqAuthority18761Mapping file id18761 NCBI fileEvidenceIEA
GenePsen1Authority19164Mapping file id19164 NCBI fileEvidenceIEA
GenePsen2Authority19165Mapping file id19165 NCBI fileEvidenceIEA
GenePsenenAuthority66340Mapping file id66340 NCBI fileEvidenceIEA
GenePspnAuthority19197Mapping file idENSMUSG00000002664 Ensembl fileEvidenceIEA
GenePtk2Authority14083Mapping file id14083 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GenePtpraAuthority19262Mapping file id19262 NCBI fileEvidenceIEA
GenePtprcAuthority19264Mapping file id19264 NCBI fileEvidenceIEA
GeneRac1Authority19353Mapping file id19353 NCBI fileEvidenceIEA
GeneRanbp9Authority56705Mapping file id56705 NCBI fileEvidenceIEA
GeneRap1gapAuthority110351Mapping file id110351 NCBI fileEvidenceIEA
GeneRasa1Authority218397Mapping file id218397 NCBI fileEvidenceIEA
GeneRdxAuthority19684Mapping file id19684 NCBI fileEvidenceIEA
GeneRelnAuthority19699Mapping file id19699 NCBI fileEvidenceIEA
GeneRetAuthority19713Mapping file id19713 NCBI fileEvidenceIEA
GeneRhoaAuthority11848Mapping file id11848 NCBI fileEvidenceIEA
GeneRhobAuthority11852Mapping file id11852 NCBI fileEvidenceIEA
GeneRhocAuthority11853Mapping file id11853 NCBI fileEvidenceIEA
GeneRnd1Authority223881Mapping file id223881 NCBI fileEvidenceIEA
GeneRobo1Authority19876Mapping file id19876 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.