sensors Mode-S transponder
781EAD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32CY · AIRBUS A-321neo
- Hex
- 781EAD
- Octal
- 36017255
- Decimal
- 7,872,173
- Country
- CN
- Tail
- B-32CY
- Type
- A21N
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 781EAD 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 |
|---|---|---|---|
| CXA887 | Xiamen Airlines | 6 | 2026-05-22 |
| CXA834 | Xiamen Airlines | 6 | 2026-05-11 |
| CXA833 | Xiamen Airlines | 5 | 2026-05-11 |
| CXA8321 | Xiamen Airlines | 4 | 2026-05-18 |
| CXA8536 | - | 3 | 2026-05-23 |
| CXA8397 | - | 3 | 2026-05-10 |
| CXA888 | Xiamen Airlines | 2 | 2026-05-22 |
| CXA8398 | - | 2 | 2026-05-03 |
| CXA8375 | Xiamen Airlines | 2 | 2026-04-21 |
| CXA8350 | Xiamen Airlines | 2 | 2026-05-15 |
| CXA8816 | Xiamen Airlines | 1 | 2026-05-18 |
| CXA864 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA863 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA854 | Xiamen Airlines | 1 | 2026-04-21 |
| CXA853 | Xiamen Airlines | 1 | 2026-04-21 |
| CXA8524 | Xiamen Airlines | 1 | 2026-05-25 |
| CXA8387 | Xiamen Airlines | 1 | 2026-04-16 |
| CXA8361 | Xiamen Airlines | 1 | 2026-05-02 |
| CXA8360 | Xiamen Airlines | 1 | 2026-04-20 |
| CXA8349 | Xiamen Airlines | 1 | 2026-05-14 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-25 | CXA8524 | TAO → FOC | May 25, 11:10 UTC | May 25, 11:45 UTC | 35m |
| 2026-05-23 | CXA8536 | - | May 23, 02:05 UTC | May 23, 07:20 UTC | 5h 15m |
| 2026-05-22 | CXA8536 | - | May 22, 07:20 UTC | May 23, 07:15 UTC | 23h 54m |
| 2026-05-22 | CXA888 | TPE → XMN | May 22, 03:45 UTC | May 23, 02:05 UTC | 22h 20m |
| 2026-05-22 | CXA887 | XMN → TPE | May 22, 01:20 UTC | May 22, 01:50 UTC | 30m |
| 2026-05-18 | CXA8816 | SYX → XMN | May 18, 13:00 UTC | May 19, 09:15 UTC | 20h 14m |
| 2026-05-18 | CXA8321 | HGH → SYX | May 18, 00:30 UTC | May 18, 13:05 UTC | 12h 35m |
| 2026-05-15 | CXA8350 | SZX → PKX | May 15, 16:10 UTC | May 15, 16:25 UTC | 15m |
| 2026-05-15 | - | - | May 15, 13:50 UTC | May 15, 14:10 UTC | 20m |
| 2026-05-14 | CXA8350 | SZX → PKX | May 14, 15:20 UTC | May 14, 15:30 UTC | 10m |
| 2026-05-14 | CXA8349 | PKX → SZX | May 14, 13:01 UTC | May 14, 13:25 UTC | 25m |
| 2026-05-12 | CXA8536 | - | May 12, 06:45 UTC | May 12, 07:25 UTC | 40m |
| 2026-05-11 | CXA834 | BKK → XMN | May 11, 11:20 UTC | May 12, 07:25 UTC | 20h 5m |
| 2026-05-11 | CXA834 | BKK → XMN | May 11, 10:55 UTC | May 12, 07:25 UTC | 20h 31m |
| 2026-05-11 | CXA833 | XMN → BKK | May 11, 03:20 UTC | May 11, 09:10 UTC | 5h 50m |
| 2026-05-11 | CXA887 | XMN → TPE | May 11, 01:15 UTC | May 11, 01:40 UTC | 25m |
| 2026-05-10 | CXA8397 | - | May 10, 00:34 UTC | May 10, 04:29 UTC | 3h 55m |
| 2026-05-08 | CXA8307 | XMN → SYX | May 8, 03:35 UTC | May 8, 13:20 UTC | 9h 45m |
| 2026-05-08 | CXA887 | XMN → TPE | May 8, 01:14 UTC | May 8, 01:45 UTC | 30m |
| 2026-05-07 | CXA834 | BKK → XMN | May 7, 11:00 UTC | May 7, 13:20 UTC | 2h 20m |
| 2026-05-07 | CXA833 | XMN → BKK | May 7, 03:25 UTC | May 7, 09:35 UTC | 6h 10m |
| 2026-05-07 | CXA887 | XMN → TPE | May 7, 01:10 UTC | May 7, 01:50 UTC | 40m |
| 2026-05-05 | CXA8321 | HGH → SYX | May 5, 00:35 UTC | May 5, 04:25 UTC | 3h 50m |
| 2026-05-04 | CXA8321 | HGH → SYX | May 4, 04:00 UTC | May 5, 00:55 UTC | 20h 56m |
| 2026-05-04 | CXA8321 | HGH → SYX | May 4, 00:34 UTC | May 4, 04:05 UTC | 3h 30m |
| 2026-05-03 | CXA8398 | - | May 3, 04:20 UTC | May 4, 00:50 UTC | 20h 30m |
| 2026-05-02 | CXA8397 | - | May 2, 13:45 UTC | May 3, 04:40 UTC | 14h 54m |
| 2026-05-02 | CXA8361 | XMN → HAK | May 2, 10:30 UTC | May 2, 10:55 UTC | 25m |
| 2026-04-30 | CXA834 | BKK → XMN | Apr 30, 11:15 UTC | Apr 30, 13:25 UTC | 2h 10m |
| 2026-04-30 | CXA833 | XMN → BKK | Apr 30, 03:30 UTC | Apr 30, 09:45 UTC | 6h 15m |
| 2026-04-29 | CXA834 | BKK → XMN | Apr 29, 11:10 UTC | Apr 30, 01:35 UTC | 14h 24m |
| 2026-04-29 | CXA833 | XMN → BKK | Apr 29, 09:00 UTC | Apr 29, 09:35 UTC | 35m |
| 2026-04-29 | CXA888 | TPE → XMN | Apr 29, 03:45 UTC | Apr 29, 04:20 UTC | 35m |
| 2026-04-28 | CXA864 | SIN → HGH | Apr 28, 13:50 UTC | Apr 29, 02:05 UTC | 12h 15m |
| 2026-04-28 | CXA863 | HGH → SIN | Apr 28, 09:55 UTC | Apr 28, 12:30 UTC | 2h 35m |
| 2026-04-23 | CXA834 | BKK → XMN | Apr 23, 11:05 UTC | Apr 23, 13:20 UTC | 2h 15m |
| 2026-04-23 | CXA833 | XMN → BKK | Apr 23, 03:40 UTC | Apr 23, 09:50 UTC | 6h 10m |
| 2026-04-23 | CXA887 | XMN → TPE | Apr 23, 01:20 UTC | Apr 23, 01:45 UTC | 25m |
| 2026-04-22 | CXA887 | XMN → TPE | Apr 22, 03:20 UTC | Apr 23, 01:45 UTC | 22h 25m |
| 2026-04-21 | CXA8375 | XMN → NNG | Apr 21, 10:35 UTC | Apr 22, 03:20 UTC | 16h 45m |
| 2026-04-21 | CXA8375 | XMN → NNG | Apr 21, 07:45 UTC | Apr 22, 03:20 UTC | 19h 35m |
| 2026-04-21 | CXA854 | BKK → XMN | Apr 21, 05:45 UTC | Apr 22, 03:15 UTC | 21h 30m |
| 2026-04-21 | CXA853 | XMN → BKK | Apr 21, 01:45 UTC | Apr 21, 04:10 UTC | 2h 25m |
| 2026-04-20 | CXA8360 | NNG → XMN | Apr 20, 14:15 UTC | Apr 20, 14:25 UTC | 10m |
| 2026-04-16 | - | - | Apr 16, 15:00 UTC | Apr 16, 15:10 UTC | 10m |
| 2026-04-16 | CXA8387 | HGH → SZX | Apr 16, 06:05 UTC | Apr 16, 06:29 UTC | 25m |
| 2026-04-13 | CXA8398 | - | Apr 13, 05:10 UTC | Apr 13, 05:30 UTC | 20m |
| 2026-04-13 | CXA8397 | - | Apr 13, 01:30 UTC | Apr 13, 01:55 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-32CY page for operator, model, and routing details .