sensors Mode-S transponder
868DB5
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA771F · BOEING 777-200LR
- Hex
- 868DB5
- Octal
- 41506665
- Decimal
- 8,818,101
- Country
- JP
- Tail
- JA771F
- Type
- B77L
- Flights observed
- 81
- Distinct callsigns
- 12
- Country
- JP
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 868DB5 falls within the block assigned to Japan (JP) by ICAO Annex 10, Volume III. Every aircraft registered in Japan receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ANA8401 | All Nippon Airways | 22 | 2026-05-27 |
| ANA8402 | All Nippon Airways | 13 | 2026-05-27 |
| ANA8422 | All Nippon Airways | 11 | 2026-05-30 |
| ANA8421 | All Nippon Airways | 10 | 2026-05-18 |
| ANA8403 | All Nippon Airways | 9 | 2026-05-29 |
| ANA8404 | All Nippon Airways | 4 | 2026-05-28 |
| ANA8408 | All Nippon Airways | 3 | 2026-05-16 |
| ANA8407 | All Nippon Airways | 3 | 2026-05-16 |
| ANA8418 | All Nippon Airways | 2 | 2026-05-19 |
| ANA8417 | All Nippon Airways | 2 | 2026-05-19 |
| ANA8531 | All Nippon Airways | 1 | 2026-05-25 |
| ANA840D | - | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | ANA8422 | NRT → ORD | May 30, 00:35 UTC | May 30, 01:00 UTC | 25m |
| 2026-05-29 | ANA8403 | NRT → PVG | May 29, 13:10 UTC | May 29, 21:15 UTC | 8h 5m |
| 2026-05-28 | ANA8404 | PVG → NRT | May 28, 12:55 UTC | May 28, 21:05 UTC | 8h 10m |
| 2026-05-27 | ANA8401 | ORD → NRT | May 27, 20:25 UTC | May 28, 09:05 UTC | 12h 40m |
| 2026-05-27 | ANA8402 | NRT → ORD | May 27, 05:55 UTC | May 27, 17:10 UTC | 11h 16m |
| 2026-05-26 | ANA840D | - | May 26, 13:10 UTC | May 26, 21:09 UTC | 8h 0m |
| 2026-05-25 | ANA8531 | ORD → NRT | May 25, 20:34 UTC | May 26, 08:39 UTC | 12h 5m |
| 2026-05-21 | ANA8422 | NRT → ORD | May 21, 01:10 UTC | May 21, 12:00 UTC | 10h 50m |
| 2026-05-20 | ANA8404 | PVG → NRT | May 20, 13:50 UTC | May 20, 21:40 UTC | 7h 50m |
| 2026-05-19 | ANA8417 | NRT → OKA | May 19, 18:10 UTC | May 20, 05:25 UTC | 11h 16m |
| 2026-05-19 | ANA8418 | OKA → NRT | May 19, 06:35 UTC | May 19, 15:50 UTC | 9h 15m |
| 2026-05-18 | ANA8421 | ORD → NRT | May 18, 14:55 UTC | May 19, 04:10 UTC | 13h 14m |
| 2026-05-18 | ANA8422 | NRT → ORD | May 18, 00:35 UTC | May 18, 11:55 UTC | 11h 20m |
| 2026-05-16 | ANA8407 | LAX → NRT | May 16, 23:35 UTC | May 17, 10:55 UTC | 11h 20m |
| 2026-05-16 | ANA8408 | NRT → LAX | May 16, 11:35 UTC | May 16, 20:40 UTC | 9h 5m |
| 2026-05-15 | ANA8401 | ORD → NRT | May 15, 20:35 UTC | May 16, 08:55 UTC | 12h 21m |
| 2026-05-15 | ANA8402 | NRT → ORD | May 15, 05:45 UTC | May 15, 17:35 UTC | 11h 49m |
| 2026-05-10 | ANA8407 | LAX → NRT | May 10, 00:05 UTC | May 10, 11:20 UTC | 11h 15m |
| 2026-05-09 | ANA8408 | NRT → LAX | May 9, 12:40 UTC | May 9, 21:40 UTC | 9h 0m |
| 2026-05-08 | ANA8401 | ORD → NRT | May 8, 20:50 UTC | May 9, 09:50 UTC | 13h 0m |
| 2026-05-08 | ANA8402 | NRT → ORD | May 8, 05:59 UTC | May 8, 16:55 UTC | 10h 55m |
| 2026-05-07 | ANA8403 | NRT → PVG | May 7, 12:55 UTC | May 7, 21:20 UTC | 8h 25m |
| 2026-05-06 | ANA8401 | ORD → NRT | May 6, 21:05 UTC | May 7, 10:00 UTC | 12h 55m |
| 2026-05-06 | ANA8402 | NRT → ORD | May 6, 06:25 UTC | May 6, 17:25 UTC | 11h 0m |
| 2026-05-05 | ANA8421 | ORD → NRT | May 5, 14:45 UTC | May 6, 03:35 UTC | 12h 50m |
| 2026-05-05 | ANA8422 | NRT → ORD | May 5, 00:20 UTC | May 5, 11:05 UTC | 10h 45m |
| 2026-05-03 | ANA8401 | ORD → NRT | May 3, 21:10 UTC | May 4, 10:30 UTC | 13h 20m |
| 2026-05-03 | ANA8402 | NRT → ORD | May 3, 06:10 UTC | May 3, 17:10 UTC | 11h 0m |
| 2026-05-02 | ANA8421 | ORD → NRT | May 2, 14:40 UTC | May 3, 03:40 UTC | 12h 59m |
| 2026-05-02 | ANA8422 | NRT → ORD | May 2, 00:20 UTC | May 2, 11:30 UTC | 11h 10m |
| 2026-05-01 | ANA8403 | NRT → PVG | May 1, 13:05 UTC | May 1, 21:05 UTC | 8h 0m |
| 2026-04-30 | ANA8403 | NRT → PVG | Apr 30, 13:10 UTC | Apr 30, 21:50 UTC | 8h 40m |
| 2026-04-29 | ANA8401 | ORD → NRT | Apr 29, 20:10 UTC | Apr 30, 08:55 UTC | 12h 44m |
| 2026-04-29 | ANA8402 | NRT → ORD | Apr 29, 06:05 UTC | Apr 29, 17:01 UTC | 10h 56m |
| 2026-04-28 | ANA8421 | ORD → NRT | Apr 28, 14:20 UTC | Apr 29, 03:04 UTC | 12h 45m |
| 2026-04-28 | ANA8422 | NRT → ORD | Apr 28, 00:05 UTC | Apr 28, 11:10 UTC | 11h 5m |
| 2026-04-27 | ANA8403 | NRT → PVG | Apr 27, 13:10 UTC | Apr 27, 21:10 UTC | 8h 0m |
| 2026-04-26 | ANA8401 | ORD → NRT | Apr 26, 20:10 UTC | Apr 27, 08:50 UTC | 12h 40m |
| 2026-04-26 | ANA8402 | NRT → ORD | Apr 26, 05:50 UTC | Apr 26, 16:55 UTC | 11h 5m |
| 2026-04-25 | ANA8421 | ORD → NRT | Apr 25, 14:15 UTC | Apr 26, 02:35 UTC | 12h 20m |
| 2026-04-25 | ANA8422 | NRT → ORD | Apr 25, 00:20 UTC | Apr 25, 11:35 UTC | 11h 15m |
| 2026-04-24 | ANA8403 | NRT → PVG | Apr 24, 13:20 UTC | Apr 24, 21:10 UTC | 7h 50m |
| 2026-04-23 | ANA8403 | NRT → PVG | Apr 23, 13:45 UTC | Apr 23, 22:00 UTC | 8h 15m |
| 2026-04-22 | ANA8401 | ORD → NRT | Apr 22, 22:20 UTC | Apr 23, 11:01 UTC | 12h 41m |
| 2026-04-22 | ANA8402 | NRT → ORD | Apr 22, 08:10 UTC | Apr 22, 19:15 UTC | 11h 5m |
| 2026-04-21 | ANA8417 | NRT → OKA | Apr 21, 18:25 UTC | Apr 22, 05:30 UTC | 11h 5m |
| 2026-04-21 | ANA8418 | OKA → NRT | Apr 21, 06:35 UTC | Apr 21, 15:51 UTC | 9h 15m |
| 2026-04-20 | ANA8421 | ORD → NRT | Apr 20, 14:55 UTC | Apr 21, 04:05 UTC | 13h 10m |
| 2026-04-20 | ANA8422 | NRT → ORD | Apr 20, 00:15 UTC | Apr 20, 11:20 UTC | 11h 5m |
| 2026-04-19 | ANA8407 | LAX → NRT | Apr 19, 00:45 UTC | Apr 19, 11:40 UTC | 10h 55m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the JA771F page for operator, model, and routing details .