RPR → BOMRaipur to Mumbai

live

Direct flights from Raipur (RPR) to Mumbai (BOM): 21 nonstop departures observed each week across 1 airline. 78% of the last 23 tracked flights arrived within 15 minutes of schedule. The median arrival is 9 minutes early. 1 of the 23 tracked flights was cancelled. The nonstop covers 955 km, an estimated 1 hour 43 minutes in the air. Measured by Pro Flight Search from live flight boards at Raipur and Mumbai. Updated 14 November 2026 at 04:53 UTC.

Today, RPR → BOM

Sat 14 Nov · local times
  1. · 6E2730INDIGO On schedule BOM 20:00scheduled
  2. · 6E594INDIGO Departed Landed 09:51 −29

Checked BOM board 10:23

RPR Raipur tracking
BOM Mumbai smooth · +0
955 km · ~1h 43m est.
dep bank 00:10–20:0021x weekly
Runs mixed · 1 airline · 21x weekly · nonstop
78% on time

of the last 23 tracked RPR → BOM flights arrived within 15 minutes

Median arrival delay is −9 min. 1 of 23 tracked legs cancelled in the sample. Will a delayed flight be cancelled? →

Median arrival−9 minacross the last 22 arrivals
Flight time~1h 43mestimated from route distance
Weekly departures21x1 direct airline on the leg
Cancelled4.3%recent route rate · 1 of 23

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

Flights 6E5062 00:10 daily · 6E594 08:25 daily · 6E2730 20:00 daily

History

operated legs · board outcomes
11-146E594arrived−29
11-136E2730arrived+19
11-136E5062arrived+3
11-136E594arrived−17
11-126E2730arrived+35
11-126E5062arrived−17
11-126E594arrived−3
11-116E2730arrived+12
11-116E5062arrived−17
11-116E594arrived−21
11-106E2730arrived+8
11-106E5062arrived+2
11-106E594arrived−9
11-096E2730arrived−4
11-096E5062arrived−22
11-096E594arrived−12
11-086E2730arrived−22
11-086E5062cancelledCNX
11-086E594arrived−17
11-076E2730arrived+42
11-076E5062arrived+21
11-076E594arrived−11
11-066E5062arrived−12

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
RPRRaipur tracking Full RPR delay board →
BOMMumbai +0 min smooth Full BOM delay board →

How the Raipur to Mumbai route actually runs

Pro Flight Search records official board updates for nonstop RPR 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: Raipur (RPR) to Mumbai (BOM) route reliability, measured from operated flights on official airport boards.

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

RPR to BOM questions

Is RPR–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 RPR to BOM?

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

How often does RPR–BOM fly?

IndiGo runs the route with about 21 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 RPR 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.