sensors Mode-S transponder
780CDE
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1706 · BOEING 737-800
- Hex
- 780CDE
- Octal
- 36006336
- Decimal
- 7,867,614
- Country
- CN
- Tail
- B-1706
- Type
- B738
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 17m ago
Current position
Country allocation
The ICAO 24-bit address 780CDE 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 |
|---|---|---|---|
| CXA877 | - | 9 | 2026-07-14 |
| CXA878 | - | 6 | 2026-07-14 |
| CXA886 | - | 4 | 2026-06-28 |
| CXA885 | - | 4 | 2026-06-27 |
| CXA866 | - | 4 | 2026-07-03 |
| CXA865 | - | 4 | 2026-07-03 |
| CXA897 | - | 2 | 2026-07-01 |
| CXA8722 | - | 2 | 2026-04-14 |
| CXA872 | Xiamen Airlines | 2 | 2026-06-05 |
| CXA8680 | Xiamen Airlines | 2 | 2026-05-15 |
| CXA8679 | Xiamen Airlines | 2 | 2026-05-15 |
| CXA844 | - | 2 | 2026-04-26 |
| CXA898 | Xiamen Airlines | 1 | 2026-05-26 |
| CXA893 | Xiamen Airlines | 1 | 2026-06-14 |
| CXA883 | Xiamen Airlines | 1 | 2026-04-19 |
| CXA880 | - | 1 | 2026-07-17 |
| CXA8793 | Xiamen Airlines | 1 | 2026-05-24 |
| CXA8790 | - | 1 | 2026-05-01 |
| CXA879 | Xiamen Airlines | 1 | 2026-07-17 |
| CXA8784 | Xiamen Airlines | 1 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | CXA8721 | - | Jul 18, 01:50 UTC | Jul 18, 09:30 UTC | 7h 41m |
| 2026-07-17 | CXA880 | - | Jul 17, 04:04 UTC | Jul 18, 01:54 UTC | 21h 50m |
| 2026-07-17 | CXA879 | FOC → TPE | Jul 17, 02:20 UTC | Jul 17, 02:50 UTC | 30m |
| 2026-07-15 | CXA8672 | - | Jul 15, 11:20 UTC | Jul 15, 11:35 UTC | 15m |
| 2026-07-14 | CXA878 | - | Jul 14, 12:35 UTC | Jul 14, 13:20 UTC | 45m |
| 2026-07-14 | CXA877 | - | Jul 14, 08:50 UTC | Jul 14, 09:40 UTC | 50m |
| 2026-07-08 | CXA878 | - | Jul 8, 11:55 UTC | Jul 8, 12:25 UTC | 30m |
| 2026-07-08 | CXA877 | - | Jul 8, 09:25 UTC | Jul 8, 10:10 UTC | 45m |
| 2026-07-04 | CXA8650 | BKI → FOC | Jul 4, 05:00 UTC | Jul 4, 06:50 UTC | 1h 50m |
| 2026-07-04 | CXA8649 | FOC → BKI | Jul 4, 03:05 UTC | Jul 4, 03:35 UTC | 30m |
| 2026-07-03 | CXA866 | - | Jul 3, 07:50 UTC | Jul 3, 11:05 UTC | 3h 15m |
| 2026-07-03 | CXA865 | - | Jul 3, 03:00 UTC | Jul 3, 06:10 UTC | 3h 10m |
| 2026-07-02 | CXA866 | - | Jul 2, 07:45 UTC | Jul 2, 08:10 UTC | 25m |
| 2026-07-02 | CXA865 | - | Jul 2, 02:50 UTC | Jul 2, 06:20 UTC | 3h 30m |
| 2026-07-01 | CXA865 | - | Jul 1, 10:00 UTC | Jul 2, 06:20 UTC | 20h 20m |
| 2026-07-01 | CXA897 | - | Jul 1, 07:55 UTC | Jul 1, 08:25 UTC | 30m |
| 2026-06-30 | CXA848 | - | Jun 30, 06:55 UTC | Jun 30, 07:25 UTC | 30m |
| 2026-06-30 | CXA847 | - | Jun 30, 04:45 UTC | Jun 30, 05:20 UTC | 35m |
| 2026-06-28 | CXA886 | - | Jun 28, 01:04 UTC | Jun 28, 04:25 UTC | 3h 20m |
| 2026-06-27 | CXA885 | - | Jun 27, 10:40 UTC | Jun 27, 14:14 UTC | 3h 35m |
| 2026-06-15 | CXA886 | - | Jun 15, 01:15 UTC | Jun 15, 01:40 UTC | 25m |
| 2026-06-14 | CXA885 | - | Jun 14, 07:55 UTC | Jun 14, 14:25 UTC | 6h 30m |
| 2026-06-14 | CXA893 | FOC → MFM | Jun 14, 02:00 UTC | Jun 14, 02:25 UTC | 25m |
| 2026-06-08 | CXA886 | SIN → XMN | Jun 8, 01:10 UTC | Jun 8, 04:35 UTC | 3h 25m |
| 2026-06-07 | CXA885 | XMN → SIN | Jun 7, 01:55 UTC | Jun 7, 13:55 UTC | 12h 0m |
| 2026-06-06 | CXA886 | SIN → XMN | Jun 6, 01:05 UTC | Jun 6, 01:30 UTC | 25m |
| 2026-06-05 | CXA885 | XMN → SIN | Jun 5, 12:55 UTC | Jun 5, 16:00 UTC | 3h 5m |
| 2026-06-05 | CXA872 | ICN → XMN | Jun 5, 07:35 UTC | Jun 5, 07:50 UTC | 15m |
| 2026-06-05 | CXA872 | ICN → XMN | Jun 5, 05:00 UTC | Jun 5, 05:30 UTC | 30m |
| 2026-06-05 | CXA871 | - | Jun 5, 03:00 UTC | Jun 5, 03:25 UTC | 25m |
| 2026-05-31 | CXA8325 | FOC → CAN | May 31, 08:30 UTC | May 31, 08:45 UTC | 15m |
| 2026-05-29 | CXA866 | SIN → FOC | May 29, 12:00 UTC | May 29, 12:25 UTC | 25m |
| 2026-05-29 | CXA866 | SIN → FOC | May 29, 08:10 UTC | May 29, 08:40 UTC | 30m |
| 2026-05-29 | CXA865 | FOC → SIN | May 29, 02:40 UTC | May 29, 06:00 UTC | 3h 20m |
| 2026-05-26 | CXA898 | KUL → FOC | May 26, 09:55 UTC | May 26, 10:10 UTC | 15m |
| 2026-05-26 | CXA897 | FOC → KUL | May 26, 05:15 UTC | May 26, 08:24 UTC | 3h 10m |
| 2026-05-24 | CXA8784 | HAK → FOC | May 24, 14:10 UTC | May 24, 14:25 UTC | 15m |
| 2026-05-24 | CXA8783 | FOC → HAK | May 24, 10:30 UTC | May 24, 11:30 UTC | 1h 0m |
| 2026-05-24 | CXA8793 | FOC → NNG | May 24, 04:30 UTC | May 24, 07:40 UTC | 3h 10m |
| 2026-05-18 | CXA878 | ICN → FOC | May 18, 11:40 UTC | May 18, 12:10 UTC | 30m |
| 2026-05-18 | CXA877 | FOC → ICN | May 18, 07:40 UTC | May 18, 09:35 UTC | 1h 55m |
| 2026-05-15 | CXA8680 | KHH → FOC | May 15, 11:55 UTC | May 15, 12:15 UTC | 20m |
| 2026-05-15 | CXA8679 | FOC → KHH | May 15, 10:00 UTC | May 15, 10:20 UTC | 20m |
| 2026-05-10 | CXA878 | ICN → FOC | May 10, 12:00 UTC | May 10, 12:19 UTC | 20m |
| 2026-05-10 | CXA877 | FOC → ICN | May 10, 08:45 UTC | May 10, 09:15 UTC | 30m |
| 2026-05-01 | CXA8790 | - | May 1, 23:40 UTC | May 2, 05:30 UTC | 5h 50m |
| 2026-05-01 | CXA8682 | MFM → XMN | May 1, 07:15 UTC | May 1, 07:30 UTC | 15m |
| 2026-05-01 | CXA8681 | XMN → MFM | May 1, 05:30 UTC | May 1, 05:45 UTC | 15m |
| 2026-04-29 | CXA8331 | SHA → SZX | Apr 29, 16:30 UTC | Apr 29, 16:40 UTC | 10m |
| 2026-04-29 | CXA8377 | SHA → SZX | Apr 29, 10:30 UTC | Apr 29, 10:40 UTC | 10m |
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-1706 page for operator, model, and routing details .