sensors Mode-S transponder
8682DA
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA740J · BOEING 777-300ER
- Hex
- 8682DA
- Octal
- 41501332
- Decimal
- 8,815,322
- Country
- JP
- Tail
- JA740J
- Type
- B77W
- Flights observed
- 145
- Distinct callsigns
- 18
- Country
- JP
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 8682DA 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAL10 | - | 23 | 2026-07-10 |
| JAL9 | - | 20 | 2026-07-10 |
| JAL1 | - | 16 | 2026-07-02 |
| JAL2 | - | 15 | 2026-07-02 |
| JAL47 | - | 12 | 2026-07-13 |
| JAL34 | - | 12 | 2026-07-12 |
| JAL48 | - | 11 | 2026-06-24 |
| JAL31 | - | 11 | 2026-07-12 |
| JAL46 | - | 5 | 2026-07-07 |
| JAL45 | Japan Airlines | 5 | 2026-07-07 |
| JAL37 | Japan Airlines | 3 | 2026-05-03 |
| JAL36 | Japan Airlines | 3 | 2026-05-03 |
| JAL29 | - | 3 | 2026-07-05 |
| JAL26 | - | 2 | 2026-07-05 |
| JAL89 | Japan Airlines | 1 | 2026-05-22 |
| JAL52 | Japan Airlines | 1 | 2026-04-29 |
| JAL51 | Japan Airlines | 1 | 2026-04-29 |
| JAL0000 | - | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JAL47 | HND → HEL | Jul 13, 23:05 UTC | Jul 14, 11:50 UTC | 12h 45m |
| 2026-07-12 | JAL34 | - | Jul 12, 17:20 UTC | Jul 12, 20:40 UTC | 3h 20m |
| 2026-07-12 | JAL34 | - | Jul 12, 15:01 UTC | Jul 12, 15:15 UTC | 15m |
| 2026-07-12 | JAL31 | - | Jul 12, 07:10 UTC | Jul 12, 07:31 UTC | 20m |
| 2026-07-12 | JAL31 | - | Jul 12, 01:55 UTC | Jul 12, 04:45 UTC | 2h 50m |
| 2026-07-10 | JAL9 | - | Jul 10, 20:25 UTC | Jul 11, 08:15 UTC | 11h 50m |
| 2026-07-10 | JAL10 | HND → ORD | Jul 10, 04:15 UTC | Jul 10, 15:40 UTC | 11h 25m |
| 2026-07-07 | JAL46 | CDG → HND | Jul 7, 18:45 UTC | Jul 8, 07:50 UTC | 13h 5m |
| 2026-07-07 | JAL45 | HND → CDG | Jul 7, 01:40 UTC | Jul 7, 15:40 UTC | 14h 0m |
| 2026-07-05 | JAL26 | HKG → HND | Jul 5, 07:45 UTC | Jul 5, 11:30 UTC | 3h 45m |
| 2026-07-05 | JAL29 | - | Jul 5, 01:40 UTC | Jul 5, 05:15 UTC | 3h 35m |
| 2026-07-04 | JAL26 | HKG → HND | Jul 4, 08:05 UTC | Jul 4, 11:50 UTC | 3h 45m |
| 2026-07-04 | JAL29 | - | Jul 4, 04:50 UTC | Jul 4, 05:15 UTC | 25m |
| 2026-07-04 | JAL29 | - | Jul 4, 01:25 UTC | Jul 4, 04:20 UTC | 2h 55m |
| 2026-07-02 | JAL1 | - | Jul 2, 20:20 UTC | Jul 3, 06:30 UTC | 10h 10m |
| 2026-07-02 | JAL2 | - | Jul 2, 07:50 UTC | Jul 2, 16:30 UTC | 8h 40m |
| 2026-07-01 | JAL34 | - | Jul 1, 17:15 UTC | Jul 1, 20:35 UTC | 3h 20m |
| 2026-07-01 | JAL31 | - | Jul 1, 02:05 UTC | Jul 1, 07:40 UTC | 5h 35m |
| 2026-06-29 | JAL46 | - | Jun 29, 19:00 UTC | Jun 30, 08:00 UTC | 13h 1m |
| 2026-06-29 | JAL45 | HND → CDG | Jun 29, 01:50 UTC | Jun 29, 15:39 UTC | 13h 50m |
| 2026-06-27 | JAL9 | - | Jun 27, 19:59 UTC | Jun 28, 08:09 UTC | 12h 10m |
| 2026-06-27 | JAL10 | HND → ORD | Jun 27, 04:34 UTC | Jun 27, 15:39 UTC | 11h 5m |
| 2026-06-25 | JAL1 | - | Jun 25, 19:34 UTC | Jun 26, 06:09 UTC | 10h 35m |
| 2026-06-25 | JAL2 | HND → SFO | Jun 25, 07:54 UTC | Jun 25, 16:45 UTC | 8h 50m |
| 2026-06-24 | JAL48 | HEL → HND | Jun 24, 15:39 UTC | Jun 25, 04:29 UTC | 12h 50m |
| 2026-06-23 | JAL47 | HND → HEL | Jun 23, 23:14 UTC | Jun 24, 11:54 UTC | 12h 40m |
| 2026-06-23 | JAL1 | - | Jun 23, 04:45 UTC | Jun 23, 05:34 UTC | 50m |
| 2026-06-22 | JAL1 | - | Jun 22, 19:29 UTC | Jun 23, 00:15 UTC | 4h 45m |
| 2026-06-22 | JAL2 | HND → SFO | Jun 22, 08:15 UTC | Jun 22, 17:00 UTC | 8h 45m |
| 2026-06-21 | JAL1 | SFO → HND | Jun 21, 19:14 UTC | Jun 22, 05:24 UTC | 10h 10m |
| 2026-06-21 | JAL2 | HND → SFO | Jun 21, 07:45 UTC | Jun 21, 16:49 UTC | 9h 5m |
| 2026-06-20 | JAL48 | HEL → HND | Jun 20, 16:34 UTC | Jun 21, 05:04 UTC | 12h 30m |
| 2026-06-20 | JAL47 | HND → HEL | Jun 20, 00:29 UTC | Jun 20, 13:29 UTC | 13h 0m |
| 2026-06-18 | JAL1 | - | Jun 18, 19:20 UTC | Jun 19, 05:34 UTC | 10h 14m |
| 2026-06-18 | JAL2 | - | Jun 18, 07:50 UTC | Jun 18, 17:00 UTC | 9h 10m |
| 2026-06-17 | JAL48 | HEL → HND | Jun 17, 15:50 UTC | Jun 18, 05:20 UTC | 13h 30m |
| 2026-06-16 | JAL47 | HND → HEL | Jun 16, 23:05 UTC | Jun 17, 12:10 UTC | 13h 5m |
| 2026-06-15 | JAL1 | - | Jun 15, 19:35 UTC | Jun 16, 05:50 UTC | 10h 15m |
| 2026-06-15 | JAL2 | HND → SFO | Jun 15, 07:40 UTC | Jun 15, 16:30 UTC | 8h 50m |
| 2026-06-14 | JAL48 | - | Jun 14, 15:20 UTC | Jun 15, 05:15 UTC | 13h 54m |
| 2026-06-13 | JAL47 | HND → HEL | Jun 13, 23:20 UTC | Jun 14, 12:30 UTC | 13h 10m |
| 2026-06-12 | JAL1 | SFO → HND | Jun 12, 19:15 UTC | Jun 13, 05:30 UTC | 10h 14m |
| 2026-06-12 | JAL2 | HND → SFO | Jun 12, 08:15 UTC | Jun 12, 16:50 UTC | 8h 35m |
| 2026-06-11 | JAL48 | HEL → HND | Jun 11, 15:25 UTC | Jun 12, 05:10 UTC | 13h 46m |
| 2026-06-10 | JAL47 | HND → HEL | Jun 10, 23:10 UTC | Jun 11, 11:50 UTC | 12h 40m |
| 2026-06-09 | JAL1 | SFO → HND | Jun 9, 21:00 UTC | Jun 10, 06:30 UTC | 9h 30m |
| 2026-06-09 | JAL2 | HND → SFO | Jun 9, 08:05 UTC | Jun 9, 19:05 UTC | 11h 0m |
| 2026-06-08 | JAL48 | HEL → HND | Jun 8, 15:20 UTC | Jun 9, 04:25 UTC | 13h 5m |
| 2026-06-07 | JAL47 | HND → HEL | Jun 7, 23:10 UTC | Jun 8, 12:20 UTC | 13h 10m |
| 2026-06-06 | JAL1 | SFO → HND | Jun 6, 19:14 UTC | Jun 7, 05:55 UTC | 10h 40m |
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 JA740J page for operator, model, and routing details .