DPSCGK
Kuta to Jakarta
Direct and one-stop flights from Denpasar I Gusti Ngurah Rai International Airport (DPS) to Soekarno-Hatta International Airport (CGK), 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 Kuta to Jakarta.
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 Kuta to Jakarta
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 Jakarta 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
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 40m 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 48m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 37m on average.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 42m on average.
- Journey
- 1h 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 33m 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 29m 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 43m 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 49m 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 31m 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 46m 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 40m on average.
- Journey
- 2h 10m
- 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 45m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 45m 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 58m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 54m 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 39m on average.
- Journey
- 2h 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 53m 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 59m 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 41m 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 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 57m 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 00m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 35m on average.
- Journey
- 1h 43m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 36m 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 40m on average.
- Journey
- 1h 40m
- 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 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 42m on average.
- Journey
- 2h 10m
- 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
- 2h 00m
- 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
- 2h 00m
- 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
- 2h 00m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 50m 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 24m 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 41m 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 41m 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 38m 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 39m 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 35m on average.
- 2h 00m stopover in Abu Dhabi
- Journey
- 19h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 19h 41m on average.
- Journey
- 21h 50m
- 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 51m on average.
- Journey
- 21h 20m
- 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 14m on average.
- Journey
- 22h 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 22h 23m on average.
- Journey
- 20h 50m
- 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 20h 55m on average.
- 2h 40m 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
- 12h 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 12h 34m on average.
- 5h 50m 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
- 16h 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 15h 37m on average.
- 2h 25m stopover in Seoul · 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
- 16h 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 16h 33m on average.
- Journey
- 16h 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 15h 48m on average.
- 1h 50m 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
- 7h 05m
- 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 6h 57m on average.
- Journey
- 8h 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 7h 58m on average.
- 4h 00m 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 30m
- 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 04m on average.
- Journey
- 2h 05m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 04m on average.
- Journey
- 1h 33m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 55m on average.
- Journey
- -11h -55m
- Arrived on time
- 0%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- Journey
- 1h 40m
- Arrived on time
- 0%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 09m on average.
- Journey
- 0h 50m
- 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 | Citilink Indonesia QG663, QG667, QG681, QG685, QG687, QG689, QG9661 | 10.0 | 100% | 0 of 14 | 0 | — | No ratings yet | — |
| 2 | Indonesia AirAsia QZ803, QZ807, QZ809, QZ811, QZ815, QZ819, QZ821 | 10.0 | 100% | 0 of 14 | 0 | — | No ratings yet | — |
| 3 | Garuda Indonesia GA401, GA403, GA407, GA409, GA411, GA413, GA415, GA417, GA419, GA421, GA427, GA653 | 9.6 | 96% | 1 of 22 | 0 | 18 min | No ratings yet | — |
| 4 | Pelita Air IP103, IP105, IP107, IP109, IP113 | 9.1 | 91% | 1 of 11 | 0 | 40 min | No ratings yet | — |
| TransNusa 8B5101, 8B5105, 8B5107, 8B5109 | No score yet | 88% | 1 of 8 | 0 | 29 min | No ratings yet | — | |
| Batik Air ID6509, ID6517 | No score yet | 100% | 0 of 4 | 0 | — | No ratings yet | — | |
| Nam Air IN281, IN283, IN7273 | No score yet | 100% | 0 of 1 | 0 | — | No ratings yet | — | |
| Lion Mentari Airlines JT15, JT21, JT31, JT35 | No score yet | 86% | 1 of 7 | 0 | 12h 50m | No ratings yet | — | |
| Sriwijaya Air SJ273 | No score yet | 0% | 0 of 1 | 1 | — | 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 Kuta to Jakarta?
Over the past 30 days, Citilink Indonesia had the best record on this route, arriving on time on 100% of 14 flights.
Which airlines fly direct from Kuta to Jakarta?
Citilink Indonesia (QG663, QG667, QG681, QG685, QG687, QG689, QG9661), Indonesia AirAsia (QZ803, QZ807, QZ809, QZ811, QZ815, QZ819, QZ821), Garuda Indonesia (GA401, GA403, GA407, GA409, GA411, GA413, GA415, GA417, GA419, GA421, GA427, GA653), Pelita Air (IP103, IP105, IP107, IP109, IP113), TransNusa (8B5101, 8B5105, 8B5107, 8B5109), Batik Air (ID6509, ID6517), Nam Air (IN281, IN283, IN7273), Lion Mentari Airlines (JT15, JT21, JT31, JT35), Sriwijaya Air (SJ273).
How often are Pelita Air flights from Kuta to Jakarta late?
1 of 11 flights arrived more than 15 minutes late over the past 30 days. When late, the typical delay was 40 min.