CTSHND
Sapporo to Tokyo
Direct and one-stop flights from New Chitose Airport (CTS) to Tokyo Haneda International Airport (HND), 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 Sapporo to Tokyo.
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 Sapporo to Tokyo
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 Tokyo 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 40m
- Arrived on time
- 100%
- Flies
- Wed, Fri
- 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 37m 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 40m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 34m on average.
- Journey
- 1h 35m
- 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
- 1h 35m
- 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
- 1h 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 43m 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 38m 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 32m on average.
- Journey
- 1h 35m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 34m on average.
- Journey
- 1h 35m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 34m 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 40m 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 32m 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 41m 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 41m 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 47m 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 45m 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 39m 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 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 41m 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 30m 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 53m 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 35m 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 53m on average.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 23m 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 58m 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 54m 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 44m 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 46m 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 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 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 45m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 35m 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 42m on average.
- Journey
- 1h 45m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- Journey
- 1h 45m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- 6h 15m stopover in Bangkok · Two airlines: book on one ticket
What this means
A long wait at the airport in Bangkok. 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
- 19h 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 19h 28m on average.
- 6h 35m stopover in Bangkok
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
- Journey
- 20h 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 19h 43m on average.
- 7h 25m stopover in Bangkok
What this means
A long wait at the airport in Bangkok. Check whether you can stay airside or need to pass through immigration.
- Journey
- 20h 55m
- 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 43m on average.
- 1h 16m stopover in Fukuoka · 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 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 5h 21m on average.
- 1h 50m stopover in Fukuoka
- Journey
- 6h 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 6h 15m on average.
- 1h 50m stopover in Fukuoka · 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 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 6h 15m on average.
- 2h 15m stopover in Fukuoka
- Journey
- 6h 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 6h 47m on average.
- 3h 20m stopover in Fukuoka
- Journey
- 7h 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 7h 47m on average.
- 3h 20m stopover in Fukuoka · 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 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 7h 47m on average.
- 3h 40m stopover in Fukuoka · 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
- 8h 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 8h 15m on average.
- 4h 45m stopover in Fukuoka · 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
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 17m on average.
- 4h 45m stopover in Fukuoka
- Journey
- 9h 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 9h 17m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 52m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 1h 40m
- 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 40m
- 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 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 48m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 48m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 1h 45m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 56m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 06m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 06m on average.
- Journey
- 1h 40m
- 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
- 1h 45m
- 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 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 1h 45m
- 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
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 56m on average.
- Journey
- 1h 45m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 52m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 59m on average.
- Journey
- 1h 40m
- 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
- 1h 40m
- 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
- 1h 40m
- 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
- 1h 40m
- 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
- 1h 45m
- 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 40m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average; 1 cancelled.
- Journey
- 1h 40m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 59m on average.
- Journey
- 1h 40m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 00m on average.
- Journey
- 1h 45m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 19m on average.
- Journey
- 1h 35m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 04m on average.
- Journey
- 1h 35m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 04m on average.
- Journey
- 1h 45m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 20m on average.
- Journey
- 1h 40m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 17m on average.
- Journey
- 1h 40m
- Arrived on time
- 0%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 17m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Skymark Airlines BC706, BC710, BC712, BC714, BC716, BC720, BC726, BC730 | 8.1 | 81% | 3 of 16 | 0 | 19 min | No ratings yet | — |
| 2 | Japan Airlines JL500, JL502, JL504, JL506, JL508, JL510, JL512, JL514, JL516, JL518, JL520, JL522, JL524, JL526, JL528, JL530, JL590 · also sold as LH4891, PR3151, SQ5946, TK7656, VA7414 | 7.4 | 74% | 9 of 34 | 0 | 32 min | No ratings yet | — |
| 3 | All Nippon Airways NH1104, NH1106, NH4712, NH4714, NH4716, NH4718, NH4720, NH4724, NH4726, NH4728, NH4732, NH4736, NH4738, NH4744, NH50, NH52, NH54, NH56, NH58, NH60, NH62, NH64, NH66, NH68, NH70, NH74, NH76, NH78, NH82, NH84, NH988 · also sold as AC6258, AC6266, AI8014, AZ2804, LH4891, LH4913, PR3149, PR3151, SQ5946, TK7656, UA7969, UA7975, VA7414, VN3372 | 6.7 | 67% | 19 of 60 | 1 | 30 min | No ratings yet | — |
| 4 | Hokkaido International Airlines HD12, HD14, HD16, HD18, HD20, HD24, HD26, HD28, HD32, HD36, HD38, HD44, HD48 · also sold as UA7969, VN3372 | 5.7 | 57% | 10 of 23 | 0 | 34 min | No ratings yet | — |
| Spring Airlines Japan IJ410 | No score yet | 100% | 0 of 2 | 0 | — | 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 Sapporo to Tokyo?
Over the past 30 days, Skymark Airlines had the best record on this route, arriving on time on 81% of 16 flights.
Which airlines fly direct from Sapporo to Tokyo?
Skymark Airlines (BC706, BC710, BC712, BC714, BC716, BC720, BC726, BC730), Japan Airlines (JL500, JL502, JL504, JL506, JL508, JL510, JL512, JL514, JL516, JL518, JL520, JL522, JL524, JL526, JL528, JL530, JL590), All Nippon Airways (NH1104, NH1106, NH4712, NH4714, NH4716, NH4718, NH4720, NH4724, NH4726, NH4728, NH4732, NH4736, NH4738, NH4744, NH50, NH52, NH54, NH56, NH58, NH60, NH62, NH64, NH66, NH68, NH70, NH74, NH76, NH78, NH82, NH84, NH988), Hokkaido International Airlines (HD12, HD14, HD16, HD18, HD20, HD24, HD26, HD28, HD32, HD36, HD38, HD44, HD48), Spring Airlines Japan (IJ410).
How often are Hokkaido International Airlines flights from Sapporo to Tokyo late?
10 of 23 flights arrived more than 15 minutes late over the past 30 days. When late, the typical delay was 34 min.