sensors Mode-S transponder
781FB5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32F3 · AIRBUS A-321neo
- Hex
- 781FB5
- Octal
- 36017665
- Decimal
- 7,872,437
- Country
- CN
- Tail
- B-32F3
- Type
- A21N
- Flights observed
- 56
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781FB5 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CXA851 | Xiamen Airlines | 16 | 2026-06-01 |
| CXA852 | Xiamen Airlines | 12 | 2026-06-01 |
| CXA887 | Xiamen Airlines | 4 | 2026-05-30 |
| CXA834 | Xiamen Airlines | 4 | 2026-05-31 |
| CXA833 | Xiamen Airlines | 4 | 2026-05-31 |
| CXA854 | Xiamen Airlines | 3 | 2026-05-10 |
| CXA853 | Xiamen Airlines | 3 | 2026-05-10 |
| CXA888 | Xiamen Airlines | 1 | 2026-05-24 |
| CXA8536 | - | 1 | 2026-04-26 |
| CXA8431 | - | 1 | 2026-05-17 |
| CXA8388 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA8387 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA8362 | Xiamen Airlines | 1 | 2026-04-22 |
| CXA8361 | Xiamen Airlines | 1 | 2026-05-06 |
| CXA8311 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA8308 | Xiamen Airlines | 1 | 2026-05-28 |
| CXA8307 | Xiamen Airlines | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | CXA852 | SIN → XMN | Jun 1, 07:45 UTC | Jun 1, 10:30 UTC | 2h 45m |
| 2026-06-01 | CXA851 | XMN → SIN | Jun 1, 02:55 UTC | Jun 1, 05:45 UTC | 2h 50m |
| 2026-05-31 | CXA834 | BKK → XMN | May 31, 11:05 UTC | May 31, 13:30 UTC | 2h 25m |
| 2026-05-31 | CXA833 | XMN → BKK | May 31, 00:40 UTC | May 31, 09:30 UTC | 8h 50m |
| 2026-05-30 | CXA834 | BKK → XMN | May 30, 10:50 UTC | May 30, 13:15 UTC | 2h 25m |
| 2026-05-30 | CXA833 | XMN → BKK | May 30, 03:25 UTC | May 30, 09:10 UTC | 5h 45m |
| 2026-05-30 | CXA887 | XMN → TPE | May 30, 01:15 UTC | May 30, 01:40 UTC | 25m |
| 2026-05-29 | CXA834 | BKK → XMN | May 29, 10:55 UTC | May 29, 13:20 UTC | 2h 25m |
| 2026-05-29 | CXA833 | XMN → BKK | May 29, 03:20 UTC | May 29, 09:15 UTC | 5h 55m |
| 2026-05-29 | CXA887 | XMN → TPE | May 29, 01:10 UTC | May 29, 01:40 UTC | 30m |
| 2026-05-28 | CXA8308 | SYX → XMN | May 28, 13:40 UTC | May 28, 14:00 UTC | 20m |
| 2026-05-28 | CXA8307 | XMN → SYX | May 28, 03:25 UTC | May 28, 11:10 UTC | 7h 45m |
| 2026-05-27 | CXA887 | XMN → TPE | May 27, 08:55 UTC | May 28, 01:45 UTC | 16h 50m |
| 2026-05-24 | CXA834 | BKK → XMN | May 24, 10:50 UTC | May 24, 13:10 UTC | 2h 20m |
| 2026-05-24 | CXA833 | XMN → BKK | May 24, 07:05 UTC | May 24, 09:35 UTC | 2h 30m |
| 2026-05-24 | CXA888 | TPE → XMN | May 24, 03:35 UTC | May 24, 04:45 UTC | 1h 10m |
| 2026-05-24 | CXA887 | XMN → TPE | May 24, 01:15 UTC | May 24, 01:45 UTC | 30m |
| 2026-05-19 | CXA852 | SIN → XMN | May 19, 07:50 UTC | May 19, 10:55 UTC | 3h 5m |
| 2026-05-17 | CXA8431 | - | May 17, 06:50 UTC | May 17, 07:00 UTC | 10m |
| 2026-05-12 | CXA852 | SIN → XMN | May 12, 07:55 UTC | May 12, 08:10 UTC | 15m |
| 2026-05-12 | CXA851 | XMN → SIN | May 12, 05:15 UTC | May 12, 05:30 UTC | 15m |
| 2026-05-10 | CXA854 | BKK → XMN | May 10, 05:34 UTC | May 10, 07:55 UTC | 2h 20m |
| 2026-05-10 | CXA853 | XMN → BKK | May 10, 01:24 UTC | May 10, 03:55 UTC | 2h 30m |
| 2026-05-08 | CXA854 | BKK → XMN | May 8, 05:39 UTC | May 8, 07:55 UTC | 2h 15m |
| 2026-05-08 | CXA853 | XMN → BKK | May 8, 01:14 UTC | May 8, 03:44 UTC | 2h 30m |
| 2026-05-06 | CXA8361 | XMN → HAK | May 6, 10:45 UTC | May 6, 13:55 UTC | 3h 10m |
| 2026-05-05 | CXA852 | SIN → XMN | May 5, 07:55 UTC | May 5, 08:10 UTC | 15m |
| 2026-05-05 | CXA851 | XMN → SIN | May 5, 05:15 UTC | May 5, 05:25 UTC | 10m |
| 2026-05-04 | CXA852 | SIN → XMN | May 4, 08:00 UTC | May 4, 08:15 UTC | 15m |
| 2026-05-04 | CXA851 | XMN → SIN | May 4, 05:20 UTC | May 4, 05:35 UTC | 15m |
| 2026-05-03 | CXA852 | SIN → XMN | May 3, 08:20 UTC | May 4, 05:35 UTC | 21h 15m |
| 2026-05-03 | CXA851 | XMN → SIN | May 3, 06:05 UTC | May 3, 06:35 UTC | 30m |
| 2026-05-03 | CXA851 | XMN → SIN | May 3, 02:55 UTC | May 3, 03:05 UTC | 10m |
| 2026-05-02 | CXA852 | SIN → XMN | May 2, 07:50 UTC | May 2, 08:10 UTC | 20m |
| 2026-05-02 | CXA851 | XMN → SIN | May 2, 05:20 UTC | May 2, 05:45 UTC | 25m |
| 2026-05-01 | CXA852 | SIN → XMN | May 1, 08:35 UTC | May 2, 05:45 UTC | 21h 10m |
| 2026-05-01 | CXA851 | XMN → SIN | May 1, 06:00 UTC | May 1, 06:25 UTC | 25m |
| 2026-04-30 | CXA851 | XMN → SIN | Apr 30, 08:00 UTC | May 1, 06:25 UTC | 22h 25m |
| 2026-04-30 | CXA851 | XMN → SIN | Apr 30, 05:30 UTC | Apr 30, 06:05 UTC | 35m |
| 2026-04-28 | CXA8388 | SZX → HGH | Apr 28, 06:40 UTC | Apr 28, 06:50 UTC | 10m |
| 2026-04-28 | CXA8387 | HGH → SZX | Apr 28, 04:50 UTC | Apr 28, 05:15 UTC | 25m |
| 2026-04-26 | CXA8536 | - | Apr 26, 06:35 UTC | Apr 26, 06:55 UTC | 20m |
| 2026-04-23 | CXA8311 | HGH → CAN | Apr 23, 15:50 UTC | Apr 23, 16:05 UTC | 15m |
| 2026-04-22 | CXA8362 | HAK → XMN | Apr 22, 13:55 UTC | Apr 22, 14:10 UTC | 15m |
| 2026-04-22 | CXA854 | BKK → XMN | Apr 22, 05:45 UTC | Apr 22, 11:25 UTC | 5h 40m |
| 2026-04-22 | CXA853 | XMN → BKK | Apr 22, 00:55 UTC | Apr 22, 03:45 UTC | 2h 50m |
| 2026-04-21 | CXA852 | SIN → XMN | Apr 21, 07:50 UTC | Apr 21, 09:10 UTC | 1h 20m |
| 2026-04-21 | CXA851 | XMN → SIN | Apr 21, 04:10 UTC | Apr 21, 05:30 UTC | 1h 20m |
| 2026-04-20 | CXA852 | SIN → XMN | Apr 20, 07:45 UTC | Apr 20, 09:10 UTC | 1h 25m |
| 2026-04-20 | CXA851 | XMN → SIN | Apr 20, 02:50 UTC | Apr 20, 06:10 UTC | 3h 20m |
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-32F3 page for operator, model, and routing details .