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