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