HNDITM
Tokyo to Osaka
Direct and one-stop flights from Tokyo Haneda International Airport (HND) to Osaka Itami International Airport (ITM), 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 Tokyo to Osaka.
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 Tokyo to Osaka
Past week. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Osaka 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 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 07m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 12m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 17m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 13m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 12m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 14m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 06m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 14m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 09m on average.
- Journey
- 1h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 11m on average.
- Journey
- 1h 20m
- 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 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 39m on average.
- 1h 38m stopover in Sapporo · 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
- 5h 14m
- 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 5h 16m on average.
- 2h 08m stopover in Sapporo · 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
- 5h 44m
- 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 5h 44m on average.
- 1h 05m stopover in Sapporo
- Journey
- 4h 35m
- 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 4h 35m on average.
- 4h 18m stopover in Sapporo · 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 54m
- 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 7h 48m on average.
- 3h 15m stopover in Sapporo · 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
- 6h 45m
- 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 6h 39m on average.
- 6h 23m stopover in Sapporo · Two airlines: book on one ticket
What this means
A long wait at the airport in Sapporo. 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
- 10h 04m
- 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 05m on average.
- 5h 20m stopover in Sapporo
- Journey
- 8h 55m
- 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 8h 56m on average.
- 6h 53m stopover in Sapporo · Two airlines: book on one ticket
What this means
A long wait at the airport in Sapporo. 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
- 10h 29m
- 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 30m on average.
- 5h 50m stopover in Sapporo · 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 20m
- 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 21m on average.
- 7h 15m stopover in Sapporo · Two airlines: book on one ticket
What this means
A long wait at the airport in Sapporo. 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
- 10h 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 10h 47m on average.
- 7h 10m stopover in Sapporo
What this means
A long wait at the airport in Sapporo. Check whether you can stay airside or need to pass through immigration.
- Journey
- 10h 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 10h 42m on average.
- 7h 35m stopover in Sapporo
What this means
A long wait at the airport in Sapporo. Check whether you can stay airside or need to pass through immigration.
- Journey
- 11h 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 11h 03m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 25m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 24m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 16m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 22m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 18m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 30m on average.
- Journey
- 1h 10m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 32m on average.
- Journey
- 1h 10m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 24m on average.
- Journey
- 1h 10m
- Arrived on time
- 33%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 21m on average.
- Journey
- 1h 10m
- Arrived on time
- 33%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 32m on average.
- Journey
- 1h 10m
- Arrived on time
- 33%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 31m on average.
- Journey
- 1h 10m
- Arrived on time
- 33%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 28m on average.
- Journey
- 1h 10m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 37m on average.
- Journey
- 1h 10m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 33m on average.
- Journey
- 1h 10m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 31m on average.
- Journey
- 1h 15m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 22m on average.
- Journey
- 1h 20m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | ANA NH13, NH15, NH17, NH19, NH21, NH23, NH27, NH31, NH33, NH35, NH37, NH39, NH41, NH985 | 7.5 | 75% | 9 of 36 | 0 | 28 min | No ratings yet | — |
| 2 | Japan Airlines JL101, JL103, JL107, JL111, JL113, JL115, JL117, JL119, JL121, JL125, JL127, JL131, JL133, JL137, JL139 | 5.5 | 55% | 17 of 38 | 0 | 33 min | No ratings yet | — |
On-time record over time
- Japan Airlines
- ANA
Show as a table
| Day | Japan Airlines | ANA |
|---|---|---|
| 18 Nov | 53.3% (15) | 92.9% (14) |
| 19 Nov | 53.3% (15) | 78.6% (14) |
| 20 Nov | 62.5% (8) | 37.5% (8) |
Questions travellers ask
Which airline is most on time from Tokyo to Osaka?
Over the past week, ANA had the best record on this route, arriving on time on 75% of 36 flights.
Which airlines fly direct from Tokyo to Osaka?
ANA (NH13, NH15, NH17, NH19, NH21, NH23, NH27, NH31, NH33, NH35, NH37, NH39, NH41, NH985), Japan Airlines (JL101, JL103, JL107, JL111, JL113, JL115, JL117, JL119, JL121, JL125, JL127, JL131, JL133, JL137, JL139).
How often are Japan Airlines flights from Tokyo to Osaka late?
17 of 38 flights arrived more than 15 minutes late over the past week. When late, the typical delay was 33 min.