sensors Mode-S transponder
781417
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1112 · BOEING 787-9 Dreamliner
- Hex
- 781417
- Octal
- 36012027
- Decimal
- 7,869,463
- Country
- CN
- Tail
- B-1112
- Type
- B789
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 781417 falls within the block assigned to China (CN) by ICAO Annex 10, Volume III. Every aircraft registered in China 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 |
|---|---|---|---|
| CSH816 | - | 35 | 2026-06-16 |
| CSH815 | - | 35 | 2026-06-15 |
| CSH823 | Shanghai Airlines | 12 | 2026-06-12 |
| CSH870 | - | 9 | 2026-07-12 |
| CSH9253 | - | 8 | 2026-06-22 |
| CSH869 | - | 8 | 2026-07-10 |
| CSH885 | - | 7 | 2026-07-10 |
| CSH824 | Shanghai Airlines | 6 | 2026-06-16 |
| CES738 | - | 6 | 2026-06-29 |
| CES737 | - | 6 | 2026-06-28 |
| CSH886 | - | 4 | 2026-07-02 |
| CSH871 | Shanghai Airlines | 3 | 2026-07-08 |
| CSH869D | - | 3 | 2026-07-12 |
| CSH896 | - | 2 | 2026-07-01 |
| CSH892 | - | 2 | 2026-06-27 |
| CSH872 | - | 2 | 2026-07-08 |
| CSH834 | Shanghai Airlines | 2 | 2026-04-15 |
| CSH833 | Shanghai Airlines | 2 | 2026-04-15 |
| CSH821 | - | 2 | 2026-07-13 |
| CES740 | China Eastern Airlines | 2 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSH821 | KIX → KIX | Jul 13, 11:35 UTC | Jul 14, 08:45 UTC | 21h 10m |
| 2026-07-12 | CSH870 | BUD → KIX | Jul 12, 20:30 UTC | Jul 13, 10:20 UTC | 13h 50m |
| 2026-07-12 | CSH869D | - | Jul 12, 00:40 UTC | Jul 12, 18:05 UTC | 17h 25m |
| 2026-07-11 | CSH869D | - | Jul 11, 19:50 UTC | Jul 12, 18:05 UTC | 22h 15m |
| 2026-07-11 | CSH869D | - | Jul 11, 19:05 UTC | Jul 12, 17:45 UTC | 22h 40m |
| 2026-07-10 | CSH869 | - | Jul 10, 11:30 UTC | Jul 11, 04:35 UTC | 17h 5m |
| 2026-07-10 | CSH869 | - | Jul 10, 08:30 UTC | Jul 11, 04:35 UTC | 20h 5m |
| 2026-07-10 | CSH885 | - | Jul 10, 02:35 UTC | Jul 10, 06:50 UTC | 4h 15m |
| 2026-07-09 | CSH885 | - | Jul 9, 04:05 UTC | Jul 10, 03:45 UTC | 23h 40m |
| 2026-07-08 | CSH872 | - | Jul 8, 21:40 UTC | Jul 9, 04:45 UTC | 7h 5m |
| 2026-07-08 | CSH872 | - | Jul 8, 16:15 UTC | Jul 8, 18:15 UTC | 2h 0m |
| 2026-07-08 | CSH871 | PVG → MRS | Jul 8, 09:05 UTC | Jul 8, 11:05 UTC | 2h 0m |
| 2026-07-07 | CSH871 | PVG → MRS | Jul 7, 11:55 UTC | Jul 8, 05:50 UTC | 17h 55m |
| 2026-07-07 | CSH871 | PVG → MRS | Jul 7, 08:40 UTC | Jul 8, 05:50 UTC | 21h 10m |
| 2026-07-06 | CSH870 | BUD → PVG | Jul 6, 11:50 UTC | Jul 7, 06:30 UTC | 18h 40m |
| 2026-07-06 | CSH870 | BUD → PVG | Jul 6, 10:55 UTC | Jul 7, 06:30 UTC | 19h 35m |
| 2026-07-05 | CSH869 | PVG → BUD | Jul 5, 10:25 UTC | Jul 6, 05:10 UTC | 18h 45m |
| 2026-07-04 | CSH870 | BUD → PVG | Jul 4, 11:50 UTC | Jul 5, 08:55 UTC | 21h 5m |
| 2026-07-04 | CSH870 | BUD → PVG | Jul 4, 10:50 UTC | Jul 5, 08:55 UTC | 22h 5m |
| 2026-07-03 | CSH869 | PVG → BUD | Jul 3, 09:50 UTC | Jul 4, 05:20 UTC | 19h 30m |
| 2026-07-03 | CSH869 | PVG → BUD | Jul 3, 09:30 UTC | Jul 4, 05:20 UTC | 19h 50m |
| 2026-07-02 | CSH886 | - | Jul 2, 08:25 UTC | Jul 3, 07:45 UTC | 23h 20m |
| 2026-07-02 | CSH885 | - | Jul 2, 02:30 UTC | Jul 2, 06:35 UTC | 4h 5m |
| 2026-07-01 | CSH885 | - | Jul 1, 09:50 UTC | Jul 2, 06:35 UTC | 20h 45m |
| 2026-07-01 | CSH896 | - | Jul 1, 09:00 UTC | Jul 2, 06:35 UTC | 21h 35m |
| 2026-06-30 | CSH870 | BUD → PVG | Jun 30, 11:50 UTC | Jul 1, 07:25 UTC | 19h 35m |
| 2026-06-30 | CSH870 | BUD → PVG | Jun 30, 10:45 UTC | Jul 1, 07:25 UTC | 20h 40m |
| 2026-06-29 | CSH869 | PVG → BUD | Jun 29, 09:50 UTC | Jun 30, 05:20 UTC | 19h 31m |
| 2026-06-29 | CSH869 | PVG → BUD | Jun 29, 08:39 UTC | Jun 30, 05:20 UTC | 20h 41m |
| 2026-06-29 | CES738 | - | Jun 29, 05:20 UTC | Jun 29, 23:34 UTC | 18h 15m |
| 2026-06-29 | CES738 | - | Jun 29, 01:50 UTC | Jun 29, 23:34 UTC | 21h 45m |
| 2026-06-29 | CES738 | - | Jun 29, 01:20 UTC | Jun 29, 23:34 UTC | 22h 15m |
| 2026-06-28 | CES737 | - | Jun 28, 13:34 UTC | Jun 28, 22:29 UTC | 8h 55m |
| 2026-06-27 | CES737 | - | Jun 27, 22:49 UTC | Jun 28, 19:14 UTC | 20h 25m |
| 2026-06-27 | CSH892 | - | Jun 27, 17:49 UTC | Jun 28, 15:55 UTC | 22h 5m |
| 2026-06-27 | CSH892 | - | Jun 27, 17:14 UTC | Jun 28, 15:44 UTC | 22h 30m |
| 2026-06-26 | CSH891 | - | Jun 26, 10:25 UTC | Jun 27, 08:35 UTC | 22h 10m |
| 2026-06-26 | CES738 | - | Jun 26, 01:29 UTC | Jun 26, 10:25 UTC | 8h 55m |
| 2026-06-25 | CES737 | - | Jun 25, 08:30 UTC | Jun 25, 23:19 UTC | 14h 50m |
| 2026-06-24 | CSH870 | BUD → PVG | Jun 24, 11:50 UTC | Jun 25, 06:30 UTC | 18h 40m |
| 2026-06-24 | CSH870 | BUD → PVG | Jun 24, 10:35 UTC | Jun 25, 06:30 UTC | 19h 55m |
| 2026-06-23 | CSH869 | PVG → BUD | Jun 23, 22:40 UTC | Jun 24, 04:39 UTC | 6h 0m |
| 2026-06-22 | CSH9253 | - | Jun 22, 12:10 UTC | Jun 22, 15:45 UTC | 3h 35m |
| 2026-06-16 | CSH824 | GMP → SHA | Jun 16, 12:14 UTC | Jun 16, 12:55 UTC | 40m |
| 2026-06-16 | CSH816 | HND → GMP | Jun 16, 04:45 UTC | Jun 16, 10:55 UTC | 6h 10m |
| 2026-06-15 | CSH815 | GMP → HND | Jun 15, 12:10 UTC | Jun 16, 03:10 UTC | 15h 0m |
| 2026-06-15 | CSH816 | - | Jun 15, 04:45 UTC | Jun 15, 10:55 UTC | 6h 10m |
| 2026-06-14 | CSH815 | GMP → HND | Jun 14, 12:15 UTC | Jun 15, 03:05 UTC | 14h 50m |
| 2026-06-14 | CSH816 | HND → SHA | Jun 14, 04:35 UTC | Jun 14, 10:55 UTC | 6h 20m |
| 2026-06-13 | CSH815 | GMP → HND | Jun 13, 12:10 UTC | Jun 14, 03:00 UTC | 14h 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 B-1112 page for operator, model, and routing details .