sensors Mode-S transponder
782081
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32GA · AIRBUS A-321neo
- Hex
- 782081
- Octal
- 36020201
- Decimal
- 7,872,641
- Country
- CN
- Tail
- B-32GA
- Type
- A21N
- Flights observed
- 67
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 782081 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 |
|---|---|---|---|
| CXA851 | - | 11 | 2026-07-06 |
| CXA834 | - | 10 | 2026-06-14 |
| CXA833 | - | 10 | 2026-06-14 |
| CXA852 | - | 9 | 2026-07-06 |
| CXA887 | Xiamen Airlines | 4 | 2026-05-01 |
| CXA854 | - | 2 | 2026-07-07 |
| CXA853 | - | 2 | 2026-07-07 |
| CXA8307 | - | 2 | 2026-07-07 |
| CXA8812 | Xiamen Airlines | 1 | 2026-05-04 |
| CXA8784 | Xiamen Airlines | 1 | 2026-05-14 |
| CXA864 | - | 1 | 2026-07-02 |
| CXA863 | - | 1 | 2026-07-02 |
| CXA8559 | Xiamen Airlines | 1 | 2026-05-24 |
| CXA8536 | - | 1 | 2026-05-13 |
| CXA8437 | - | 1 | 2026-07-14 |
| CXA8428 | Xiamen Airlines | 1 | 2026-07-08 |
| CXA8397 | - | 1 | 2026-05-31 |
| CXA8382 | Xiamen Airlines | 1 | 2026-06-16 |
| CXA8361 | Xiamen Airlines | 1 | 2026-05-14 |
| CXA8350 | - | 1 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CXA8437 | - | Jul 14, 10:00 UTC | Jul 14, 10:20 UTC | 20m |
| 2026-07-13 | CXA8350 | - | Jul 13, 12:50 UTC | Jul 13, 13:00 UTC | 10m |
| 2026-07-13 | CXA8349 | - | Jul 13, 10:30 UTC | Jul 13, 10:45 UTC | 15m |
| 2026-07-08 | CXA8428 | KWE → XMN | Jul 8, 14:15 UTC | Jul 8, 14:30 UTC | 15m |
| 2026-07-07 | CXA8307 | - | Jul 7, 10:20 UTC | Jul 7, 14:20 UTC | 4h 0m |
| 2026-07-07 | CXA854 | - | Jul 7, 05:40 UTC | Jul 7, 07:55 UTC | 2h 15m |
| 2026-07-07 | CXA853 | - | Jul 7, 01:30 UTC | Jul 7, 04:10 UTC | 2h 40m |
| 2026-07-06 | CXA852 | - | Jul 6, 08:15 UTC | Jul 6, 08:40 UTC | 25m |
| 2026-07-06 | CXA851 | - | Jul 6, 03:05 UTC | Jul 6, 06:35 UTC | 3h 30m |
| 2026-07-02 | CXA864 | - | Jul 2, 13:15 UTC | Jul 2, 15:40 UTC | 2h 25m |
| 2026-07-02 | CXA863 | - | Jul 2, 09:00 UTC | Jul 2, 11:30 UTC | 2h 30m |
| 2026-06-23 | CXA8324 | - | Jun 23, 05:24 UTC | Jun 23, 05:34 UTC | 10m |
| 2026-06-16 | CXA8382 | CAN → HGH | Jun 16, 07:45 UTC | Jun 16, 07:55 UTC | 10m |
| 2026-06-14 | CXA834 | - | Jun 14, 10:55 UTC | Jun 14, 13:10 UTC | 2h 15m |
| 2026-06-14 | CXA833 | - | Jun 14, 07:05 UTC | Jun 14, 09:25 UTC | 2h 20m |
| 2026-06-12 | CXA834 | BKK → XMN | Jun 12, 10:55 UTC | Jun 12, 13:10 UTC | 2h 15m |
| 2026-06-12 | CXA833 | XMN → BKK | Jun 12, 06:40 UTC | Jun 12, 09:20 UTC | 2h 40m |
| 2026-06-10 | CXA852 | SIN → XMN | Jun 10, 08:55 UTC | Jun 10, 09:25 UTC | 30m |
| 2026-06-10 | CXA851 | XMN → SIN | Jun 10, 04:00 UTC | Jun 10, 07:05 UTC | 3h 5m |
| 2026-06-09 | CXA852 | SIN → XMN | Jun 9, 07:35 UTC | Jun 10, 04:00 UTC | 20h 25m |
| 2026-06-09 | CXA851 | XMN → SIN | Jun 9, 02:20 UTC | Jun 9, 05:35 UTC | 3h 15m |
| 2026-06-07 | CXA8105 | XMN → PKX | Jun 7, 10:00 UTC | Jun 7, 10:10 UTC | 10m |
| 2026-06-02 | CXA852 | SIN → XMN | Jun 2, 07:50 UTC | Jun 2, 11:15 UTC | 3h 25m |
| 2026-06-01 | CXA8032 | SHE → XMN | Jun 1, 05:40 UTC | Jun 1, 08:00 UTC | 2h 20m |
| 2026-05-31 | CXA8397 | - | May 31, 00:35 UTC | May 31, 00:55 UTC | 20m |
| 2026-05-26 | CXA852 | SIN → XMN | May 26, 07:49 UTC | May 26, 08:10 UTC | 20m |
| 2026-05-26 | CXA851 | XMN → SIN | May 26, 05:10 UTC | May 26, 05:34 UTC | 25m |
| 2026-05-25 | CXA852 | SIN → XMN | May 25, 07:50 UTC | May 25, 08:25 UTC | 35m |
| 2026-05-25 | CXA851 | XMN → SIN | May 25, 02:30 UTC | May 25, 05:30 UTC | 3h 0m |
| 2026-05-24 | CXA8559 | XMN → NKG | May 24, 11:15 UTC | May 24, 11:25 UTC | 10m |
| 2026-05-23 | CXA852 | SIN → XMN | May 23, 08:20 UTC | May 23, 08:50 UTC | 30m |
| 2026-05-23 | CXA851 | XMN → SIN | May 23, 02:45 UTC | May 23, 06:45 UTC | 4h 0m |
| 2026-05-21 | CXA8307 | XMN → SYX | May 21, 09:50 UTC | May 21, 14:40 UTC | 4h 50m |
| 2026-05-14 | CXA8784 | HAK → FOC | May 14, 14:05 UTC | May 14, 14:15 UTC | 10m |
| 2026-05-14 | CXA8361 | XMN → HAK | May 14, 10:40 UTC | May 14, 11:01 UTC | 20m |
| 2026-05-13 | CXA8536 | - | May 13, 13:05 UTC | May 14, 07:15 UTC | 18h 10m |
| 2026-05-13 | CXA834 | BKK → XMN | May 13, 11:10 UTC | May 14, 07:15 UTC | 20h 5m |
| 2026-05-13 | CXA833 | XMN → BKK | May 13, 07:05 UTC | May 13, 09:35 UTC | 2h 30m |
| 2026-05-10 | CXA834 | BKK → XMN | May 10, 10:49 UTC | May 10, 12:59 UTC | 2h 10m |
| 2026-05-10 | CXA833 | XMN → BKK | May 10, 06:35 UTC | May 10, 09:20 UTC | 2h 45m |
| 2026-05-08 | CXA834 | BKK → XMN | May 8, 10:49 UTC | May 8, 13:10 UTC | 2h 20m |
| 2026-05-08 | CXA833 | XMN → BKK | May 8, 06:50 UTC | May 8, 09:09 UTC | 2h 20m |
| 2026-05-04 | CXA8812 | HRB → HGH | May 4, 05:50 UTC | May 4, 06:15 UTC | 25m |
| 2026-05-01 | CXA834 | BKK → XMN | May 1, 12:10 UTC | May 1, 14:25 UTC | 2h 15m |
| 2026-05-01 | CXA833 | XMN → BKK | May 1, 04:10 UTC | May 1, 10:35 UTC | 6h 25m |
| 2026-05-01 | CXA887 | XMN → TPE | May 1, 02:05 UTC | May 1, 02:35 UTC | 30m |
| 2026-04-28 | CXA8321 | HGH → SYX | Apr 28, 00:30 UTC | Apr 28, 04:20 UTC | 3h 50m |
| 2026-04-25 | CXA852 | SIN → XMN | Apr 25, 07:50 UTC | Apr 25, 09:10 UTC | 1h 20m |
| 2026-04-25 | CXA851 | XMN → SIN | Apr 25, 02:25 UTC | Apr 25, 06:00 UTC | 3h 35m |
| 2026-04-24 | CXA851 | XMN → SIN | Apr 24, 08:55 UTC | Apr 25, 06:00 UTC | 21h 5m |
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-32GA page for operator, model, and routing details .