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