sensors Mode-S transponder
841043
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA04GR · BOEING 737-800
- Hex
- 841043
- Octal
- 41010103
- Decimal
- 8,654,915
- Country
- JP
- Tail
- JA04GR
- Type
- B738
- Flights observed
- 64
- Distinct callsigns
- 11
- Country
- JP
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address 841043 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAL8695 | - | 15 | 2026-05-14 |
| JAL8680 | - | 12 | 2026-05-16 |
| JAL8799 | - | 9 | 2026-05-13 |
| JAL8689 | - | 8 | 2026-05-11 |
| JAL8790 | - | 6 | 2026-05-15 |
| JAL8696 | - | 5 | 2026-05-14 |
| SJO621 | Spring Japan | 4 | 2026-04-17 |
| SJO622 | Spring Japan | 2 | 2026-04-18 |
| SJO9811 | - | 1 | 2026-05-17 |
| SJO858 | - | 1 | 2026-04-23 |
| SJO857 | - | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-17 | SJO9811 | - | May 17, 11:15 UTC | May 17, 12:35 UTC | 1h 20m |
| 2026-05-16 | JAL8680 | - | May 16, 10:50 UTC | May 17, 06:30 UTC | 19h 40m |
| 2026-05-16 | JAL8680 | - | May 16, 09:21 UTC | May 17, 06:30 UTC | 21h 10m |
| 2026-05-15 | JAL8790 | - | May 15, 10:50 UTC | May 16, 05:10 UTC | 18h 19m |
| 2026-05-14 | JAL8696 | - | May 14, 11:45 UTC | May 14, 13:15 UTC | 1h 30m |
| 2026-05-14 | JAL8695 | - | May 14, 06:35 UTC | May 14, 07:55 UTC | 1h 20m |
| 2026-05-13 | JAL8799 | - | May 13, 10:50 UTC | May 14, 04:50 UTC | 18h 0m |
| 2026-05-13 | JAL8790 | - | May 13, 03:25 UTC | May 13, 04:55 UTC | 1h 30m |
| 2026-05-12 | JAL8799 | - | May 12, 10:50 UTC | May 12, 12:15 UTC | 1h 25m |
| 2026-05-11 | JAL8680 | - | May 11, 10:50 UTC | May 12, 06:05 UTC | 19h 15m |
| 2026-05-11 | JAL8689 | NRT → NRT | May 11, 09:30 UTC | May 12, 06:05 UTC | 20h 36m |
| 2026-05-10 | JAL8680 | - | May 10, 11:10 UTC | May 11, 06:10 UTC | 19h 0m |
| 2026-05-10 | JAL8680 | NRT → NRT | May 10, 09:35 UTC | May 11, 06:10 UTC | 20h 35m |
| 2026-05-09 | JAL8799 | NRT → NRT | May 9, 11:15 UTC | May 10, 05:10 UTC | 17h 55m |
| 2026-05-08 | JAL8799 | - | May 8, 10:54 UTC | May 9, 04:45 UTC | 17h 50m |
| 2026-05-08 | JAL8680 | - | May 8, 04:19 UTC | May 8, 06:20 UTC | 2h 0m |
| 2026-05-07 | JAL8689 | - | May 7, 09:20 UTC | May 7, 11:25 UTC | 2h 5m |
| 2026-05-06 | JAL8799 | - | May 6, 10:50 UTC | May 7, 05:10 UTC | 18h 19m |
| 2026-05-06 | JAL8680 | - | May 6, 04:00 UTC | May 6, 06:00 UTC | 2h 0m |
| 2026-05-06 | JAL8680 | - | May 6, 03:00 UTC | May 6, 03:10 UTC | 10m |
| 2026-05-05 | JAL8689 | - | May 5, 09:20 UTC | May 5, 11:30 UTC | 2h 10m |
| 2026-05-05 | JAL8680 | - | May 5, 04:10 UTC | May 5, 06:15 UTC | 2h 5m |
| 2026-05-04 | JAL8689 | - | May 4, 11:35 UTC | May 4, 12:10 UTC | 35m |
| 2026-05-04 | JAL8689 | - | May 4, 09:50 UTC | May 4, 11:05 UTC | 1h 15m |
| 2026-05-04 | JAL8680 | - | May 4, 03:05 UTC | May 4, 06:10 UTC | 3h 5m |
| 2026-05-03 | JAL8689 | - | May 3, 09:30 UTC | May 3, 11:45 UTC | 2h 15m |
| 2026-05-02 | JAL8799 | - | May 2, 10:50 UTC | May 3, 05:05 UTC | 18h 14m |
| 2026-05-02 | JAL8799 | NRT → NRT | May 2, 10:35 UTC | May 3, 05:05 UTC | 18h 29m |
| 2026-05-02 | JAL8680 | - | May 2, 03:20 UTC | May 2, 06:10 UTC | 2h 50m |
| 2026-05-01 | JAL8689 | - | May 1, 09:35 UTC | May 1, 11:50 UTC | 2h 15m |
| 2026-04-30 | JAL8799 | - | Apr 30, 10:50 UTC | May 1, 05:05 UTC | 18h 15m |
| 2026-04-29 | JAL8695 | NRT → NRT | Apr 29, 05:25 UTC | Apr 29, 12:30 UTC | 7h 6m |
| 2026-04-28 | JAL8695 | NRT → NRT | Apr 28, 05:25 UTC | Apr 28, 12:30 UTC | 7h 5m |
| 2026-04-27 | JAL8695 | - | Apr 27, 05:20 UTC | Apr 27, 12:10 UTC | 6h 50m |
| 2026-04-26 | JAL8695 | NRT → NRT | Apr 26, 05:20 UTC | Apr 26, 12:40 UTC | 7h 20m |
| 2026-04-25 | JAL8696 | - | Apr 25, 10:50 UTC | Apr 25, 12:05 UTC | 1h 15m |
| 2026-04-25 | JAL8695 | - | Apr 25, 05:20 UTC | Apr 25, 06:50 UTC | 1h 30m |
| 2026-04-24 | JAL8695 | NRT → NRT | Apr 24, 05:15 UTC | Apr 24, 12:20 UTC | 7h 5m |
| 2026-04-23 | JAL8695 | - | Apr 23, 05:25 UTC | Apr 23, 12:15 UTC | 6h 50m |
| 2026-04-23 | SJO858 | - | Apr 23, 02:10 UTC | Apr 23, 03:20 UTC | 1h 10m |
| 2026-04-22 | SJO857 | - | Apr 22, 23:50 UTC | Apr 23, 00:50 UTC | 1h 0m |
| 2026-04-22 | JAL8695 | NRT → NRT | Apr 22, 05:15 UTC | Apr 22, 12:15 UTC | 7h 0m |
| 2026-04-21 | JAL8695 | NRT → NRT | Apr 21, 05:25 UTC | Apr 21, 12:35 UTC | 7h 10m |
| 2026-04-20 | JAL8695 | NRT → NRT | Apr 20, 05:20 UTC | Apr 20, 12:10 UTC | 6h 50m |
| 2026-04-19 | JAL8695 | - | Apr 19, 05:20 UTC | Apr 19, 12:25 UTC | 7h 5m |
| 2026-04-18 | JAL8695 | NRT → NRT | Apr 18, 05:30 UTC | Apr 18, 12:30 UTC | 7h 0m |
| 2026-04-18 | SJO622 | HIJ → NRT | Apr 18, 01:25 UTC | Apr 18, 02:20 UTC | 55m |
| 2026-04-17 | SJO621 | NRT → HIJ | Apr 17, 23:25 UTC | Apr 17, 23:55 UTC | 30m |
| 2026-04-17 | SJO621 | NRT → HIJ | Apr 17, 22:50 UTC | Apr 17, 23:20 UTC | 30m |
| 2026-04-17 | JAL8696 | - | Apr 17, 11:25 UTC | Apr 17, 12:25 UTC | 1h 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 JA04GR page for operator, model, and routing details .