whattrainisitnow.com

A "Firefox train" is Mozilla's term for the scheduled release cadence that moves each Firefox version through three development channels — Nightly, Beta, and Release — on fixed dates. WhatTrainIsItNow.com is a lightweight dashboard that shows which version currently occupies each channel, plus the next merge day and ship date. It's useful if you want to know what's shipping next, when a version moves from Beta to Release, or which ESR line is current, without digging through Mozilla's wiki pages.

The three channels and how a version moves

Each Firefox version boards the train as a Nightly build, then moves one channel forward at each merge day:

• Nightly — the newest code, where a version starts. Features land here first and may still be removed.
• Beta — the version has been stabilized and is being tested by a wider audience before release.
• Release — the version ships to general users.

When Nightly moves to Beta, a new version number starts on Nightly. When Beta moves to Release, the previous Release version is retired. So at any moment, three consecutive version numbers are in flight at once.

The site's current snapshot shows this clearly:

The page also lists the next merge day (October 22) and the ship date for Firefox 159 (October 27, "in 6 days"), which is the Beta-to-Release step for that version.

Reading the numbers

The version numbers are sequential, and the gap between them is always two: if Release is 158, Beta is 159 and Nightly is 160. This lets you sanity-check the page — if the numbers don't line up that way, the snapshot is stale or mid-merge. The "in 6 days" countdown is relative to when the page was generated, so treat it as a rough indicator rather than a live clock.

What ESR means on the train

ESR (Extended Support Release) is a separate track that does not follow the same rapid cadence. It's a version pinned for organizations that need a longer support window and slower change. On the site it appears as its own line — currently "153 / 115" — meaning an ESR branch based on Firefox 153 alongside the older 115 ESR line. ESR versions do not advance with every merge day; they receive security and stability fixes on their own schedule.

If you're deciding which channel to follow: Nightly is for testing and early feedback, Beta for pre-release verification, Release for normal use, and ESR for environments that value stability over new features.

How to use the site for a practical question

Say you need to know whether a fix you're tracking will reach regular users soon. Check which channel it landed in, then count the merge days:

1. Open the site and note the version in the channel where the fix exists.
2. If it's in Nightly, it needs two merge days to reach Release (Nightly → Beta → Release).
3. If it's in Beta, it needs one merge day.
4. Cross-check the listed "Next merge day" and ship date to estimate timing.

The site also links to bug landings and crash data per channel ("Bug landings and crashes — In Nightly / In Beta / In Release"), which is the place to confirm whether a specific change is actually present in a given build.

Common points of confusion

• "Train" is not a product. It's the release process, not a separate Firefox edition.
• The countdown is a snapshot. "Ships on October 27 (in 6 days)" reflects the page's generation time; verify against the calendar if the date matters.
• ESR numbers don't fit the 158/159/160 pattern. The ESR line is intentionally offset and should be read on its own.
• Merge day and ship day are different events. Merge day moves a version to the next channel; ship day is when the Release build goes out. The page lists both, and they're usually a few days apart.

WhatTrainIsItNow.com is a lightweight dashboard that tracks which Firefox "train" is currently in each release channel. On a single page it shows the current Nightly, Beta, Release, and ESR version numbers, plus the next ship date and merge day. It's useful if you follow Firefox development, need to know what version is about to ship, or want to confirm which channel a given version belongs to. It is a community-style tracker, not an official Mozilla product unless the site itself says otherwise.

What the site tracks

The page is organized around the four Firefox release channels and the milestones that move versions between them.

From the site's own snapshot, the channels read 153 / 115 ESR, 158 Release, 159 Beta, and 160 Nightly, with Firefox 159 shipping on October 27 (in 6 days) and the next merge day on October 22. That single line is the core value: you can see the whole pipeline at a glance.

How to read the numbers

Firefox development runs on a train model. A version starts in Nightly, moves to Beta after a merge day, and then ships as Release. ESR runs on a slower, separate cadence, which is why it shows a much lower number (115 in the snapshot) than the main channels.

A concrete example: if the site shows 160 Nightly and 159 Beta, then version 160 is still under active development, 159 is in beta testing, and 158 is what most users currently have. The "next merge day" date tells you when 160 will move to Beta and 159 will move toward Release.

When it's useful

• Checking what's about to ship — the ship date answers "when does the next Firefox come out?"
• Confirming channel versions — useful when a bug report or add-on compatibility note references a specific version.
• Following the train schedule — merge days and ship dates give you the rhythm of the release cycle.
• ESR reference — organizations on ESR can confirm the current ESR line.

Limits to keep in mind

The site is a convenience tracker. Dates can shift, and the page reflects what its maintainers have entered, so treat ship dates and merge days as scheduled rather than guaranteed. For authoritative release information, cross-check Mozilla's own release channels. The site does not state pricing or login requirements, so don't assume any particular access model beyond what you see when you visit.

Quick way to use it

1. Open whattrainisitnow.com.
2. Read the four channel numbers to see the current Nightly, Beta, Release, and ESR versions.
3. Check the ship date for the next Release and the merge day for the next channel move.
4. Use the calendar and "About Firefox Trains" links if you need the fuller schedule or background.

That's the whole workflow — one page, one glance, and you know where Firefox is in its release cycle.

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.

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.

