GOX → BLRMopa to Bengaluru

live

Direct flights from Mopa (GOX) to Bengaluru (BLR): 7 nonstop departures observed each week across 1 airline. 80% of the last 20 operated flights arrived within 15 minutes of schedule. The median arrival is on schedule. No cancellations were recorded across the 20 tracked flights. The nonstop covers 500 km, an estimated 1 hour 8 minutes in the air. Measured by Pro Flight Search from live flight boards at Mopa and Bengaluru. Updated 20 October 2026 at 10:38 UTC.

Today, GOX → BLR

Tue 20 Oct · local times
  1. · 6E6298IndiGo On schedule BLR est. 14:05sched 14:20
  2. · 6E6527IndiGo On schedule BLR est. 14:55sched 15:15
  3. · 6E6584IndiGo Departed Landed 08:04 −1

Checked BLR board 16:08

GOX Mopa tracking
BLR Bengaluru smooth · +0
500 km · ~1h 08m est.
dep bank 08:05–15:157x weekly
Runs reliable · 1 airline · 7x weekly · nonstop
80% on time

of the last 20 operated GOX → BLR flights arrived within 15 minutes

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

Median arrival+0 minacross the last 20 operated legs
Flight time~1h 08mestimated from route distance
Weekly departures7x1 direct airline on the leg
Cancelled0.0%recent route rate · 0 of 20

The week

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

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
IndiGo6E80% on time

Flights 6E6584 08:05 daily · 6E6298 14:20 Mo Tu Th Fr Sa Su · 6E6527 15:15 Mo Tu Th Fr Sa Su

History

operated legs · board outcomes
10-206E6584arrived−1
10-196E6298arrived+26
10-196E6527arrived−15
10-196E6584arrived+32
10-186E6298arrived−18
10-186E6527arrived−37
10-186E6584arrived+26
10-176E6298arrived−26
10-176E6527arrived−16
10-176E6584arrived+39
10-166E6298arrived−5
10-166E6527arrived−24
10-166E6584arrived+0
10-156E6298arrived+0
10-156E6527arrived+0
10-156E6584arrived+0
10-146E6584arrived+0
10-136E6298arrived+0
10-136E6527arrived+0
10-136E6584arrived+0

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
GOXMopa tracking Full GOX delay board →
BLRBengaluru +0 min smooth Full BLR delay board →

How the Mopa to Bengaluru route actually runs

Pro Flight Search records official board updates for nonstop GOX to BLR 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 — Mopa (GOX) to Bengaluru (BLR) route reliability, measured from operated flights on official airport boards.

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

GOX to BLR questions

Is GOX–BLR 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 GOX to BLR?

Great-circle distance is 500 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 65–73 min gate-to-gate on this route.

How often does GOX–BLR fly?

IndiGo runs the route with about 19 flights a week (daily). Since one carrier owns the route, a single disruption tends to ripple through the day.

What does the route health score measure?

A blend of departure-side delay at GOX and arrival-side delay at BLR, 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.