sensors Mode-S transponder
7822AD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32MY · AIRBUS A-320neo
- Hex
- 7822AD
- Octal
- 36021255
- Decimal
- 7,873,197
- Country
- CN
- Tail
- B-32MY
- Type
- A20N
- Flights observed
- 61
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 7822AD 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CXA8307 | - | 27 | 2026-07-09 |
| CXA8375 | - | 5 | 2026-07-10 |
| CXA8308 | Xiamen Airlines | 5 | 2026-06-15 |
| CXA8359 | - | 4 | 2026-07-06 |
| CXA8376 | - | 3 | 2026-07-11 |
| CXA8361 | Xiamen Airlines | 3 | 2026-05-24 |
| CXA8397 | - | 2 | 2026-07-14 |
| CXA8362 | Xiamen Airlines | 2 | 2026-05-31 |
| CXA8571 | Xiamen Airlines | 1 | 2026-05-30 |
| CXA8540 | Xiamen Airlines | 1 | 2026-06-21 |
| CXA8342 | - | 1 | 2026-06-24 |
| CXA8341 | - | 1 | 2026-06-24 |
| CXA8337 | - | 1 | 2026-07-10 |
| CXA8048 | - | 1 | 2026-07-10 |
| CXA8047 | - | 1 | 2026-07-12 |
| CXA8032 | - | 1 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CXA8397 | - | Jul 14, 00:45 UTC | Jul 14, 04:50 UTC | 4h 5m |
| 2026-07-12 | - | - | Jul 12, 13:20 UTC | Jul 12, 13:40 UTC | 20m |
| 2026-07-12 | CXA8047 | - | Jul 12, 06:20 UTC | Jul 12, 12:10 UTC | 5h 50m |
| 2026-07-11 | CXA8376 | - | Jul 11, 02:45 UTC | Jul 11, 03:01 UTC | 15m |
| 2026-07-10 | CXA8375 | - | Jul 10, 23:00 UTC | Jul 10, 23:45 UTC | 45m |
| 2026-07-10 | CXA8048 | - | Jul 10, 06:20 UTC | Jul 10, 13:45 UTC | 7h 25m |
| 2026-07-10 | CXA8337 | - | Jul 10, 00:05 UTC | Jul 10, 00:20 UTC | 15m |
| 2026-07-09 | CXA8307 | - | Jul 9, 10:05 UTC | Jul 9, 14:25 UTC | 4h 20m |
| 2026-07-07 | CXA8375 | - | Jul 7, 23:10 UTC | Jul 7, 23:50 UTC | 40m |
| 2026-07-06 | CXA8359 | - | Jul 6, 09:55 UTC | Jul 6, 11:20 UTC | 1h 25m |
| 2026-07-02 | CXA8376 | - | Jul 2, 03:10 UTC | Jul 2, 11:45 UTC | 8h 35m |
| 2026-07-01 | CXA8359 | - | Jul 1, 10:45 UTC | Jul 2, 00:05 UTC | 13h 20m |
| 2026-06-27 | CXA8032 | - | Jun 27, 01:09 UTC | Jun 27, 10:10 UTC | 9h 0m |
| 2026-06-24 | CXA8342 | - | Jun 24, 08:45 UTC | Jun 24, 09:00 UTC | 15m |
| 2026-06-24 | CXA8341 | - | Jun 24, 05:54 UTC | Jun 24, 06:15 UTC | 20m |
| 2026-06-21 | CXA8540 | NKG → XMN | Jun 21, 05:49 UTC | Jun 21, 05:59 UTC | 10m |
| 2026-06-19 | CXA8307 | - | Jun 19, 10:19 UTC | Jun 19, 13:39 UTC | 3h 20m |
| 2026-06-19 | CXA8397 | - | Jun 19, 00:34 UTC | Jun 19, 04:54 UTC | 4h 20m |
| 2026-06-16 | CXA8307 | - | Jun 16, 10:15 UTC | Jun 16, 14:20 UTC | 4h 5m |
| 2026-06-15 | CXA8307 | - | Jun 15, 13:20 UTC | Jun 16, 11:30 UTC | 22h 10m |
| 2026-06-15 | CXA8308 | SYX → XMN | Jun 15, 12:49 UTC | Jun 16, 10:45 UTC | 21h 55m |
| 2026-06-15 | CXA8307 | - | Jun 15, 10:00 UTC | Jun 15, 10:50 UTC | 50m |
| 2026-06-14 | CXA8307 | - | Jun 14, 01:55 UTC | Jun 14, 12:25 UTC | 10h 30m |
| 2026-06-11 | CXA8375 | XMN → NNG | Jun 11, 13:30 UTC | Jun 12, 05:30 UTC | 16h 1m |
| 2026-06-11 | CXA8307 | XMN → SYX | Jun 11, 10:15 UTC | Jun 12, 05:30 UTC | 19h 16m |
| 2026-06-10 | CXA8376 | NNG → XMN | Jun 10, 02:50 UTC | Jun 10, 03:05 UTC | 15m |
| 2026-06-09 | CXA8375 | XMN → NNG | Jun 9, 23:55 UTC | Jun 10, 00:15 UTC | 20m |
| 2026-06-08 | CXA8307 | XMN → SYX | Jun 8, 10:15 UTC | Jun 8, 14:00 UTC | 3h 45m |
| 2026-06-05 | CXA8375 | XMN → NNG | Jun 5, 23:45 UTC | Jun 6, 00:00 UTC | 15m |
| 2026-06-04 | CXA8359 | XMN → NNG | Jun 4, 11:10 UTC | Jun 4, 12:00 UTC | 50m |
| 2026-06-02 | CXA8308 | SYX → XMN | Jun 2, 12:05 UTC | Jun 2, 12:50 UTC | 45m |
| 2026-06-02 | CXA8307 | XMN → SYX | Jun 2, 09:00 UTC | Jun 2, 09:55 UTC | 55m |
| 2026-05-31 | CXA8362 | HAK → XMN | May 31, 10:30 UTC | May 31, 14:15 UTC | 3h 45m |
| 2026-05-30 | CXA8308 | SYX → XMN | May 30, 12:20 UTC | May 30, 12:50 UTC | 30m |
| 2026-05-30 | CXA8307 | XMN → SYX | May 30, 08:30 UTC | May 30, 10:00 UTC | 1h 30m |
| 2026-05-30 | CXA8571 | XMN → TNA | May 30, 01:35 UTC | May 30, 01:45 UTC | 10m |
| 2026-05-24 | CXA8362 | HAK → XMN | May 24, 13:50 UTC | May 25, 09:50 UTC | 20h 0m |
| 2026-05-24 | CXA8361 | XMN → HAK | May 24, 10:45 UTC | May 24, 14:05 UTC | 3h 20m |
| 2026-05-23 | CXA8361 | XMN → HAK | May 23, 12:55 UTC | May 24, 11:10 UTC | 22h 15m |
| 2026-05-23 | CXA8307 | XMN → SYX | May 23, 09:30 UTC | May 23, 13:05 UTC | 3h 35m |
| 2026-05-20 | CXA8307 | XMN → SYX | May 20, 01:40 UTC | May 20, 12:55 UTC | 11h 16m |
| 2026-05-17 | CXA8359 | XMN → NNG | May 17, 11:01 UTC | May 17, 11:25 UTC | 25m |
| 2026-05-11 | - | - | May 11, 01:50 UTC | May 11, 02:00 UTC | 10m |
| 2026-05-10 | CXA8307 | XMN → SYX | May 10, 08:54 UTC | May 10, 12:40 UTC | 3h 45m |
| 2026-05-06 | CXA8307 | XMN → SYX | May 6, 08:55 UTC | May 6, 12:40 UTC | 3h 45m |
| 2026-05-03 | CXA8307 | XMN → SYX | May 3, 08:35 UTC | May 3, 12:45 UTC | 4h 10m |
| 2026-04-27 | CXA8307 | XMN → SYX | Apr 27, 09:00 UTC | Apr 27, 13:00 UTC | 4h 0m |
| 2026-04-26 | CXA8307 | XMN → SYX | Apr 26, 12:15 UTC | Apr 27, 09:30 UTC | 21h 15m |
| 2026-04-26 | CXA8307 | XMN → SYX | Apr 26, 08:50 UTC | Apr 26, 12:25 UTC | 3h 35m |
| 2026-04-25 | CXA8307 | XMN → SYX | Apr 25, 13:50 UTC | Apr 26, 12:25 UTC | 22h 35m |
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-32MY page for operator, model, and routing details .