sensors Mode-S transponder
780E45
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6482 · BOEING 737-800
- Hex
- 780E45
- Octal
- 36007105
- Decimal
- 7,867,973
- Country
- CN
- Tail
- B-6482
- Type
- B738
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 11:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 780E45 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 |
|---|---|---|---|
| CXA871 | - | 4 | 2026-05-19 |
| CXA872 | Xiamen Airlines | 3 | 2026-04-18 |
| CXA8719 | Xiamen Airlines | 3 | 2026-06-03 |
| CXA883 | - | 2 | 2026-06-28 |
| CXA880 | - | 2 | 2026-07-05 |
| CXA8791 | - | 2 | 2026-07-23 |
| CXA879 | - | 2 | 2026-07-04 |
| CXA8720 | Xiamen Airlines | 2 | 2026-06-03 |
| CXA8704 | Xiamen Airlines | 2 | 2026-07-22 |
| CXA8703 | Xiamen Airlines | 2 | 2026-07-22 |
| CXA8650 | Xiamen Airlines | 2 | 2026-06-30 |
| CXA8649 | Xiamen Airlines | 2 | 2026-06-30 |
| CXA8377 | - | 2 | 2026-07-14 |
| CXA810 | - | 2 | 2026-06-29 |
| CXA897 | - | 1 | 2026-07-04 |
| CXA886 | - | 1 | 2026-07-16 |
| CXA885 | - | 1 | 2026-07-15 |
| CXA884 | Xiamen Airlines | 1 | 2026-05-09 |
| CXA882 | - | 1 | 2026-05-19 |
| CXA881 | - | 1 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CXA8509 | - | Jul 26, 09:00 UTC | Jul 26, 11:45 UTC | 2h 45m |
| 2026-07-25 | CXA8383 | KHN → SZX | Jul 25, 00:40 UTC | Jul 25, 00:55 UTC | 15m |
| 2026-07-24 | CXA8678 | KUL → HGH | Jul 24, 08:35 UTC | Jul 24, 12:20 UTC | 3h 45m |
| 2026-07-23 | CXA8677 | HGH → KUL | Jul 23, 14:25 UTC | Jul 24, 06:35 UTC | 16h 10m |
| 2026-07-23 | CXA8791 | - | Jul 23, 10:50 UTC | Jul 23, 11:35 UTC | 45m |
| 2026-07-22 | CXA8704 | SIN → HGH | Jul 22, 11:10 UTC | Jul 23, 04:45 UTC | 17h 35m |
| 2026-07-22 | CXA8703 | HGH → SIN | Jul 22, 04:55 UTC | Jul 22, 05:25 UTC | 30m |
| 2026-07-21 | CXA8704 | SIN → HGH | Jul 21, 07:30 UTC | Jul 22, 02:00 UTC | 18h 30m |
| 2026-07-21 | CXA8703 | HGH → SIN | Jul 21, 01:20 UTC | Jul 21, 05:10 UTC | 3h 50m |
| 2026-07-18 | CXA8363 | - | Jul 18, 11:05 UTC | Jul 18, 15:00 UTC | 3h 55m |
| 2026-07-18 | CXA8738 | - | Jul 18, 08:40 UTC | Jul 18, 08:55 UTC | 15m |
| 2026-07-18 | CXA8737 | XMN → SHS | Jul 18, 07:15 UTC | Jul 18, 07:25 UTC | 10m |
| 2026-07-16 | CXA886 | - | Jul 16, 01:10 UTC | Jul 16, 01:35 UTC | 25m |
| 2026-07-15 | CXA885 | - | Jul 15, 12:10 UTC | Jul 15, 15:15 UTC | 3h 5m |
| 2026-07-15 | CXA8682 | - | Jul 15, 09:10 UTC | Jul 15, 09:25 UTC | 15m |
| 2026-07-14 | CXA8377 | - | Jul 14, 01:55 UTC | Jul 14, 02:40 UTC | 45m |
| 2026-07-11 | CXA8377 | - | Jul 11, 02:25 UTC | Jul 11, 02:45 UTC | 20m |
| 2026-07-09 | CXA878 | - | Jul 9, 12:00 UTC | Jul 9, 12:40 UTC | 40m |
| 2026-07-09 | CXA877 | - | Jul 9, 09:30 UTC | Jul 9, 10:10 UTC | 40m |
| 2026-07-07 | CXA8722 | - | Jul 7, 04:00 UTC | Jul 7, 11:25 UTC | 7h 25m |
| 2026-07-05 | CXA880 | - | Jul 5, 03:45 UTC | Jul 5, 04:20 UTC | 35m |
| 2026-07-04 | CXA879 | - | Jul 4, 10:00 UTC | Jul 5, 02:10 UTC | 16h 10m |
| 2026-07-04 | CXA897 | - | Jul 4, 08:10 UTC | Jul 4, 08:35 UTC | 25m |
| 2026-06-30 | CXA8650 | BKI → FOC | Jun 30, 05:05 UTC | Jun 30, 07:35 UTC | 2h 30m |
| 2026-06-30 | CXA8649 | FOC → BKI | Jun 30, 00:55 UTC | Jun 30, 03:35 UTC | 2h 41m |
| 2026-06-29 | CXA810 | - | Jun 29, 07:20 UTC | Jun 30, 03:35 UTC | 20h 16m |
| 2026-06-29 | CXA810 | - | Jun 29, 06:34 UTC | Jun 30, 03:35 UTC | 21h 1m |
| 2026-06-28 | CXA809 | - | Jun 28, 13:14 UTC | Jun 29, 04:30 UTC | 15h 15m |
| 2026-06-28 | CXA883 | - | Jun 28, 11:55 UTC | Jun 28, 12:15 UTC | 20m |
| 2026-06-09 | CXA880 | TPE → FOC | Jun 9, 03:45 UTC | Jun 9, 04:15 UTC | 30m |
| 2026-06-09 | CXA879 | FOC → TPE | Jun 9, 01:10 UTC | Jun 9, 02:00 UTC | 50m |
| 2026-06-05 | CXA8792 | HAK → FOC | Jun 5, 14:35 UTC | Jun 5, 14:50 UTC | 15m |
| 2026-06-05 | CXA8791 | FOC → HAK | Jun 5, 11:30 UTC | Jun 5, 11:40 UTC | 10m |
| 2026-06-03 | CXA8720 | MFM → HGH | Jun 3, 10:50 UTC | Jun 3, 11:10 UTC | 20m |
| 2026-06-03 | CXA8719 | HGH → MFM | Jun 3, 08:15 UTC | Jun 3, 09:05 UTC | 50m |
| 2026-06-02 | CXA8719 | HGH → MFM | Jun 2, 09:25 UTC | Jun 3, 09:05 UTC | 23h 40m |
| 2026-05-29 | CXA8720 | MFM → HGH | May 29, 10:40 UTC | May 29, 11:00 UTC | 20m |
| 2026-05-29 | CXA8719 | HGH → MFM | May 29, 08:45 UTC | May 29, 09:15 UTC | 30m |
| 2026-05-28 | CXA8321 | HGH → SYX | May 28, 11:55 UTC | May 29, 04:25 UTC | 16h 30m |
| 2026-05-27 | CXA8316 | HAK → HGH | May 27, 00:55 UTC | May 27, 03:50 UTC | 2h 55m |
| 2026-05-21 | CXA8359 | XMN → NNG | May 21, 10:15 UTC | May 21, 10:35 UTC | 20m |
| 2026-05-21 | CXA8790 | - | May 21, 07:40 UTC | May 21, 08:15 UTC | 35m |
| 2026-05-19 | CXA882 | - | May 19, 11:40 UTC | May 19, 12:10 UTC | 30m |
| 2026-05-19 | CXA881 | - | May 19, 05:10 UTC | May 19, 10:20 UTC | 5h 10m |
| 2026-05-19 | CXA871 | - | May 19, 02:45 UTC | May 19, 03:30 UTC | 45m |
| 2026-05-18 | CXA828 | MNL → XMN | May 18, 04:05 UTC | May 18, 04:30 UTC | 25m |
| 2026-05-17 | CXA844 | - | May 17, 19:20 UTC | May 18, 02:20 UTC | 7h 0m |
| 2026-05-17 | CXA843 | - | May 17, 15:20 UTC | May 17, 17:35 UTC | 2h 15m |
| 2026-05-10 | CXA8666 | KHH → XMN | May 10, 12:40 UTC | May 10, 12:49 UTC | 10m |
| 2026-05-10 | CXA8665 | XMN → KHH | May 10, 11:00 UTC | May 10, 11:25 UTC | 25m |
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-6482 page for operator, model, and routing details .