The Bug landings and crashes sections on WhatTrainIsItNow.com are channel-level health signals for the Firefox train. They show how many bugs have landed in Nightly, Beta, and Release, and they surface crash information for each channel. The page presents these as separate views — “In Nightly,” “In Beta,” and “In Release” — so you can compare activity across the train rather than reading a single combined number. Use them to judge whether a channel is absorbing change normally or showing signs of instability; do not treat them as a release blocker list or a formal quality gate.

What each section tracks

The site’s navigation lists Bug landings and crashes alongside In Nightly, In Beta, and In Release, which tells you the data is organized by channel first and by signal second.

The two signals answer different questions. Landings tell you how much is changing; crashes tell you how well the channel is holding up while that change happens. A channel with heavy landings and flat crash numbers is behaving differently from one with heavy landings and rising crashes.

Why the numbers move so often

Firefox development runs on a fixed train schedule, and the site states the current positions directly: 153 / 115 ESR, 158 Release, 159 Beta, and 160 Nightly, with Firefox 159 shipping on October 27 (in 6 days) and the next merge day on October 22.

That schedule explains the churn. Landings accumulate continuously on Nightly, and merge day moves a whole set of changes from one channel to the next. Around a merge or a ship date, expect the landings figures to shift sharply and the channel labels to advance. Crash data can also update frequently because it reflects incoming reports rather than a fixed snapshot.

A practical example: if you check the page a few days before October 22, Nightly landings may look busy while Beta is comparatively quiet. After the merge, that pattern flips — Beta picks up the changes Nightly was carrying. Reading the numbers without the dates above will make normal train movement look like an anomaly.

How these signals relate to train health

Treat the sections as a quick triage view, not a verdict:

• Landings concentrated in Nightly is the expected state; Nightly is where change is supposed to land first.
• Landings in Beta or Release deserve more attention, because those channels are closer to users.
• Crash information that worsens on a channel after a merge is the pattern worth noticing — it suggests the incoming changes need scrutiny before the next step.
• Quiet landings with stable crashes on Release is the healthy baseline.

The site does not publish thresholds, pass/fail criteria, or a definition of what counts as an unhealthy crash level in the material available, so avoid reading any specific number as a cutoff. The value is in the comparison across channels and across the dates shown on the page.

Using the sections in practice

1. Open the page and note the current channel versions and the two dates — the ship date and the next merge day.
2. Check In Nightly, In Beta, and In Release under Bug landings and crashes to see where activity sits.
3. Compare against the schedule: activity near a merge day or ship date is expected; activity far from either is worth a closer look.
4. Re-check after the merge day to confirm the expected shift actually happened.

Common sticking points: the figures update frequently, so a number you saw yesterday may not match today; and the page tracks train-level signals, not individual bugs, so it will not tell you which bug landed or why a crash appeared. For that detail you need the linked bug and crash views the site points to, not the summary counts.

According to the current snapshot on WhatTrainIsItNow.com, Firefox 159 ships on October 27 (in 6 days), and the next merge day is October 22. Those two dates are the ones to plan around if you track Firefox trains: the merge day moves Nightly into the Beta slot, and the ship date is when the Beta build becomes the Release version. Because train dates can shift, treat these as the latest published values and re-check the site before you rely on them for a deadline.

What the site currently shows

The homepage presents the active trains as a set of version numbers, each tied to a channel:

The page also states the two key dates directly: Firefox 159 ships on October 27 (in 6 days) and Next merge day: October 22. The "in 6 days" phrasing is relative to when the page was generated, so the countdown is a convenience, not a fixed fact — the absolute dates are the reliable part.

How release and merge day fit together

Firefox development runs on a "train" model: work moves through channels on a schedule rather than shipping whenever a feature is ready. The two dates on the site mark the handoffs in that pipeline.

• Merge day (October 22) is when the next version is promoted into Beta. In practice, the Nightly train (160) becomes the new Beta, and a fresh Nightly cycle begins. This is the point where feature work stops landing freely and stabilization starts.
• Ship date (October 27) is when the Beta train (159) is released as the new stable version, replacing 158 in the Release channel.

So the sequence is: merge on the 22nd, ship on the 27th. If you maintain add-ons, run a QA process, or write documentation, merge day is your signal that the API surface is settling, and the ship date is when users actually receive it.

Using the calendar for milestones

The site includes a Calendar section alongside the train overview, intended for following major milestones rather than just the current version numbers. Use it when you need dates beyond the immediate release — for example, to find when a future train is scheduled to merge or ship so you can plan testing windows or content updates.

A practical workflow:

1. Check the homepage for the current channel-to-version mapping and the next two dates.
2. Open the Calendar to confirm whether a later milestone you care about is already listed.
3. Note the absolute dates (not the "in N days" countdown) in your own tracker.
4. Re-check a few days before the merge day, since schedules can move.

Why you should re-check before relying on a date

The site itself frames these as dates that can change, and that is the right posture. Merge and ship dates are planned targets; a delayed merge or a held release will move them, and the countdown on the page will update accordingly. If a date matters to a deadline — a compatibility test, a support article, a training session — confirm it on the site close to the event rather than planning months out from a single reading.

For the broader picture of what each channel and version number represents, see the related explainers on what a Firefox train is and which version sits in each channel.