sensors Mode-S transponder
868340
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA743J · BOEING 777-300ER
- Hex
- 868340
- Octal
- 41501500
- Decimal
- 8,815,424
- Country
- JP
- Tail
- JA743J
- Type
- B77W
- Flights observed
- 146
- Distinct callsigns
- 20
- Country
- JP
- Last broadcast
- Jul 26, 08:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 868340 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 |
|---|---|---|---|
| JAL9 | Japan Airlines | 21 | 2026-07-24 |
| JAL10 | Japan Airlines | 20 | 2026-07-24 |
| JAL2 | Japan Airlines | 18 | 2026-07-22 |
| JAL1 | Japan Airlines | 16 | 2026-07-22 |
| JAL34 | - | 12 | 2026-07-09 |
| JAL48 | Japan Airlines | 10 | 2026-07-21 |
| JAL47 | Japan Airlines | 10 | 2026-07-20 |
| JAL31 | - | 10 | 2026-07-09 |
| JAL37 | Japan Airlines | 6 | 2026-04-19 |
| JAL46 | - | 4 | 2026-06-23 |
| JAL45 | Japan Airlines | 4 | 2026-06-23 |
| JAL36 | Japan Airlines | 4 | 2026-04-16 |
| JAL82 | Japan Airlines | 1 | 2026-07-26 |
| JAL81 | - | 1 | 2026-06-30 |
| JAL52 | Japan Airlines | 1 | 2026-04-28 |
| JAL515 | - | 1 | 2026-07-06 |
| JAL514 | - | 1 | 2026-07-06 |
| JAL51 | Japan Airlines | 1 | 2026-04-28 |
| JAL332 | - | 1 | 2026-07-06 |
| JAL329 | - | 1 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | JAL82 | SHA → HND | Jul 26, 00:50 UTC | Jul 26, 07:25 UTC | 6h 36m |
| 2026-07-24 | JAL9 | ORD → NRT | Jul 24, 19:50 UTC | Jul 25, 08:45 UTC | 12h 55m |
| 2026-07-24 | JAL10 | NRT → ORD | Jul 24, 04:35 UTC | Jul 24, 15:50 UTC | 11h 15m |
| 2026-07-22 | JAL1 | SFO → HND | Jul 22, 20:00 UTC | Jul 23, 05:45 UTC | 9h 45m |
| 2026-07-22 | JAL2 | HND → SFO | Jul 22, 16:30 UTC | Jul 22, 17:30 UTC | 1h 0m |
| 2026-07-21 | JAL48 | HEL → HND | Jul 21, 15:15 UTC | Jul 22, 04:30 UTC | 13h 15m |
| 2026-07-20 | JAL47 | HND → HEL | Jul 20, 23:15 UTC | Jul 21, 11:55 UTC | 12h 39m |
| 2026-07-19 | JAL1 | SFO → HND | Jul 19, 20:05 UTC | Jul 20, 05:55 UTC | 9h 50m |
| 2026-07-19 | JAL2 | - | Jul 19, 07:50 UTC | Jul 19, 17:15 UTC | 9h 25m |
| 2026-07-18 | JAL48 | HEL → HND | Jul 18, 15:25 UTC | Jul 19, 04:45 UTC | 13h 20m |
| 2026-07-17 | JAL47 | HND → HEL | Jul 17, 23:05 UTC | Jul 18, 12:05 UTC | 13h 1m |
| 2026-07-16 | JAL9 | ORD → HND | Jul 16, 20:35 UTC | Jul 17, 08:45 UTC | 12h 10m |
| 2026-07-16 | JAL10 | HND → ORD | Jul 16, 04:25 UTC | Jul 16, 15:45 UTC | 11h 20m |
| 2026-07-13 | JAL9 | - | Jul 13, 20:15 UTC | Jul 14, 08:35 UTC | 12h 20m |
| 2026-07-13 | JAL10 | HND → ORD | Jul 13, 04:25 UTC | Jul 13, 15:45 UTC | 11h 20m |
| 2026-07-11 | JAL1 | - | Jul 11, 19:55 UTC | Jul 12, 06:01 UTC | 10h 5m |
| 2026-07-11 | JAL2 | HND → SFO | Jul 11, 07:45 UTC | Jul 11, 17:00 UTC | 9h 15m |
| 2026-07-10 | JAL48 | HEL → HND | Jul 10, 15:20 UTC | Jul 11, 04:25 UTC | 13h 5m |
| 2026-07-09 | JAL47 | HND → HEL | Jul 9, 23:10 UTC | Jul 10, 12:10 UTC | 13h 0m |
| 2026-07-09 | JAL34 | - | Jul 9, 14:55 UTC | Jul 9, 20:20 UTC | 5h 25m |
| 2026-07-09 | JAL31 | - | Jul 9, 02:05 UTC | Jul 9, 07:35 UTC | 5h 30m |
| 2026-07-07 | JAL1 | SFO → HND | Jul 7, 20:05 UTC | Jul 8, 06:25 UTC | 10h 20m |
| 2026-07-07 | JAL2 | HND → SFO | Jul 7, 08:00 UTC | Jul 7, 17:15 UTC | 9h 15m |
| 2026-07-06 | JAL332 | - | Jul 6, 12:15 UTC | Jul 6, 13:25 UTC | 1h 10m |
| 2026-07-06 | JAL329 | - | Jul 6, 09:25 UTC | Jul 6, 10:30 UTC | 1h 5m |
| 2026-07-06 | JAL514 | - | Jul 6, 06:40 UTC | Jul 6, 07:55 UTC | 1h 15m |
| 2026-07-06 | JAL515 | - | Jul 6, 04:15 UTC | Jul 6, 05:25 UTC | 1h 10m |
| 2026-07-06 | JAL308 | - | Jul 6, 01:30 UTC | Jul 6, 02:45 UTC | 1h 15m |
| 2026-07-05 | JAL305 | - | Jul 5, 22:25 UTC | Jul 5, 23:30 UTC | 1h 5m |
| 2026-07-04 | JAL1 | SFO → HND | Jul 4, 20:00 UTC | Jul 5, 06:10 UTC | 10h 10m |
| 2026-07-04 | JAL2 | HND → SFO | Jul 4, 07:55 UTC | Jul 4, 17:00 UTC | 9h 5m |
| 2026-07-03 | JAL48 | HEL → HND | Jul 3, 15:30 UTC | Jul 4, 04:50 UTC | 13h 20m |
| 2026-07-02 | JAL47 | HND → HEL | Jul 2, 23:05 UTC | Jul 3, 12:00 UTC | 12h 55m |
| 2026-07-01 | JAL9 | ORD → HND | Jul 1, 20:05 UTC | Jul 2, 08:20 UTC | 12h 15m |
| 2026-07-01 | JAL10 | HND → ORD | Jul 1, 04:35 UTC | Jul 1, 15:45 UTC | 11h 10m |
| 2026-06-30 | JAL81 | - | Jun 30, 00:49 UTC | Jun 30, 07:40 UTC | 6h 51m |
| 2026-06-28 | JAL1 | - | Jun 28, 19:14 UTC | Jun 29, 05:59 UTC | 10h 45m |
| 2026-06-28 | JAL2 | HND → SFO | Jun 28, 07:44 UTC | Jun 28, 16:25 UTC | 8h 40m |
| 2026-06-27 | JAL48 | HEL → HND | Jun 27, 15:14 UTC | Jun 28, 04:35 UTC | 13h 20m |
| 2026-06-26 | JAL47 | HND → HEL | Jun 26, 23:15 UTC | Jun 27, 11:44 UTC | 12h 30m |
| 2026-06-25 | JAL9 | - | Jun 25, 20:45 UTC | Jun 26, 09:14 UTC | 12h 30m |
| 2026-06-25 | JAL10 | HND → ORD | Jun 25, 04:20 UTC | Jun 25, 15:50 UTC | 11h 30m |
| 2026-06-23 | JAL46 | - | Jun 23, 19:59 UTC | Jun 24, 08:45 UTC | 12h 45m |
| 2026-06-23 | JAL45 | HND → CDG | Jun 23, 02:15 UTC | Jun 23, 16:24 UTC | 14h 10m |
| 2026-06-21 | JAL9 | - | Jun 21, 20:09 UTC | Jun 22, 08:25 UTC | 12h 15m |
| 2026-06-21 | JAL10 | HND → ORD | Jun 21, 04:14 UTC | Jun 21, 15:40 UTC | 11h 25m |
| 2026-06-19 | JAL46 | - | Jun 19, 19:19 UTC | Jun 20, 08:09 UTC | 12h 50m |
| 2026-06-19 | JAL45 | HND → CDG | Jun 19, 01:54 UTC | Jun 19, 16:14 UTC | 14h 20m |
| 2026-06-17 | JAL46 | - | Jun 17, 19:20 UTC | Jun 18, 08:20 UTC | 13h 0m |
| 2026-06-17 | JAL45 | HND → CDG | Jun 17, 02:40 UTC | Jun 17, 16:20 UTC | 13h 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 JA743J page for operator, model, and routing details .