BLRBOM
Bengaluru to Mumbai
Direct and one-stop flights from Kempegowda International Airport Bengaluru (BLR) to Chhatrapati Shivaji Maharaj International Airport (BOM), ranked by how reliably they actually get you there.
Our recommendation
Not enough flight history yet to recommend a journey
We don't have enough flight history yet to recommend a way to fly from Bengaluru to Mumbai.
Flexible on dates?
Pick a range of up to 14 days and we'll tell you the best day to fly, and the most reliable journey that actually operates on each date.
Every way to fly Bengaluru to Mumbai
Past 30 days. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Mumbai within 15 minutes of schedule; a missed connection counts as late.
Live prices aren't connected in this preview yet. When they are, each journey shows its lowest current fare for the date you pick. Prices never affect our recommendation.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 38m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 31m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 46m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 35m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 38m on average.
- Journey
- 2h 05m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 35m on average.
- Journey
- 1h 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 36m on average.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 27m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 39m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 04m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 57m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 54m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 08m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 22m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 54m on average.
- Journey
- 1h 58m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 55m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 12m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 42m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 50m on average.
- 2h 45m stopover in Amsterdam
- Journey
- 22h 05m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 22h 10m on average.
- 3h 30m stopover in Abu Dhabi
- Journey
- 10h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 10h 55m on average.
- 7h 15m stopover in Abu Dhabi
What this means
A long wait at the airport in Abu Dhabi. Check whether you can stay airside or need to pass through immigration.
- Journey
- 14h 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 14h 23m on average.
- 7h 05m stopover in Bangkok · Two airlines: book on one ticket
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 15h 35m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 15h 30m on average.
- 6h 10m stopover in Bangkok
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
- Journey
- 14h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 14h 40m on average.
- 7h 25m stopover in Bangkok · Two airlines: book on one ticket
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 15h 58m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 16h 02m on average.
- 3h 35m stopover in Bangkok · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 12h 15m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 12h 16m on average.
- 5h 20m stopover in Bangkok · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 14h 05m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 14h 05m on average.
- 6h 45m stopover in Bangkok · Two airlines: book on one ticket
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 15h 35m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 15h 30m on average.
- 6h 55m stopover in Bangkok · Two airlines: book on one ticket
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 15h 35m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 15h 24m on average.
- 6h 10m stopover in Kolkata
What this means
A long wait at the airport in Kolkata. Check whether you can stay airside or need to pass through immigration.
- Journey
- 12h 08m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 53m on average.
- 5h 00m stopover in Kolkata
- Journey
- 10h 48m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 10h 33m on average.
- Journey
- 2h 00m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average.
- Journey
- 1h 55m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 57m on average.
- Journey
- 1h 45m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 56m on average.
- Journey
- 2h 00m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 03m on average.
- Journey
- 2h 03m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 17m on average.
- Journey
- 2h 00m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 12m on average.
- Journey
- 2h 00m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 18m on average.
- Journey
- 2h 13m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 29m on average.
- Journey
- 2h 05m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 26m on average.
- Journey
- 2h 00m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 26m on average.
- Journey
- 2h 05m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 03m on average.
- Journey
- 2h 05m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 43m on average.
- Journey
- 1h 35m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 56m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | IndiGo Airlines 6E5031, 6E5051, 6E5069, 6E5082, 6E5089, 6E5094, 6E5205, 6E5216, 6E5218, 6E5255, 6E5256, 6E5351, 6E5376, 6E6189 | 8.3 | 83% | 4 of 23 | 0 | 22 min | No ratings yet | — |
| 2 | Air Kenya (Priv) QP1130, QP1132, QP1134, QP1136, QP1144, QP1150, QP1331, QP1333, QP1335, QP1366, QP1736, QP1986 | 8.3 | 83% | 2 of 12 | 0 | 18 min | No ratings yet | — |
| 3 | Air India Limited AI2402, AI2483, AI2604, AI2610, AI2622, AI2624, AI2630, AI2642, AI2811, AI2840, AI2846, AI2850, AI2852, AI2854, AI2858 | 6.5 | 65% | 6 of 17 | 0 | 37 min | No ratings yet | — |
| Air India Express IX1548 | No score yet | 0% | 1 of 1 | 0 | 21 min | No ratings yet | — | |
| Spicejet SG640 | No score yet | — | — | — | — | No ratings yet | — |
On-time record over time
Not enough flights yet to show a trend.
Questions travellers ask
Which airline is most on time from Bengaluru to Mumbai?
Over the past 30 days, IndiGo Airlines had the best record on this route, arriving on time on 83% of 23 flights.
Which airlines fly direct from Bengaluru to Mumbai?
IndiGo Airlines (6E5031, 6E5051, 6E5069, 6E5082, 6E5089, 6E5094, 6E5205, 6E5216, 6E5218, 6E5255, 6E5256, 6E5351, 6E5376, 6E6189), Air Kenya (Priv) (QP1130, QP1132, QP1134, QP1136, QP1144, QP1150, QP1331, QP1333, QP1335, QP1366, QP1736, QP1986), Air India Limited (AI2402, AI2483, AI2604, AI2610, AI2622, AI2624, AI2630, AI2642, AI2811, AI2840, AI2846, AI2850, AI2852, AI2854, AI2858), Air India Express (IX1548), Spicejet (SG640).
How often are Air India Limited flights from Bengaluru to Mumbai late?
6 of 17 flights arrived more than 15 minutes late over the past 30 days. When late, the typical delay was 37 min.