Which Firefox Version Is Currently in Nightly, Beta, Release, and ESR?

Updated

As of the snapshot on WhatTrainIsItNow.com, the four channels show Firefox 160 in Nightly, 159 in Beta, 158 in Release, and 153 / 115 ESR for the extended support line. The page also states that Firefox 159 ships on October 27 (in 6 days) and that the next merge day is October 22. These figures change as trains move, so treat them as the state shown on the site at the time you read it rather than fixed numbers.

Reading the channel labels

The site presents each channel as a short label, and the version number next to it is the build currently sitting in that channel.

Label on the page Channel What the number means
160 Nightly Nightly The version under active development, ahead of Beta
159 Beta Beta The version in stabilization testing, next to reach Release
158 Release Release The version most users are running
153 / 115 ESR ESR The extended support line, shown with two numbers

The ESR entry is the one that trips people up. It appears as 153 / 115 ESR, a paired label rather than a single version. Read it as the ESR line being tracked alongside its own version number, separate from the rapid-release channels. If you only need the mainstream channels, watch the Nightly, Beta, and Release rows; the ESR pair answers a different question about the long-support branch.

Where the dates fit

Two dates on the page tell you what happens next:

  • Firefox 159 ships on October 27 (in 6 days). This is the Release date for the version currently in Beta. When it lands, 159 moves from Beta to Release and 158 stops being the current Release.
  • Next merge day: October 22. Merge day is when Nightly content moves into Beta. After it, the Beta number advances and a new Nightly cycle begins.

The "in 6 days" phrasing is a countdown relative to when the page was captured. If you are reading later, recalculate from the stated date rather than trusting the day count.

How to use this to answer your own question

  1. Open the site and look at the four channel labels at the top.
  2. Match the number to the channel name beside it — Nightly, Beta, Release, or the ESR pair.
  3. Check the release date line to see when the Beta version becomes the Release version.
  4. Check the merge day line to see when Nightly rolls into Beta.

The expected result is a one-line answer: the version in each channel plus the two upcoming dates. A common snag is reading the ESR pair as a single version or assuming the countdown is always accurate; both need the caveat above.

What this does and does not tell you

The page tracks train positions and milestone dates. It does not tell you whether a specific feature has landed, what changed between versions, or which build you should install — for those, follow the linked Bug landings and crashes sections or the release notes for the version in question. Use the channel table when you need the current version per channel, and the dates when you need to know when the next shift happens.