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