sensors Mode-S transponder
86E4DA
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA868J · BOEING 787-9 Dreamliner
- Hex
- 86E4DA
- Octal
- 41562332
- Decimal
- 8,840,410
- Country
- JP
- Tail
- JA868J
- Type
- B789
- Flights observed
- 160
- Distinct callsigns
- 20
- Country
- JP
- Last broadcast
- 5m ago
Current position
Country allocation
The ICAO 24-bit address 86E4DA 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 |
|---|---|---|---|
| JAL8 | - | 21 | 2026-07-06 |
| JAL7 | - | 20 | 2026-07-07 |
| JAL58 | - | 16 | 2026-07-10 |
| JAL57 | - | 15 | 2026-07-10 |
| JAL407 | - | 11 | 2026-07-14 |
| JAL17 | - | 11 | 2026-07-08 |
| JAL18 | - | 10 | 2026-07-08 |
| JAL408 | - | 9 | 2026-07-12 |
| JAL66 | - | 6 | 2026-06-23 |
| JAL65 | - | 6 | 2026-06-23 |
| JAL062 | - | 6 | 2026-07-09 |
| JAL061 | - | 6 | 2026-07-09 |
| JAL68 | - | 5 | 2026-06-28 |
| JAL67 | - | 5 | 2026-06-28 |
| JAL754 | Japan Airlines | 4 | 2026-06-22 |
| JAL8782 | Japan Airlines | 2 | 2026-04-30 |
| JAL8663 | Japan Airlines | 2 | 2026-05-26 |
| JAL753 | - | 2 | 2026-06-22 |
| JAL8664 | Japan Airlines | 1 | 2026-05-26 |
| JAL8124 | Japan Airlines | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JAL407 | - | Jul 14, 02:00 UTC | Jul 14, 14:30 UTC | 12h 30m |
| 2026-07-12 | JAL408 | - | Jul 12, 18:40 UTC | Jul 13, 06:50 UTC | 12h 10m |
| 2026-07-12 | JAL407 | NRT → FRA | Jul 12, 01:55 UTC | Jul 12, 15:25 UTC | 13h 30m |
| 2026-07-10 | JAL57 | - | Jul 10, 21:30 UTC | Jul 11, 07:20 UTC | 9h 50m |
| 2026-07-10 | JAL58 | NRT → SFO | Jul 10, 10:00 UTC | Jul 10, 19:05 UTC | 9h 5m |
| 2026-07-09 | JAL061 | - | Jul 9, 21:25 UTC | Jul 10, 07:45 UTC | 10h 20m |
| 2026-07-09 | JAL062 | - | Jul 9, 08:50 UTC | Jul 9, 18:25 UTC | 9h 35m |
| 2026-07-08 | JAL17 | - | Jul 8, 21:30 UTC | Jul 9, 06:35 UTC | 9h 5m |
| 2026-07-08 | JAL18 | NRT → YVR | Jul 8, 10:35 UTC | Jul 8, 18:35 UTC | 8h 0m |
| 2026-07-07 | JAL7 | - | Jul 7, 17:55 UTC | Jul 8, 06:30 UTC | 12h 35m |
| 2026-07-06 | JAL8 | NRT → BOS | Jul 6, 10:05 UTC | Jul 6, 22:05 UTC | 12h 0m |
| 2026-07-05 | JAL57 | - | Jul 5, 21:40 UTC | Jul 6, 07:40 UTC | 10h 0m |
| 2026-07-05 | JAL58 | NRT → SFO | Jul 5, 09:40 UTC | Jul 5, 18:40 UTC | 9h 0m |
| 2026-07-02 | JAL57 | - | Jul 2, 21:50 UTC | Jul 3, 08:00 UTC | 10h 10m |
| 2026-07-02 | JAL58 | NRT → SFO | Jul 2, 09:45 UTC | Jul 2, 18:15 UTC | 8h 30m |
| 2026-07-01 | JAL17 | - | Jul 1, 21:10 UTC | Jul 2, 06:41 UTC | 9h 31m |
| 2026-07-01 | JAL18 | NRT → YVR | Jul 1, 10:25 UTC | Jul 1, 18:20 UTC | 7h 55m |
| 2026-06-30 | JAL57 | - | Jun 30, 21:05 UTC | Jul 1, 07:20 UTC | 10h 15m |
| 2026-06-30 | JAL58 | - | Jun 30, 10:00 UTC | Jun 30, 18:35 UTC | 8h 35m |
| 2026-06-29 | JAL061 | - | Jun 29, 20:40 UTC | Jun 30, 07:30 UTC | 10h 51m |
| 2026-06-29 | JAL062 | - | Jun 29, 08:54 UTC | Jun 29, 17:55 UTC | 9h 0m |
| 2026-06-28 | JAL67 | SEA → NRT | Jun 28, 20:39 UTC | Jun 29, 06:24 UTC | 9h 45m |
| 2026-06-28 | JAL68 | NRT → SEA | Jun 28, 09:39 UTC | Jun 28, 17:39 UTC | 8h 0m |
| 2026-06-27 | JAL7 | - | Jun 27, 17:44 UTC | Jun 28, 07:05 UTC | 13h 20m |
| 2026-06-26 | JAL8 | NRT → BOS | Jun 26, 10:39 UTC | Jun 26, 22:34 UTC | 11h 55m |
| 2026-06-24 | JAL57 | - | Jun 24, 20:54 UTC | Jun 25, 07:19 UTC | 10h 25m |
| 2026-06-24 | JAL58 | NRT → SFO | Jun 24, 09:45 UTC | Jun 24, 18:20 UTC | 8h 35m |
| 2026-06-23 | JAL65 | - | Jun 23, 20:29 UTC | Jun 24, 07:24 UTC | 10h 55m |
| 2026-06-23 | JAL66 | NRT → SAN | Jun 23, 08:39 UTC | Jun 23, 17:54 UTC | 9h 15m |
| 2026-06-22 | JAL754 | BLR → NRT | Jun 22, 23:55 UTC | Jun 23, 05:39 UTC | 5h 45m |
| 2026-06-22 | JAL754 | BLR → NRT | Jun 22, 21:14 UTC | Jun 22, 21:30 UTC | 15m |
| 2026-06-22 | JAL753 | - | Jun 22, 10:25 UTC | Jun 22, 18:30 UTC | 8h 5m |
| 2026-06-21 | JAL65 | - | Jun 21, 21:19 UTC | Jun 22, 08:00 UTC | 10h 40m |
| 2026-06-21 | JAL66 | NRT → SAN | Jun 21, 09:15 UTC | Jun 21, 18:50 UTC | 9h 35m |
| 2026-06-20 | JAL67 | - | Jun 20, 20:45 UTC | Jun 21, 05:59 UTC | 9h 15m |
| 2026-06-20 | JAL68 | NRT → SEA | Jun 20, 09:14 UTC | Jun 20, 17:54 UTC | 8h 40m |
| 2026-06-19 | JAL408 | FRA → NRT | Jun 19, 18:34 UTC | Jun 20, 06:45 UTC | 12h 10m |
| 2026-06-19 | JAL407 | NRT → FRA | Jun 19, 01:59 UTC | Jun 19, 15:49 UTC | 13h 50m |
| 2026-06-17 | JAL7 | BOS → NRT | Jun 17, 17:35 UTC | Jun 18, 06:25 UTC | 12h 50m |
| 2026-06-16 | JAL8 | NRT → BOS | Jun 16, 10:55 UTC | Jun 16, 22:55 UTC | 12h 1m |
| 2026-06-15 | JAL57 | - | Jun 15, 21:14 UTC | Jun 16, 07:25 UTC | 10h 10m |
| 2026-06-15 | JAL58 | NRT → SFO | Jun 15, 10:15 UTC | Jun 15, 18:55 UTC | 8h 40m |
| 2026-06-14 | JAL408 | FRA → NRT | Jun 14, 18:30 UTC | Jun 15, 06:49 UTC | 12h 19m |
| 2026-06-14 | JAL407 | - | Jun 14, 07:20 UTC | Jun 14, 15:25 UTC | 8h 5m |
| 2026-06-14 | JAL407 | - | Jun 14, 02:00 UTC | Jun 14, 02:30 UTC | 30m |
| 2026-06-12 | JAL408 | FRA → NRT | Jun 12, 18:50 UTC | Jun 13, 07:10 UTC | 12h 19m |
| 2026-06-12 | JAL407 | NRT → FRA | Jun 12, 02:05 UTC | Jun 12, 15:05 UTC | 13h 0m |
| 2026-06-10 | JAL17 | YVR → NRT | Jun 10, 21:20 UTC | Jun 11, 07:05 UTC | 9h 45m |
| 2026-06-10 | JAL18 | NRT → YVR | Jun 10, 10:25 UTC | Jun 10, 18:15 UTC | 7h 50m |
| 2026-06-09 | JAL061 | LAX → NRT | Jun 9, 20:45 UTC | Jun 10, 07:50 UTC | 11h 5m |
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 JA868J page for operator, model, and routing details .