sensors Mode-S transponder
781FF8
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32FN · AIRBUS A-321neo
- Hex
- 781FF8
- Octal
- 36017770
- Decimal
- 7,872,504
- Country
- CN
- Tail
- B-32FN
- Type
- A21N
- Flights observed
- 68
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 21:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 781FF8 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 |
|---|---|---|---|
| CXA8350 | - | 6 | 2026-07-22 |
| CXA8349 | Xiamen Airlines | 5 | 2026-07-22 |
| CXA8321 | - | 5 | 2026-07-05 |
| CXA887 | Xiamen Airlines | 4 | 2026-07-26 |
| CXA8070 | Xiamen Airlines | 4 | 2026-07-20 |
| CXA888 | Xiamen Airlines | 3 | 2026-07-26 |
| CXA854 | - | 3 | 2026-06-19 |
| CXA853 | - | 3 | 2026-06-18 |
| CXA834 | - | 3 | 2026-06-23 |
| CXA8335 | Xiamen Airlines | 3 | 2026-06-05 |
| CXA833 | - | 3 | 2026-06-23 |
| CXA8812 | - | 2 | 2026-07-18 |
| CXA863 | Xiamen Airlines | 2 | 2026-06-20 |
| CXA8339 | - | 2 | 2026-07-06 |
| CXA8784 | Xiamen Airlines | 1 | 2026-04-29 |
| CXA8783 | Xiamen Airlines | 1 | 2026-04-29 |
| CXA864 | Xiamen Airlines | 1 | 2026-06-20 |
| CXA8547 | Xiamen Airlines | 1 | 2026-04-26 |
| CXA8535 | - | 1 | 2026-05-07 |
| CXA8511 | - | 1 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CXA844 | - | Jul 26, 19:30 UTC | Jul 26, 21:45 UTC | 2h 15m |
| 2026-07-26 | CXA843 | - | Jul 26, 06:55 UTC | Jul 26, 17:35 UTC | 10h 40m |
| 2026-07-26 | CXA888 | TPE → XMN | Jul 26, 03:50 UTC | Jul 26, 05:00 UTC | 1h 10m |
| 2026-07-26 | CXA887 | XMN → TPE | Jul 26, 00:55 UTC | Jul 26, 02:15 UTC | 1h 20m |
| 2026-07-24 | CXA8106 | - | Jul 24, 11:20 UTC | Jul 24, 23:35 UTC | 12h 15m |
| 2026-07-24 | CXA8105 | XMN → PKX | Jul 24, 09:10 UTC | Jul 24, 09:25 UTC | 15m |
| 2026-07-24 | CXA8511 | - | Jul 24, 01:35 UTC | Jul 24, 02:15 UTC | 40m |
| 2026-07-22 | CXA8350 | - | Jul 22, 15:30 UTC | Jul 22, 15:40 UTC | 10m |
| 2026-07-22 | CXA8349 | PKX → SZX | Jul 22, 11:55 UTC | Jul 22, 12:10 UTC | 15m |
| 2026-07-21 | CXA8350 | - | Jul 21, 14:25 UTC | Jul 21, 14:40 UTC | 15m |
| 2026-07-21 | CXA8349 | PKX → SZX | Jul 21, 12:45 UTC | Jul 21, 13:00 UTC | 15m |
| 2026-07-20 | CXA8070 | CGQ → HGH | Jul 20, 13:00 UTC | Jul 20, 13:45 UTC | 45m |
| 2026-07-18 | CXA8812 | - | Jul 18, 12:40 UTC | Jul 19, 06:40 UTC | 18h 0m |
| 2026-07-18 | CXA8812 | - | Jul 18, 09:15 UTC | Jul 19, 06:40 UTC | 21h 25m |
| 2026-07-18 | CXA8395 | PKX → CAN | Jul 18, 02:14 UTC | Jul 18, 02:35 UTC | 20m |
| 2026-07-14 | CXA8070 | - | Jul 14, 12:40 UTC | Jul 15, 04:25 UTC | 15h 44m |
| 2026-07-09 | CXA8070 | - | Jul 9, 13:15 UTC | Jul 9, 14:05 UTC | 50m |
| 2026-07-08 | CXA8359 | - | Jul 8, 09:50 UTC | Jul 8, 10:30 UTC | 40m |
| 2026-07-07 | CXA8437 | - | Jul 7, 11:55 UTC | Jul 8, 01:50 UTC | 13h 55m |
| 2026-07-07 | CXA8394 | - | Jul 7, 05:15 UTC | Jul 7, 05:30 UTC | 15m |
| 2026-07-06 | CXA8339 | - | Jul 6, 13:35 UTC | Jul 6, 13:50 UTC | 15m |
| 2026-07-05 | CXA8321 | - | Jul 5, 00:40 UTC | Jul 5, 04:25 UTC | 3h 45m |
| 2026-07-03 | CXA8070 | - | Jul 3, 13:20 UTC | Jul 3, 14:05 UTC | 45m |
| 2026-06-27 | CXA8321 | - | Jun 27, 00:29 UTC | Jun 27, 14:09 UTC | 13h 40m |
| 2026-06-23 | CXA834 | - | Jun 23, 10:55 UTC | Jun 23, 13:15 UTC | 2h 20m |
| 2026-06-23 | CXA833 | - | Jun 23, 06:44 UTC | Jun 23, 09:29 UTC | 2h 45m |
| 2026-06-23 | CXA888 | - | Jun 23, 03:54 UTC | Jun 23, 04:19 UTC | 25m |
| 2026-06-23 | CXA887 | - | Jun 23, 01:30 UTC | Jun 23, 01:59 UTC | 30m |
| 2026-06-20 | CXA864 | SIN → HGH | Jun 20, 13:04 UTC | Jun 20, 15:19 UTC | 2h 15m |
| 2026-06-20 | CXA863 | HGH → SIN | Jun 20, 08:49 UTC | Jun 20, 11:14 UTC | 2h 25m |
| 2026-06-19 | CXA854 | - | Jun 19, 05:45 UTC | Jun 19, 08:24 UTC | 2h 40m |
| 2026-06-18 | CXA853 | - | Jun 18, 13:40 UTC | Jun 19, 03:39 UTC | 13h 59m |
| 2026-06-18 | CXA863 | HGH → SIN | Jun 18, 09:15 UTC | Jun 18, 12:05 UTC | 2h 50m |
| 2026-06-06 | CXA8350 | SZX → PKX | Jun 6, 15:50 UTC | Jun 6, 15:59 UTC | 10m |
| 2026-06-06 | CXA8349 | PKX → SZX | Jun 6, 13:25 UTC | Jun 6, 13:34 UTC | 10m |
| 2026-06-05 | CXA8335 | PKX → SZX | Jun 5, 03:00 UTC | Jun 5, 03:20 UTC | 20m |
| 2026-05-25 | CXA8322 | SYX → HGH | May 25, 04:15 UTC | May 25, 04:25 UTC | 10m |
| 2026-05-22 | CXA8307 | XMN → SYX | May 22, 09:00 UTC | May 22, 13:55 UTC | 4h 55m |
| 2026-05-21 | CXA835Z | - | May 21, 05:15 UTC | May 21, 05:25 UTC | 10m |
| 2026-05-19 | CXA8350 | SZX → PKX | May 19, 14:10 UTC | May 19, 14:20 UTC | 10m |
| 2026-05-19 | CXA8349 | PKX → SZX | May 19, 12:00 UTC | May 19, 12:15 UTC | 15m |
| 2026-05-17 | CXA8339 | PKX → CAN | May 17, 10:10 UTC | May 17, 10:25 UTC | 15m |
| 2026-05-16 | CXA888 | TPE → XMN | May 16, 03:15 UTC | May 16, 03:45 UTC | 30m |
| 2026-05-16 | CXA887 | XMN → TPE | May 16, 01:05 UTC | May 16, 01:30 UTC | 25m |
| 2026-05-14 | CXA8388 | SZX → HGH | May 14, 07:15 UTC | May 14, 07:30 UTC | 15m |
| 2026-05-12 | CXA834 | BKK → XMN | May 12, 10:50 UTC | May 12, 13:05 UTC | 2h 15m |
| 2026-05-12 | CXA833 | XMN → BKK | May 12, 03:20 UTC | May 12, 09:10 UTC | 5h 50m |
| 2026-05-07 | CXA8535 | - | May 7, 02:00 UTC | May 7, 02:15 UTC | 15m |
| 2026-05-06 | CXA834 | BKK → XMN | May 6, 10:50 UTC | May 6, 13:10 UTC | 2h 20m |
| 2026-05-06 | CXA833 | XMN → BKK | May 6, 03:25 UTC | May 6, 09:15 UTC | 5h 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-32FN page for operator, model, and routing details .