OD390 Batik Air Malaysia - Flight Status

Which is the frequency of flight OD390?
The flight OD390 is scheduled to flight on Monday, Tuesday, Thursday, Saturday on a weekly basis.

Which is the distance of flight OD390?
The distance between the two airports is 1129 kilometers.

Are the departure airport and arrival airport at the same Time Zone?
No, each airport is in a different timezone. The times shown above, are presented in the local time of each respective airport.
Current Time in Kuala Lumpur: 2025-11-04 11:27:03
Current Time in Jakarta: 2025-11-04 10:27:03

The following airlines serves the same route between Kuala Lumpur and Jakarta:

AirAsia
- Flight Number: AK351. (On Time performance: 53 - Average Delay: 33 minutes)
- Flight Number: AK353. (On Time performance: 34 - Average Delay: 79 minutes)
- Flight Number: AK380. (On Time performance: 93 - Average Delay: 4 minutes)
- Flight Number: AK384. (On Time performance: 37 - Average Delay: 58 minutes)
- Flight Number: AK386. (On Time performance: 28 - Average Delay: 81 minutes)

Citilink
- Flight Number: QG503. (On Time performance: 96 - Average Delay: 3 minutes)

Garuda Indonesia
- Flight Number: GA821. (On Time performance: 90 - Average Delay: 6 minutes)

Batik Air
- Flight Number: ID7283. (On Time performance: 57 - Average Delay: 24 minutes)

KLM Royal Dutch Airlines
- Flight Number: KL809. (On Time performance: 89 - Average Delay: 5 minutes)

Malaysia Airlines
- Flight Number: MH711. (On Time performance: 70 - Average Delay: 11 minutes)
- Flight Number: MH713. (On Time performance: 80 - Average Delay: 8 minutes)
- Flight Number: MH717. (On Time performance: 80 - Average Delay: 9 minutes)
- Flight Number: MH721. (On Time performance: 88 - Average Delay: 9 minutes)
- Flight Number: MH723. (On Time performance: 89 - Average Delay: 5 minutes)
- Flight Number: MH725. (On Time performance: 67 - Average Delay: 12 minutes)
- Flight Number: MH727. (On Time performance: 82 - Average Delay: 8 minutes)

Batik Air Malaysia
- Flight Number: OD310. (On Time performance: 88 - Average Delay: 8 minutes)
- Flight Number: OD312. (On Time performance: 72 - Average Delay: 31 minutes)
- Flight Number: OD316. (On Time performance: 84 - Average Delay: 14 minutes)
- Flight Number: OD320. (On Time performance: 91 - Average Delay: 7 minutes)
- Flight Number: OD328. (On Time performance: 86 - Average Delay: 44 minutes)
- Flight Number: OD346. (On Time performance: 77 - Average Delay: 20 minutes)
- Flight Number: OD348. (On Time performance: 67 - Average Delay: 24 minutes)
- Flight Number: OD380. (On Time performance: 100 - Average Delay: 2 minutes)
- Flight Number: OD382. (On Time performance: 100 - Average Delay: -60 minutes)
- Flight Number: OD386. (On Time performance: 75 - Average Delay: 11 minutes)
- Flight Number: OD388. (On Time performance: 63 - Average Delay: 15 minutes)
- Flight Number: OD392. (On Time performance: 75 - Average Delay: 31 minutes)
- Flight Number: OD396. (On Time performance: 83 - Average Delay: -14 minutes)

Indonesia AirAsia
- Flight Number: QZ201. (On Time performance: 73 - Average Delay: 17 minutes)
- Flight Number: QZ203. (On Time performance: 89 - Average Delay: 18 minutes)
- Flight Number: QZ205. (On Time performance: 43 - Average Delay: 74 minutes)
- Flight Number: QZ211.

TransNusa
- Flight Number: 8B674. (On Time performance: 28 - Average Delay: 70 minutes)
- Flight Number: 8B676. (On Time performance: 61 - Average Delay: 20 minutes)
- Flight Number: 8B680. (On Time performance: 29 - Average Delay: 99 minutes)

It is not possible to calculate the On-Time Performance for this flight accurately due to insufficient or non-representative data, as doing so could lead to misleading conclusions.

Delays analyzed by Week: It is not possible to calculate the On-Time Performance for this flight accurately by weekday due to insufficient or non-representative data, as doing so could lead to misleading conclusions
Delays analyzed by Month: It is not possible to calculate the On-Time Performance for this flight accurately by month due to insufficient or non-representative data, as doing so could lead to misleading conclusions