Skip to content

Create an account and get up to 25% off.

Order

Pathway Rat Rattus norvegicus

Read this first

Every rat pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

RNA Polymerase II Transcription

R-RNO-73857 in Reactome release 97: under Gene expression (Transcription), with 811 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-73857 (human), R-MMU-73857 (mouse). 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 rat 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 rat pathway

The mapping files place 811 genes in this rat pathway; showing 301 to 400, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this rat pathway, page 4 of 9
GeneLOC120097423Authority120097423Mapping file idENSRNOG00000076585 Ensembl fileEvidenceIEA
GeneLOC120101823Authority120101823Mapping file idENSRNOG00000083310 Ensembl fileEvidenceIEA
GeneLOC120103152Authority120103152Mapping file idENSRNOG00000034161 Ensembl fileEvidenceIEA
GeneLOC134478826Authority134478826Mapping file id134478826 NCBI fileEvidenceIEA
GeneLOC147995116Authority147995116Mapping file idENSRNOG00000067648 Ensembl fileEvidenceIEA
GeneLOC148000144Authority148000144Mapping file idENSRNOG00000065263 Ensembl fileEvidenceIEA
GeneLOC148000145Authority148000145Mapping file idENSRNOG00000066835 Ensembl fileEvidenceIEA
GeneLOC148000146Authority148000146Mapping file idENSRNOG00000070513 Ensembl fileEvidenceIEA
GeneLOC148000156Authority148000156Mapping file idENSRNOG00000064755 Ensembl fileEvidenceIEA
GeneLOC148004154Authority148004154Mapping file idENSRNOG00000018816 Ensembl fileEvidenceIEA
GeneLOC148004472Authority148004472Mapping file idENSRNOG00000064392 Ensembl fileEvidenceIEA
GeneLsm10Authority366468Mapping file id366468 NCBI fileEvidenceIEA
GeneLsm11Authority501688Mapping file id501688 NCBI fileEvidenceIEA
GeneMaged1Authority84469Mapping file id84469 NCBI fileEvidenceIEA
GeneMaml1Authority303101Mapping file id303101 NCBI fileEvidenceIEA
GeneMaml2Authority689844Mapping file id689844 NCBI fileEvidenceIEA
GeneMaml3Authority310405Mapping file id310405 NCBI fileEvidenceIEA
GeneMap2k6Authority114495Mapping file id114495 NCBI fileEvidenceIEA
GeneMapk1Authority116590Mapping file id116590 NCBI fileEvidenceIEA
GeneMapk11Authority689314Mapping file idENSRNOG00000006984 Ensembl fileEvidenceIEA
GeneMapk3Authority50689Mapping file id50689 NCBI fileEvidenceIEA
GeneMapkap1Authority296648Mapping file id296648 NCBI fileEvidenceIEA
GeneMapkapk5Authority498183Mapping file idENSRNOG00000001345 Ensembl fileEvidenceIEA
GeneMaxAuthority60661Mapping file id60661 NCBI fileEvidenceIEA
GeneMbd3Authority362834Mapping file id362834 NCBI fileEvidenceIEA
GeneMdm2Authority314856Mapping file idENSRNOG00000006304 Ensembl fileEvidenceIEA
GeneMdm4Authority304798Mapping file id304798 NCBI fileEvidenceIEA
GeneMeaf6Authority362594Mapping file idENSRNOG00000009309 Ensembl fileEvidenceIEA
GeneMecp2Authority29386Mapping file id29386 NCBI fileEvidenceIEA
GeneMed1Authority497991Mapping file id497991 NCBI fileEvidenceIEA
GeneMen1Authority29417Mapping file id29417 NCBI fileEvidenceIEA
GeneMgaAuthority499874Mapping file id499874 NCBI fileEvidenceIEA
GeneMllt1Authority301119Mapping file id301119 NCBI fileEvidenceIEA
GeneMllt3Authority114510Mapping file id114510 NCBI fileEvidenceIEA
GeneMlst8Authority64226Mapping file id64226 NCBI fileEvidenceIEA
GeneMnat1Authority266713Mapping file id266713 NCBI fileEvidenceIEA
GeneMre11Authority64046Mapping file id64046 NCBI fileEvidenceIEA
GeneMta2Authority361724Mapping file id361724 NCBI fileEvidenceIEA
GeneMtorAuthority56718Mapping file id56718 NCBI fileEvidenceIEA
GeneMycAuthority24577Mapping file id24577 NCBI fileEvidenceIEA
GeneNabp1Authority363227Mapping file id363227 NCBI fileEvidenceIEA
GeneNabp2Authority362813Mapping file id362813 NCBI fileEvidenceIEA
GeneNbnAuthority85482Mapping file id85482 NCBI fileEvidenceIEA
GeneNcbp1Authority298075Mapping file id298075 NCBI fileEvidenceIEA
GeneNcbp2Authority689116Mapping file id689116 NCBI fileEvidenceIEA
GeneNcor2Authority360801Mapping file idENSRNOG00000001004 Ensembl fileEvidenceIEA
GeneNek4Authority306252Mapping file idENSRNOG00000017997 Ensembl fileEvidenceIEA
GeneNelfaAuthority305455Mapping file id305455 NCBI fileEvidenceIEA
GeneNelfbAuthority311796Mapping file id311796 NCBI fileEvidenceIEA
GeneNelfcdAuthority679203Mapping file id679203 NCBI fileEvidenceIEA
GeneNelfeAuthority294258Mapping file idENSRNOG00000000420 Ensembl fileEvidenceIEA
GeneNoc2lAuthority313777Mapping file id313777 NCBI fileEvidenceIEA
GeneNotch3Authority56761Mapping file id56761 NCBI fileEvidenceIEA
GeneNotch4Authority406162Mapping file idENSRNOG00000000442 Ensembl fileEvidenceIEA
GeneNpas4Authority266734Mapping file id266734 NCBI fileEvidenceIEA
GeneNpm1Authority25498Mapping file id25498 NCBI fileEvidenceIEA
GeneNr0b1Authority58850Mapping file id58850 NCBI fileEvidenceIEA
GeneNr0b2Authority117274Mapping file id117274 NCBI fileEvidenceIEA
GeneNr1d1Authority252917Mapping file id252917 NCBI fileEvidenceIEA
GeneNr1d2Authority259241Mapping file id259241 NCBI fileEvidenceIEA
GeneNr1h2Authority58851Mapping file id58851 NCBI fileEvidenceIEA
GeneNr1h3Authority58852Mapping file idENSRNOG00000013172 Ensembl fileEvidenceIEA
GeneNr1h4Authority60351Mapping file id60351 NCBI fileEvidenceIEA
GeneNr1i2Authority84385Mapping file id84385 NCBI fileEvidenceIEA
GeneNr1i3Authority65035Mapping file id65035 NCBI fileEvidenceIEA
GeneNr2c1Authority252924Mapping file id252924 NCBI fileEvidenceIEA
GeneNr2c2Authority50659Mapping file id50659 NCBI fileEvidenceIEA
GeneNr2e1Authority684085Mapping file idENSRNOG00000050550 Ensembl fileEvidenceIEA
GeneNr2e3Authority100365683Mapping file id100365683 NCBI fileEvidenceIEA
GeneNr2f1Authority81808Mapping file id81808 NCBI fileEvidenceIEA
GeneNr2f6Authority245980Mapping file id245980 NCBI fileEvidenceIEA
GeneNr3c1Authority24413Mapping file id24413 NCBI fileEvidenceIEA
GeneNr3c2Authority25672Mapping file id25672 NCBI fileEvidenceIEA
GeneNr4a1Authority79240Mapping file id79240 NCBI fileEvidenceIEA
GeneNr4a2Authority54278Mapping file id54278 NCBI fileEvidenceIEA
GeneNr4a3Authority58853Mapping file id58853 NCBI fileEvidenceIEA
GeneNr5a1Authority83826Mapping file id83826 NCBI fileEvidenceIEA
GeneNr5a2Authority60349Mapping file id60349 NCBI fileEvidenceIEA
GeneNr6a1Authority362125Mapping file idENSRNOG00000013232 Ensembl fileEvidenceIEA
GeneNrbf2Authority58839Mapping file id58839 NCBI fileEvidenceIEA
GeneNrbf2l1Authority499670Mapping file idENSRNOG00000030494 Ensembl fileEvidenceIEA
GeneNuak1Authority299694Mapping file id299694 NCBI fileEvidenceIEA
GeneNudt21Authority291877Mapping file id291877 NCBI fileEvidenceIEA
GeneOscp1Authority362595Mapping file idENSRNOG00000026978 Ensembl fileEvidenceIEA
GenePabpn1Authority116697Mapping file id116697 NCBI fileEvidenceIEA
GenePaf1Authority361531Mapping file id361531 NCBI fileEvidenceIEA
GenePapolaAuthority314417Mapping file id314417 NCBI fileEvidenceIEA
GeneParp1Authority25591Mapping file id25591 NCBI fileEvidenceIEA
GenePax5Authority500453Mapping file id500453 NCBI fileEvidenceIEA
GenePbrm1Authority306254Mapping file idENSRNOG00000028227 Ensembl fileEvidenceIEA
GenePcf11Authority361605Mapping file idENSRNOG00000009891 Ensembl fileEvidenceIEA
GenePcgf2Authority287662Mapping file id287662 NCBI fileEvidenceIEA
GenePcgf5Authority681178Mapping file id681178 NCBI fileEvidenceIEA
GenePcgf6Authority309457Mapping file id309457 NCBI fileEvidenceIEA
GenePcnaAuthority25737Mapping file id25737 NCBI fileEvidenceIEA
GenePdpk1Authority81745Mapping file id81745 NCBI fileEvidenceIEA
GenePgrAuthority25154Mapping file id25154 NCBI fileEvidenceIEA
GenePhaxAuthority286917Mapping file id286917 NCBI fileEvidenceIEA
GenePhc1Authority312690Mapping file idENSRNOG00000015191 Ensembl fileEvidenceIEA
GenePhc2Authority313038Mapping file id313038 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 64,140 rat pairs both place.

  • Reactome mapping files, the rat 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 rat 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.