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