sensors Mode-S transponder
86D668
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA827J · BOEING 787-8 Dreamliner
- Hex
- 86D668
- Octal
- 41553150
- Decimal
- 8,836,712
- Country
- JP
- Tail
- JA827J
- Type
- B788
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- JP
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 86D668 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TZP26 | ZIPAIR | 14 | 2026-05-16 |
| TZP25 | ZIPAIR | 14 | 2026-05-17 |
| TZP54 | ZIPAIR | 8 | 2026-05-26 |
| TZP53 | ZIPAIR | 5 | 2026-05-26 |
| TZP24 | ZIPAIR | 4 | 2026-05-19 |
| TZP23 | ZIPAIR | 3 | 2026-05-19 |
| TZP16 | ZIPAIR | 3 | 2026-05-27 |
| TZP15 | ZIPAIR | 3 | 2026-05-27 |
| TZP52 | ZIPAIR | 2 | 2026-05-06 |
| TZP51 | ZIPAIR | 2 | 2026-05-06 |
| TZP46 | ZIPAIR | 2 | 2026-05-07 |
| TZP45 | ZIPAIR | 2 | 2026-05-07 |
| TZP44 | ZIPAIR | 2 | 2026-04-15 |
| TZP43 | ZIPAIR | 2 | 2026-04-15 |
| TZP34 | ZIPAIR | 2 | 2026-05-28 |
| TZP33 | ZIPAIR | 2 | 2026-05-28 |
| TZP30 | ZIPAIR | 2 | 2026-05-21 |
| TZP29 | ZIPAIR | 2 | 2026-05-21 |
| TZP22 | ZIPAIR | 2 | 2026-05-30 |
| TZP21 | ZIPAIR | 2 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | TZP21 | YVR → NRT | May 30, 17:45 UTC | May 30, 20:00 UTC | 2h 15m |
| 2026-05-30 | TZP22 | NRT → YVR | May 30, 07:15 UTC | May 30, 15:10 UTC | 7h 55m |
| 2026-05-28 | TZP33 | LAX → NRT | May 28, 23:15 UTC | May 29, 10:20 UTC | 11h 5m |
| 2026-05-28 | TZP34 | NRT → LAX | May 28, 11:15 UTC | May 28, 20:35 UTC | 9h 20m |
| 2026-05-27 | TZP15 | IAH → NRT | May 27, 16:10 UTC | May 28, 04:50 UTC | 12h 40m |
| 2026-05-27 | TZP16 | NRT → IAH | May 27, 01:49 UTC | May 27, 13:35 UTC | 11h 46m |
| 2026-05-26 | TZP54 | SIN → NRT | May 26, 19:45 UTC | May 26, 23:25 UTC | 3h 40m |
| 2026-05-26 | TZP54 | SIN → NRT | May 26, 16:55 UTC | May 26, 17:05 UTC | 10m |
| 2026-05-26 | TZP53 | NRT → SIN | May 26, 08:39 UTC | May 26, 12:00 UTC | 3h 20m |
| 2026-05-25 | TZP15 | IAH → NRT | May 25, 15:55 UTC | May 26, 04:24 UTC | 12h 29m |
| 2026-05-25 | TZP16 | NRT → IAH | May 25, 02:00 UTC | May 25, 13:20 UTC | 11h 20m |
| 2026-05-24 | TZP54 | SIN → NRT | May 24, 23:00 UTC | May 24, 23:10 UTC | 10m |
| 2026-05-24 | TZP54 | SIN → NRT | May 24, 19:45 UTC | May 24, 20:20 UTC | 35m |
| 2026-05-24 | TZP53 | NRT → SIN | May 24, 08:20 UTC | May 24, 14:25 UTC | 6h 5m |
| 2026-05-22 | TZP54 | SIN → NRT | May 22, 19:25 UTC | May 22, 23:05 UTC | 3h 40m |
| 2026-05-22 | TZP53 | NRT → SIN | May 22, 08:10 UTC | May 22, 12:10 UTC | 4h 0m |
| 2026-05-21 | TZP29 | SJC → NRT | May 21, 19:15 UTC | May 22, 06:15 UTC | 11h 0m |
| 2026-05-21 | TZP30 | NRT → SJC | May 21, 07:45 UTC | May 21, 16:25 UTC | 8h 40m |
| 2026-05-20 | TZP29 | SJC → NRT | May 20, 19:10 UTC | May 21, 05:30 UTC | 10h 20m |
| 2026-05-20 | TZP30 | NRT → SJC | May 20, 07:50 UTC | May 20, 16:25 UTC | 8h 35m |
| 2026-05-19 | TZP23 | LAX → NRT | May 19, 17:50 UTC | May 20, 04:55 UTC | 11h 6m |
| 2026-05-19 | TZP24 | NRT → LAX | May 19, 05:55 UTC | May 19, 15:10 UTC | 9h 15m |
| 2026-05-18 | TZP21 | YVR → NRT | May 18, 18:00 UTC | May 19, 03:30 UTC | 9h 29m |
| 2026-05-18 | TZP22 | NRT → YVR | May 18, 07:30 UTC | May 18, 15:25 UTC | 7h 55m |
| 2026-05-17 | TZP25 | SFO → NRT | May 17, 00:45 UTC | May 17, 11:10 UTC | 10h 26m |
| 2026-05-16 | TZP26 | NRT → SFO | May 16, 12:50 UTC | May 16, 21:30 UTC | 8h 40m |
| 2026-05-15 | TZP23 | LAX → NRT | May 15, 17:45 UTC | May 16, 05:00 UTC | 11h 15m |
| 2026-05-15 | TZP24 | NRT → LAX | May 15, 05:55 UTC | May 15, 15:15 UTC | 9h 19m |
| 2026-05-14 | TZP1 | HNL → NRT | May 14, 20:00 UTC | May 15, 03:35 UTC | 7h 35m |
| 2026-05-14 | TZP2 | - | May 14, 16:55 UTC | May 14, 17:15 UTC | 20m |
| 2026-05-14 | TZP2 | - | May 14, 10:35 UTC | May 14, 11:10 UTC | 35m |
| 2026-05-13 | TZP25 | SFO → NRT | May 13, 00:40 UTC | May 13, 10:30 UTC | 9h 50m |
| 2026-05-12 | TZP26 | NRT → SFO | May 12, 12:40 UTC | May 12, 21:20 UTC | 8h 40m |
| 2026-05-12 | TZP25 | SFO → NRT | May 12, 05:00 UTC | May 12, 10:20 UTC | 5h 20m |
| 2026-05-11 | TZP26 | NRT → SFO | May 11, 12:40 UTC | May 11, 21:15 UTC | 8h 35m |
| 2026-05-11 | TZP25 | SFO → NRT | May 11, 00:34 UTC | May 11, 10:40 UTC | 10h 5m |
| 2026-05-10 | TZP26 | NRT → SFO | May 10, 12:49 UTC | May 10, 21:30 UTC | 8h 40m |
| 2026-05-10 | TZP25 | SFO → NRT | May 10, 00:39 UTC | May 10, 11:05 UTC | 10h 25m |
| 2026-05-09 | TZP26 | NRT → SFO | May 9, 12:55 UTC | May 9, 21:25 UTC | 8h 30m |
| 2026-05-09 | TZP25 | SFO → NRT | May 9, 00:20 UTC | May 9, 11:10 UTC | 10h 50m |
| 2026-05-08 | TZP26 | NRT → SFO | May 8, 12:34 UTC | May 8, 21:15 UTC | 8h 40m |
| 2026-05-07 | TZP33 | LAX → NRT | May 7, 22:59 UTC | May 8, 09:49 UTC | 10h 50m |
| 2026-05-07 | TZP34 | NRT → LAX | May 7, 11:15 UTC | May 7, 20:35 UTC | 9h 20m |
| 2026-05-07 | TZP46 | ICN → NRT | May 7, 04:15 UTC | May 7, 06:10 UTC | 1h 55m |
| 2026-05-07 | TZP45 | NRT → ICN | May 7, 00:20 UTC | May 7, 02:15 UTC | 1h 55m |
| 2026-05-06 | TZP52 | BKK → NRT | May 6, 16:30 UTC | May 6, 22:05 UTC | 5h 34m |
| 2026-05-06 | TZP51 | NRT → BKK | May 6, 08:20 UTC | May 6, 14:25 UTC | 6h 5m |
| 2026-05-06 | TZP46 | ICN → NRT | May 6, 04:35 UTC | May 6, 06:25 UTC | 1h 50m |
| 2026-05-06 | TZP45 | NRT → ICN | May 6, 00:50 UTC | May 6, 03:00 UTC | 2h 10m |
| 2026-05-05 | TZP52 | BKK → NRT | May 5, 17:45 UTC | May 5, 23:10 UTC | 5h 25m |
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 JA827J page for operator, model, and routing details .