sensors Mode-S transponder
780E4B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6488 · BOEING 737-800
- Hex
- 780E4B
- Octal
- 36007113
- Decimal
- 7,867,979
- Country
- CN
- Tail
- B-6488
- Type
- B738
- Flights observed
- 59
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780E4B 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 |
|---|---|---|---|
| CXA8704 | Xiamen Airlines | 3 | 2026-05-28 |
| CXA8703 | Xiamen Airlines | 3 | 2026-05-28 |
| CXA8317 | Xiamen Airlines | 3 | 2026-06-02 |
| CXA818 | - | 3 | 2026-06-03 |
| CXA817 | - | 3 | 2026-06-03 |
| CXA871 | - | 2 | 2026-05-14 |
| CXA8648 | Xiamen Airlines | 2 | 2026-06-11 |
| CXA8647 | Xiamen Airlines | 2 | 2026-06-11 |
| CXA8318 | Xiamen Airlines | 2 | 2026-05-18 |
| CXA8304 | - | 2 | 2026-06-13 |
| CXA8882 | Xiamen Airlines | 1 | 2026-05-16 |
| CXA886 | Xiamen Airlines | 1 | 2026-05-02 |
| CXA885 | Xiamen Airlines | 1 | 2026-04-30 |
| CXA884 | - | 1 | 2026-06-14 |
| CXA883 | - | 1 | 2026-06-14 |
| CXA8827 | Xiamen Airlines | 1 | 2026-05-03 |
| CXA8765 | Xiamen Airlines | 1 | 2026-06-10 |
| CXA8720 | Xiamen Airlines | 1 | 2026-05-24 |
| CXA872 | Xiamen Airlines | 1 | 2026-05-14 |
| CXA8719 | Xiamen Airlines | 1 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-15 | CXA8116 | PKX → FOC | Jun 15, 06:20 UTC | Jun 15, 07:05 UTC | 45m |
| 2026-06-14 | CXA884 | - | Jun 14, 12:40 UTC | Jun 14, 13:20 UTC | 40m |
| 2026-06-14 | CXA883 | - | Jun 14, 10:55 UTC | Jun 14, 11:30 UTC | 35m |
| 2026-06-13 | CXA8304 | - | Jun 13, 04:15 UTC | Jun 13, 04:25 UTC | 10m |
| 2026-06-11 | CXA8648 | HKG → FOC | Jun 11, 13:40 UTC | Jun 11, 15:20 UTC | 1h 40m |
| 2026-06-11 | CXA8647 | FOC → HKG | Jun 11, 09:55 UTC | Jun 11, 12:15 UTC | 2h 20m |
| 2026-06-10 | CXA8765 | HGH → WUH | Jun 10, 10:00 UTC | Jun 10, 10:10 UTC | 10m |
| 2026-06-07 | CXA8020 | - | Jun 7, 06:45 UTC | Jun 7, 10:25 UTC | 3h 40m |
| 2026-06-07 | CXA8019 | - | Jun 7, 01:35 UTC | Jun 7, 05:00 UTC | 3h 25m |
| 2026-06-05 | CXA8615 | - | Jun 5, 10:40 UTC | Jun 6, 00:15 UTC | 13h 35m |
| 2026-06-03 | CXA818 | - | Jun 3, 10:10 UTC | Jun 3, 10:40 UTC | 30m |
| 2026-06-03 | CXA817 | - | Jun 3, 07:15 UTC | Jun 3, 08:30 UTC | 1h 15m |
| 2026-06-02 | CXA8317 | SHA → SZX | Jun 2, 09:50 UTC | Jun 2, 10:25 UTC | 35m |
| 2026-06-02 | CXA8305 | - | Jun 2, 00:20 UTC | Jun 2, 00:45 UTC | 25m |
| 2026-06-01 | CXA8304 | SZX → CKG | Jun 1, 04:05 UTC | Jun 1, 04:15 UTC | 10m |
| 2026-05-30 | CXA8648 | HKG → FOC | May 30, 13:20 UTC | May 30, 15:00 UTC | 1h 40m |
| 2026-05-30 | CXA8647 | FOC → HKG | May 30, 09:35 UTC | May 30, 11:30 UTC | 1h 55m |
| 2026-05-28 | CXA8704 | SIN → HGH | May 28, 07:30 UTC | May 28, 10:40 UTC | 3h 10m |
| 2026-05-28 | CXA8703 | HGH → SIN | May 28, 01:15 UTC | May 28, 04:50 UTC | 3h 35m |
| 2026-05-27 | CXA8703 | HGH → SIN | May 27, 10:35 UTC | May 28, 04:50 UTC | 18h 15m |
| 2026-05-27 | CXA8704 | SIN → HGH | May 27, 07:20 UTC | May 28, 04:50 UTC | 21h 30m |
| 2026-05-26 | CXA8703 | HGH → SIN | May 26, 10:05 UTC | May 27, 04:39 UTC | 18h 35m |
| 2026-05-26 | CXA8704 | SIN → HGH | May 26, 06:54 UTC | May 26, 10:44 UTC | 3h 50m |
| 2026-05-25 | CXA8658 | MNL → HGH | May 25, 13:05 UTC | May 26, 05:10 UTC | 16h 4m |
| 2026-05-25 | CXA8657 | HGH → MNL | May 25, 10:25 UTC | May 25, 11:50 UTC | 1h 25m |
| 2026-05-24 | CXA8720 | MFM → HGH | May 24, 10:50 UTC | May 25, 10:45 UTC | 23h 55m |
| 2026-05-24 | CXA8719 | HGH → MFM | May 24, 08:45 UTC | May 24, 09:10 UTC | 25m |
| 2026-05-22 | CXA8331 | SHA → SZX | May 22, 17:10 UTC | May 22, 17:35 UTC | 25m |
| 2026-05-22 | CXA8332 | SZX → SHA | May 22, 12:30 UTC | May 22, 12:40 UTC | 10m |
| 2026-05-22 | CXA8378 | SZX → SHA | May 22, 02:50 UTC | May 22, 03:30 UTC | 40m |
| 2026-05-22 | CXA8383 | KHN → SZX | May 22, 00:25 UTC | May 22, 00:45 UTC | 20m |
| 2026-05-21 | CXA8388 | SZX → HGH | May 21, 08:10 UTC | May 21, 08:20 UTC | 10m |
| 2026-05-21 | CXA831S | - | May 21, 06:20 UTC | May 21, 06:35 UTC | 15m |
| 2026-05-20 | CXA8317 | SHA → SZX | May 20, 11:25 UTC | May 20, 12:10 UTC | 45m |
| 2026-05-18 | CXA8318 | SZX → SHA | May 18, 12:40 UTC | May 18, 12:50 UTC | 10m |
| 2026-05-18 | CXA8317 | SHA → SZX | May 18, 09:35 UTC | May 18, 09:55 UTC | 20m |
| 2026-05-17 | - | - | May 17, 22:30 UTC | May 17, 22:40 UTC | 10m |
| 2026-05-17 | CXA8666 | KHH → XMN | May 17, 12:20 UTC | May 17, 12:45 UTC | 25m |
| 2026-05-17 | CXA8665 | XMN → KHH | May 17, 10:50 UTC | May 17, 11:10 UTC | 20m |
| 2026-05-16 | CXA8882 | ZUH → SHA | May 16, 13:25 UTC | May 16, 13:41 UTC | 15m |
| 2026-05-16 | CXA8371 | SHA → SZX | May 16, 01:40 UTC | May 16, 02:35 UTC | 55m |
| 2026-05-15 | CXA8318 | SZX → SHA | May 15, 14:40 UTC | May 15, 14:55 UTC | 14m |
| 2026-05-14 | CXA872 | ICN → XMN | May 14, 04:45 UTC | May 14, 14:35 UTC | 9h 50m |
| 2026-05-14 | CXA871 | - | May 14, 02:25 UTC | May 14, 03:05 UTC | 40m |
| 2026-05-14 | CXA871 | - | May 14, 00:45 UTC | May 14, 00:55 UTC | 10m |
| 2026-05-13 | CXA844 | - | May 13, 19:20 UTC | May 13, 21:30 UTC | 2h 10m |
| 2026-05-13 | CXA843 | - | May 13, 14:45 UTC | May 13, 17:35 UTC | 2h 50m |
| 2026-05-12 | CXA818 | - | May 12, 10:05 UTC | May 12, 11:05 UTC | 1h 0m |
| 2026-05-12 | CXA817 | - | May 12, 06:55 UTC | May 12, 08:05 UTC | 1h 10m |
| 2026-05-11 | CXA818 | - | May 11, 10:05 UTC | May 11, 11:15 UTC | 1h 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-6488 page for operator, model, and routing details .