GAU → BOMGuwahati to Mumbai

live

Direct flights from Guwahati (GAU) to Mumbai (BOM): 21 nonstop departures observed each week across 2 airlines. 86% of the last 22 tracked flights arrived within 15 minutes of schedule. The median arrival is 8 minutes early. No cancellations were recorded across the 22 tracked flights. The nonstop covers 2,071 km, an estimated 3 hours 9 minutes in the air. Measured by Pro Flight Search from live flight boards at Guwahati and Mumbai. Updated 20 November 2026 at 06:18 UTC.

Today, GAU → BOM

Fri 20 Nov · local times
  1. · 6E6342INDIGO Departed Landed 11:26 −19
  2. · QP1142Akasa Air On schedule BOM 22:25scheduled

Checked BOM board 11:48

GAU Guwahati tracking
BOM Mumbai smooth · +0
2,071 km · ~3h 09m est.
dep bank 11:45–22:2521x weekly
Runs reliable · 2 airlines · 21x weekly · nonstop
86% on time

of the last 22 tracked GAU → BOM flights arrived within 15 minutes

Median arrival delay is −8 min. 0 of 22 tracked legs cancelled in the sample. Will a delayed flight be cancelled? →

Median arrival−8 minacross the last 22 arrivals
Flight time~3h 09mestimated from route distance
Weekly departures21x2 direct airlines on the leg
Cancelled0.0%recent route rate · 0 of 22

The week

scheduled departures · origin local time
06121824
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Akasa AirIndiGo

Each mark is a scheduled departure at its origin-local time, observed operating in the last 7 days. Today is highlighted.

Who flies it

observed on the boards · 7 days
Akasa AirQP86% on time

Flights QP1142 22:25 daily

IndiGo6E87% on time

Flights 6E6342 11:45 daily · 6E6224 21:10 daily

History

operated legs · board outcomes
11-206E6342arrived−19
11-196E6224arrived−7
11-196E6342arrived−17
11-19QP1142arrived+3
11-186E6224arrived−20
11-186E6342arrived−31
11-18QP1142arrived−9
11-176E6224arrived−2
11-176E6342arrived−8
11-17QP1142arrived−8
11-166E6224arrived−11
11-166E6342arrived−5
11-16QP1142arrived+51
11-156E6224arrived+20
11-156E6342arrived−29
11-15QP1142arrived−39
11-146E6224arrived−716
11-146E6342arrived−38
11-14QP1142arrived+12
11-136E6224arrived−8
11-136E6342arrived+173
11-13QP1142arrived−23

Actual board outcomes rather than schedules, paired departure and arrival per flight and day.

Full board history, day by day →

Airports right now

live boards
GAUGuwahati tracking Full GAU delay board →
BOMMumbai +0 min smooth Full BOM delay board →

How the Guwahati to Mumbai route actually runs

Pro Flight Search records official board updates for nonstop GAU to BOM flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: Guwahati (GAU) to Mumbai (BOM) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/GAU-BOM
How we measure this →

GAU to BOM questions

Is GAU–BOM running on time right now?

Smooth skies ahead. Both endpoints currently score the same, route health score 100/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from GAU to BOM?

Great-circle distance is 2,071 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 176–208 min gate-to-gate on this route.

How often does GAU–BOM fly?

2 carriers operate this route, around 21 flights a week between them. Compare carrier days and times in the airline list above.

What does the route health score measure?

A blend of departure-side delay at GAU and arrival-side delay at BOM, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.