CGKDPS
Jakarta to Kuta
Direct and one-stop flights from Soekarno-Hatta International Airport (CGK) to Denpasar I Gusti Ngurah Rai International Airport (DPS), 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 Jakarta to Kuta.
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 Jakarta to Kuta
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 Kuta 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 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 43m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 45m on average.
- Journey
- 9h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 52m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 35m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 43m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 45m 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 41m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 42m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 49m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 37m on average.
- Journey
- 1h 44m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 27m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 41m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 39m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 54m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 49m 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 2h 01m 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 56m on average.
- Journey
- 2h 08m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 11m 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 47m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 37m 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 07m 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 52m 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 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 48m 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 2h 00m 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 2h 00m 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 44m 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 48m 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 2h 01m 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 51m on average.
- Journey
- 1h 36m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 36m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 54m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- 2h 10m 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
- 9h 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 9h 44m on average.
- Journey
- 21h 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 21h 45m on average.
- 3h 40m stopover in Hong Kong
- Journey
- 13h 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 13h 18m on average.
- 3h 10m stopover in Hong Kong · 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
- 13h 10m
- 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 48m on average.
- 4h 45m stopover in Sepang
- Journey
- 10h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 10h 08m on average.
- 4h 15m stopover in Sepang · 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
- 9h 25m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 9h 33m on average.
- 7h 50m stopover in Sepang
What this means
A long wait at the airport in Sepang. Check whether you can stay airside or need to pass through immigration.
- Journey
- 13h 00m
- 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 13h 04m on average.
- 7h 20m stopover in Sepang · Two airlines: book on one ticket
What this means
A long wait at the airport in Sepang. 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
- 12h 25m
- 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 29m on average.
- 7h 55m stopover in Sepang · Two airlines: book on one ticket
What this means
A long wait at the airport in Sepang. 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
- 13h 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 51m on average.
- 5h 38m stopover in Sepang · 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
- 11h 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 10h 44m on average.
- 6h 25m stopover in Sepang · Two airlines: book on one ticket
What this means
A long wait at the airport in Sepang. 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
- 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 55m on average.
- 6h 50m stopover in Sepang
What this means
A long wait at the airport in Sepang. Check whether you can stay airside or need to pass through immigration.
- 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 02m on average.
- Journey
- 1h 50m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 55m 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 58m 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 02m on average.
- Journey
- 2h 10m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 14m 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 2h 03m on average.
- Journey
- 1h 50m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 07m on average.
- Journey
- 1h 50m
- Arrived on time
- 0%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 45m on average.
- Journey
- 2h 40m
- Arrived on time
- 0%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; 1 cancelled.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Island Spirit IP102, IP104, IP106, IP108, IP112 | 10.0 | 100% | 0 of 10 | 0 | — | No ratings yet | — |
| 2 | Citilink Indonesia QG662, QG680, QG682, QG684, QG686, QG688, QG9660 | 10.0 | 100% | 0 of 13 | 0 | — | No ratings yet | — |
| 3 | Indonesia AirAsia QZ802, QZ806, QZ808, QZ814, QZ818, QZ820 | 9.2 | 92% | 1 of 12 | 0 | 28 min | No ratings yet | — |
| 4 | Garuda Indonesia GA402, GA404, GA406, GA410, GA414, GA420, GA422, GA424, GA426, GA428, GA652 | 8.1 | 81% | 3 of 21 | 1 | 20 min | No ratings yet | — |
| 5 | Lion Mentari Airlines JT12, JT20, JT22, JT24, JT30, JT34 | 5.0 | 50% | 0 of 12 | 6 | — | No ratings yet | — |
| BusinessAir 8B5104, 8B5106, 8B5108, 8B5110 | No score yet | 57% | 2 of 7 | 1 | 24 min | No ratings yet | — | |
| Interlink Airlines ID6050, ID6508 | No score yet | 100% | 0 of 4 | 0 | — | No ratings yet | — | |
| MAT Macedonian Airlines IN280, IN7272 | No score yet | 50% | 1 of 2 | 0 | 55 min | No ratings yet | — | |
| Sriwijaya Air SJ272 | No score yet | 0% | 0 of 2 | 2 | — | 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 Jakarta to Kuta?
Over the past 30 days, Island Spirit had the best record on this route, arriving on time on 100% of 10 flights.
Which airlines fly direct from Jakarta to Kuta?
Island Spirit (IP102, IP104, IP106, IP108, IP112), Citilink Indonesia (QG662, QG680, QG682, QG684, QG686, QG688, QG9660), Indonesia AirAsia (QZ802, QZ806, QZ808, QZ814, QZ818, QZ820), Garuda Indonesia (GA402, GA404, GA406, GA410, GA414, GA420, GA422, GA424, GA426, GA428, GA652), Lion Mentari Airlines (JT12, JT20, JT22, JT24, JT30, JT34), BusinessAir (8B5104, 8B5106, 8B5108, 8B5110), Interlink Airlines (ID6050, ID6508), MAT Macedonian Airlines (IN280, IN7272), Sriwijaya Air (SJ272).
How often are Lion Mentari Airlines flights from Jakarta to Kuta late?
0 of 12 flights arrived more than 15 minutes late over the past 30 days. When late, the typical delay was —.