sensors Mode-S transponder
868012
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA736J · BOEING 777-300ER
- Hex
- 868012
- Octal
- 41500022
- Decimal
- 8,814,610
- Country
- JP
- Tail
- JA736J
- Type
- B77W
- Flights observed
- 76
- Distinct callsigns
- 18
- Country
- JP
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 868012 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 |
|---|---|---|---|
| JAL47 | Japan Airlines | 11 | 2026-05-21 |
| JAL1 | Japan Airlines | 10 | 2026-05-23 |
| JAL48 | Japan Airlines | 9 | 2026-05-22 |
| JAL52 | Japan Airlines | 7 | 2026-05-08 |
| JAL2 | Japan Airlines | 7 | 2026-05-23 |
| JAL9 | Japan Airlines | 6 | 2026-05-29 |
| JAL51 | Japan Airlines | 6 | 2026-05-08 |
| JAL10 | Japan Airlines | 6 | 2026-05-29 |
| JAL82 | Japan Airlines | 2 | 2026-05-28 |
| JAL37 | Japan Airlines | 2 | 2026-04-21 |
| JAL36 | Japan Airlines | 2 | 2026-04-21 |
| JAL29 | Japan Airlines | 2 | 2026-05-21 |
| JAL92 | Japan Airlines | 1 | 2026-04-24 |
| JAL91 | Japan Airlines | 1 | 2026-04-23 |
| JAL89 | Japan Airlines | 1 | 2026-04-27 |
| JAL34 | Japan Airlines | 1 | 2026-05-26 |
| JAL31 | Japan Airlines | 1 | 2026-05-26 |
| JAL26 | Japan Airlines | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | JAL9 | ORD → NRT | May 29, 19:55 UTC | May 30, 08:10 UTC | 12h 15m |
| 2026-05-29 | JAL10 | NRT → ORD | May 29, 04:55 UTC | May 29, 16:15 UTC | 11h 20m |
| 2026-05-28 | JAL82 | SHA → HND | May 28, 00:40 UTC | May 28, 07:25 UTC | 6h 45m |
| 2026-05-26 | JAL34 | BKK → HND | May 26, 15:09 UTC | May 26, 20:40 UTC | 5h 30m |
| 2026-05-26 | JAL31 | HND → TSA | May 26, 02:10 UTC | May 26, 07:55 UTC | 5h 45m |
| 2026-05-25 | JAL82 | SHA → HND | May 25, 01:55 UTC | May 25, 07:15 UTC | 5h 20m |
| 2026-05-23 | JAL1 | SFO → HND | May 23, 19:25 UTC | May 24, 05:55 UTC | 10h 30m |
| 2026-05-23 | JAL2 | HND → SFO | May 23, 07:45 UTC | May 23, 16:30 UTC | 8h 45m |
| 2026-05-22 | JAL48 | HEL → HND | May 22, 15:50 UTC | May 23, 05:10 UTC | 13h 20m |
| 2026-05-21 | JAL47 | HND → HEL | May 21, 23:20 UTC | May 22, 12:05 UTC | 12h 45m |
| 2026-05-21 | JAL26 | HKG → HND | May 21, 07:40 UTC | May 21, 11:10 UTC | 3h 30m |
| 2026-05-21 | JAL29 | HND → HKG | May 21, 05:00 UTC | May 21, 05:15 UTC | 15m |
| 2026-05-21 | JAL29 | HND → HKG | May 21, 01:20 UTC | May 21, 04:30 UTC | 3h 10m |
| 2026-05-19 | JAL9 | ORD → NRT | May 19, 20:05 UTC | May 20, 08:20 UTC | 12h 16m |
| 2026-05-19 | JAL10 | NRT → ORD | May 19, 04:30 UTC | May 19, 15:35 UTC | 11h 5m |
| 2026-05-17 | JAL9 | ORD → NRT | May 17, 20:15 UTC | May 18, 08:20 UTC | 12h 5m |
| 2026-05-17 | JAL10 | NRT → ORD | May 17, 04:30 UTC | May 17, 15:31 UTC | 11h 0m |
| 2026-05-15 | JAL1 | SFO → HND | May 15, 19:50 UTC | May 16, 06:45 UTC | 10h 56m |
| 2026-05-15 | JAL2 | HND → SFO | May 15, 08:25 UTC | May 15, 17:20 UTC | 8h 54m |
| 2026-05-14 | JAL48 | HEL → HND | May 14, 15:15 UTC | May 15, 04:10 UTC | 12h 55m |
| 2026-05-13 | JAL47 | HND → HEL | May 13, 23:10 UTC | May 14, 12:05 UTC | 12h 55m |
| 2026-05-12 | JAL1 | SFO → HND | May 12, 19:25 UTC | May 13, 05:40 UTC | 10h 15m |
| 2026-05-12 | JAL2 | HND → SFO | May 12, 07:50 UTC | May 12, 16:25 UTC | 8h 35m |
| 2026-05-10 | JAL48 | HEL → HND | May 10, 15:19 UTC | May 11, 04:40 UTC | 13h 20m |
| 2026-05-09 | JAL47 | HND → HEL | May 9, 23:09 UTC | May 10, 11:45 UTC | 12h 35m |
| 2026-05-08 | JAL52 | SYD → HND | May 8, 23:20 UTC | May 9, 08:30 UTC | 9h 10m |
| 2026-05-08 | JAL51 | HND → SYD | May 8, 11:14 UTC | May 8, 20:10 UTC | 8h 55m |
| 2026-05-07 | JAL52 | SYD → HND | May 7, 23:14 UTC | May 8, 08:40 UTC | 9h 25m |
| 2026-05-07 | JAL51 | HND → SYD | May 7, 11:05 UTC | May 7, 20:05 UTC | 9h 0m |
| 2026-05-06 | JAL52 | SYD → HND | May 6, 23:35 UTC | May 7, 08:55 UTC | 9h 20m |
| 2026-05-06 | JAL51 | HND → SYD | May 6, 11:25 UTC | May 6, 20:10 UTC | 8h 44m |
| 2026-05-05 | JAL48 | HEL → HND | May 5, 15:15 UTC | May 6, 04:55 UTC | 13h 40m |
| 2026-05-04 | JAL47 | HND → HEL | May 4, 23:15 UTC | May 5, 11:35 UTC | 12h 20m |
| 2026-05-04 | JAL52 | SYD → HND | May 4, 08:05 UTC | May 4, 08:50 UTC | 45m |
| 2026-05-03 | JAL52 | SYD → HND | May 3, 23:25 UTC | May 4, 00:10 UTC | 45m |
| 2026-05-03 | JAL51 | HND → SYD | May 3, 11:15 UTC | May 3, 20:20 UTC | 9h 5m |
| 2026-05-02 | JAL9 | ORD → NRT | May 2, 19:40 UTC | May 3, 08:45 UTC | 13h 4m |
| 2026-05-02 | JAL10 | NRT → ORD | May 2, 04:30 UTC | May 2, 15:40 UTC | 11h 10m |
| 2026-04-30 | JAL9 | ORD → NRT | Apr 30, 19:45 UTC | May 1, 09:00 UTC | 13h 16m |
| 2026-04-30 | JAL10 | NRT → ORD | Apr 30, 04:35 UTC | Apr 30, 15:35 UTC | 11h 0m |
| 2026-04-28 | JAL1 | SFO → HND | Apr 28, 19:20 UTC | Apr 29, 06:10 UTC | 10h 50m |
| 2026-04-28 | JAL2 | HND → SFO | Apr 28, 07:45 UTC | Apr 28, 16:40 UTC | 8h 55m |
| 2026-04-27 | JAL89 | HNL → HND | Apr 27, 08:50 UTC | Apr 28, 03:50 UTC | 19h 0m |
| 2026-04-26 | JAL48 | HEL → HND | Apr 26, 15:10 UTC | Apr 27, 04:25 UTC | 13h 15m |
| 2026-04-25 | JAL47 | HND → HEL | Apr 25, 23:30 UTC | Apr 26, 12:25 UTC | 12h 55m |
| 2026-04-24 | JAL1 | SFO → HND | Apr 24, 19:20 UTC | Apr 25, 05:55 UTC | 10h 35m |
| 2026-04-24 | JAL2 | HND → SFO | Apr 24, 07:45 UTC | Apr 24, 16:15 UTC | 8h 30m |
| 2026-04-24 | JAL92 | GMP → HND | Apr 24, 03:20 UTC | Apr 24, 04:55 UTC | 1h 35m |
| 2026-04-23 | JAL91 | HND → GMP | Apr 23, 23:45 UTC | Apr 24, 01:45 UTC | 2h 0m |
| 2026-04-22 | JAL9 | ORD → NRT | Apr 22, 19:20 UTC | Apr 23, 08:10 UTC | 12h 50m |
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 JA736J page for operator, model, and routing details .