HLP → DPSJakarta to Kuta

live

Direct flights from Jakarta (HLP) to Kuta (DPS): 23 nonstop departures observed each week across 2 airlines. 80% of the last 20 tracked flights arrived within 15 minutes of schedule. The median arrival is 8 minutes early. No cancellations were recorded across the 20 tracked flights. The nonstop covers 954 km, an estimated 1 hour 43 minutes in the air. Measured by Pro Flight Search from live flight boards at Jakarta and Kuta. Updated 31 October 2026 at 04:53 UTC.

Today, HLP → DPS

Sat 31 Oct · local times
  1. · ID7309Batik Air On schedule DPS est. 13:26sched 13:40
  2. · QG194Citilink On schedule DPS 20:00scheduled

Checked DPS board 12:53

HLP Jakarta tracking
DPS Kuta smooth · +0
954 km · ~1h 43m est.
dep bank 09:55–20:0023x weekly
Runs reliable · 2 airlines · 23x weekly · nonstop
80% on time

of the last 20 tracked HLP → DPS flights arrived within 15 minutes

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

Median arrival−8 minacross the last 20 arrivals
Flight time~1h 43mestimated from route distance
Weekly departures23x2 direct airlines 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
Batik AirCitilink

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
Batik AirID91% on time

Flights ID7309 13:40 daily · ID7311 18:40 daily

CitilinkQG71% on time

Flights QG196 09:55 Mo We Fr Su · QG194 20:00 Mo Th Fr Sa Su

History

operated legs · board outcomes
10-30ID7309arrived−7
10-30ID7311arrived+18
10-30QG194arrived−12
10-30QG196arrived−24
10-29ID7309arrived+4
10-29SPRN02arrived+37
10-28ID7309arrived−23
10-28ID7311arrived−12
10-28QG196arrived−23
10-27ID7309arrived−13
10-26A34007arrived+2
10-26ID7309arrived−18
10-26ID7311arrived+0
10-26QG194arrived−19
10-26QG196arrived−29
10-25ID7309arrived−8
10-25ID7311arrived+1
10-25QG194arrived+23
10-25QG196arrived+27
10-24ID7309arrived−21

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
HLPJakarta tracking Full HLP delay board →
DPSKuta +0 min smooth ⛅ mostly cloudy · SSE 16 kt Full DPS delay board →

How the Jakarta to Kuta route actually runs

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

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

HLP to DPS questions

Is HLP–DPS 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 HLP to DPS?

Great-circle distance is 954 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 HLP–DPS fly?

2 carriers operate this route, around 23 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 HLP and arrival-side delay at DPS, 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.