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 1 to 100, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 3
GeneAbl1Authority11350Mapping file id11350 NCBI fileEvidenceIEA
GeneAbl2Authority11352Mapping file idENSMUSG00000026596 Ensembl fileEvidenceIEA
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneActr2Authority66713Mapping file id66713 NCBI fileEvidenceIEA
GeneActr3Authority74117Mapping file id74117 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
GeneAph1aAuthority226548Mapping file id226548 NCBI fileEvidenceIEA
GeneAph1bAuthority208117Mapping file id208117 NCBI fileEvidenceIEA
GeneArhgap35Authority232906Mapping file id232906 NCBI fileEvidenceIEA
GeneArhgef11Authority213498Mapping file id213498 NCBI fileEvidenceIEA
GeneArhgef12Authority69632Mapping file id69632 NCBI fileEvidenceIEA
GeneArhgef28Authority110596Mapping file id110596 NCBI fileEvidenceIEA
GeneArhgef7Authority54126Mapping file id54126 NCBI fileEvidenceIEA
GeneArpc1aAuthority56443Mapping file id56443 NCBI fileEvidenceIEA
GeneArpc1bAuthority11867Mapping file id11867 NCBI fileEvidenceIEA
GeneArpc2Authority76709Mapping file id76709 NCBI fileEvidenceIEA
GeneArpc3Authority56378Mapping file id56378 NCBI fileEvidenceIEA
GeneArpc4Authority68089Mapping file id68089 NCBI fileEvidenceIEA
GeneArpc5Authority67771Mapping file id67771 NCBI fileEvidenceIEA
GeneArtnAuthority11876Mapping file id11876 NCBI fileEvidenceIEA
GeneCd72Authority12517Mapping file id12517 NCBI fileEvidenceIEA
GeneCdc42Authority12540Mapping file id12540 NCBI fileEvidenceIEA
GeneCdk5Authority12568Mapping file id12568 NCBI fileEvidenceIEA
GeneCdk5r1Authority12569Mapping file id12569 NCBI fileEvidenceIEA
GeneCltaAuthority12757Mapping file idENSMUSG00000028478 Ensembl fileEvidenceIEA
GeneCltcAuthority67300Mapping file id67300 NCBI fileEvidenceIEA
GeneCol2a1Authority12824Mapping file id12824 NCBI fileEvidenceIEA
GeneCol3a1Authority12825Mapping file id12825 NCBI fileEvidenceIEA
GeneCol4a1Authority12826Mapping file id12826 NCBI fileEvidenceIEA
GeneCol4a2Authority12827Mapping file id12827 NCBI fileEvidenceIEA
GeneCol5a1Authority12831Mapping file id12831 NCBI fileEvidenceIEA
GeneCol5a2Authority12832Mapping file id12832 NCBI fileEvidenceIEA
GeneCol5a3Authority53867Mapping file id53867 NCBI fileEvidenceIEA
GeneCol6a1Authority12833Mapping file id12833 NCBI fileEvidenceIEA
GeneCol6a2Authority12834Mapping file id12834 NCBI fileEvidenceIEA
GeneCol6a3Authority12835Mapping file idENSMUSG00000048126 Ensembl fileEvidenceIEA
GeneCol6a5Authority665033Mapping file id665033 NCBI fileEvidenceIEA
GeneCol6a6Authority245026Mapping file id245026 NCBI fileEvidenceIEA
GeneCol9a1Authority12839Mapping file id12839 NCBI fileEvidenceIEA
GeneCol9a2Authority12840Mapping file idENSMUSG00000028626 Ensembl fileEvidenceIEA
GeneCol9a3Authority12841Mapping file id12841 NCBI fileEvidenceIEA
GeneCreb1Authority12912Mapping file id12912 NCBI fileEvidenceIEA
GeneCrmp1Authority12933Mapping file id12933 NCBI fileEvidenceIEA
GeneCsnk2a1Authority12995Mapping file id12995 NCBI fileEvidenceIEA
GeneCsnk2a2Authority13000Mapping file id13000 NCBI fileEvidenceIEA
GeneCsnk2bAuthority13001Mapping file id13001 NCBI fileEvidenceIEA
GeneCxcl12Authority20315Mapping file id20315 NCBI fileEvidenceIEA
GeneCxcr4Authority12767Mapping file id12767 NCBI fileEvidenceIEA
GeneDab1Authority13131Mapping file id13131 NCBI fileEvidenceIEA
GeneDag1Authority13138Mapping file id13138 NCBI fileEvidenceIEA
GeneDccAuthority13176Mapping file id13176 NCBI fileEvidenceIEA
GeneDnm1Authority13429Mapping file id13429 NCBI fileEvidenceIEA
GeneDnm2Authority13430Mapping file id13430 NCBI fileEvidenceIEA
GeneDnm3Authority103967Mapping file id103967 NCBI fileEvidenceIEA
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneDok1Authority13448Mapping file id13448 NCBI fileEvidenceIEA
GeneDok2Authority13449Mapping file id13449 NCBI fileEvidenceIEA
GeneDok4Authority114255Mapping file id114255 NCBI fileEvidenceIEA
GeneDok5Authority76829Mapping file id76829 NCBI fileEvidenceIEA
GeneDok6Authority623279Mapping file id623279 NCBI fileEvidenceIEA
GeneDpysl2Authority12934Mapping file id12934 NCBI fileEvidenceIEA
GeneDpysl3Authority22240Mapping file id22240 NCBI fileEvidenceIEA
GeneDpysl4Authority26757Mapping file idENSMUSG00000025478 Ensembl fileEvidenceIEA
GeneDpysl5Authority65254Mapping file id65254 NCBI fileEvidenceIEA
GeneDscamAuthority13508Mapping file id13508 NCBI fileEvidenceIEA
GeneDscaml1Authority114873Mapping file id114873 NCBI fileEvidenceIEA
GeneEfna1Authority13636Mapping file id13636 NCBI fileEvidenceIEA
GeneEfna2Authority13637Mapping file id13637 NCBI fileEvidenceIEA
GeneEfna3Authority13638Mapping file id13638 NCBI fileEvidenceIEA
GeneEfna4Authority13639Mapping file id13639 NCBI fileEvidenceIEA
GeneEfna5Authority13640Mapping file id13640 NCBI fileEvidenceIEA
GeneEfnb1Authority13641Mapping file id13641 NCBI fileEvidenceIEA
GeneEfnb2Authority13642Mapping file id13642 NCBI fileEvidenceIEA
GeneEfnb3Authority13643Mapping file id13643 NCBI fileEvidenceIEA
GeneEgfrAuthority13649Mapping file id13649 NCBI fileEvidenceIEA
GeneEnahAuthority13800Mapping file id13800 NCBI fileEvidenceIEA
GeneEpha1Authority13835Mapping file id13835 NCBI fileEvidenceIEA
GeneEpha10Authority230735Mapping file id230735 NCBI fileEvidenceIEA
GeneEpha2Authority13836Mapping file id13836 NCBI fileEvidenceIEA
GeneEpha4Authority13838Mapping file id13838 NCBI fileEvidenceIEA
GeneEpha6Authority13840Mapping file idENSMUSG00000055540 Ensembl fileEvidenceIEA
GeneEpha7Authority13841Mapping file id13841 NCBI fileEvidenceIEA
GeneEpha8Authority13842Mapping file id13842 NCBI fileEvidenceIEA
GeneEphb1Authority270190Mapping file id270190 NCBI fileEvidenceIEA
GeneEphb2Authority13844Mapping file id13844 NCBI fileEvidenceIEA
GeneEphb3Authority13845Mapping file id13845 NCBI fileEvidenceIEA
GeneEphb4Authority13846Mapping file id13846 NCBI fileEvidenceIEA
GeneEphb6Authority13848Mapping file id13848 NCBI fileEvidenceIEA
GeneErbb2Authority13866Mapping file id13866 NCBI fileEvidenceIEA
GeneEvlAuthority14026Mapping file id14026 NCBI fileEvidenceIEA
GeneEzrAuthority22350Mapping file id22350 NCBI fileEvidenceIEA
GeneFarp2Authority227377Mapping file id227377 NCBI fileEvidenceIEA
GeneFesAuthority14159Mapping file id14159 NCBI fileEvidenceIEA
GeneFgfr1Authority14182Mapping file id14182 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.