sensors Mode-S transponder
781E0D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32AP · AIRBUS A-320neo
- Hex
- 781E0D
- Octal
- 36017015
- Decimal
- 7,872,013
- Country
- CN
- Tail
- B-32AP
- Type
- A20N
- Flights observed
- 55
- Distinct callsigns
- 19
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 781E0D 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CDC8021 | - | 10 | 2026-07-16 |
| CDC8655 | - | 9 | 2026-06-03 |
| CDC8656 | - | 8 | 2026-06-03 |
| CDC8057 | - | 5 | 2026-07-13 |
| CDC8022 | - | 5 | 2026-07-16 |
| CDC8058 | - | 3 | 2026-07-14 |
| CDC8958 | Zhejiang Loong Airlines | 2 | 2026-06-23 |
| CDC8241 | - | 2 | 2026-07-04 |
| CDC8998 | - | 1 | 2026-06-25 |
| CDC8997 | - | 1 | 2026-06-25 |
| CDC8874 | - | 1 | 2026-07-05 |
| CDC8597 | - | 1 | 2026-06-21 |
| CDC8590 | - | 1 | 2026-06-14 |
| CDC8539 | Zhejiang Loong Airlines | 1 | 2026-06-05 |
| CDC8242 | - | 1 | 2026-07-04 |
| CDC8078 | Zhejiang Loong Airlines | 1 | 2026-05-11 |
| CDC8077 | Zhejiang Loong Airlines | 1 | 2026-05-11 |
| CDC8008 | - | 1 | 2026-07-08 |
| CDC8007 | - | 1 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CDC8022 | - | Jul 16, 11:25 UTC | Jul 17, 01:49 UTC | 14h 25m |
| 2026-07-16 | CDC8021 | - | Jul 16, 08:55 UTC | Jul 16, 09:10 UTC | 15m |
| 2026-07-16 | CDC8021 | - | Jul 16, 06:35 UTC | Jul 16, 06:50 UTC | 15m |
| 2026-07-14 | CDC8058 | - | Jul 14, 08:30 UTC | Jul 14, 12:30 UTC | 4h 0m |
| 2026-07-13 | CDC8057 | - | Jul 13, 13:00 UTC | Jul 14, 06:35 UTC | 17h 35m |
| 2026-07-13 | CDC8057 | - | Jul 13, 10:50 UTC | Jul 14, 06:35 UTC | 19h 45m |
| 2026-07-13 | CDC8021 | - | Jul 13, 09:05 UTC | Jul 13, 09:30 UTC | 25m |
| 2026-07-12 | CDC8022 | - | Jul 12, 19:40 UTC | Jul 13, 07:25 UTC | 11h 45m |
| 2026-07-12 | CDC8021 | - | Jul 12, 15:45 UTC | Jul 12, 16:01 UTC | 15m |
| 2026-07-12 | CDC8021 | - | Jul 12, 13:45 UTC | Jul 12, 14:05 UTC | 20m |
| 2026-07-09 | CDC8058 | - | Jul 9, 08:25 UTC | Jul 9, 12:25 UTC | 4h 0m |
| 2026-07-08 | CDC8057 | - | Jul 8, 15:05 UTC | Jul 9, 07:00 UTC | 15h 55m |
| 2026-07-08 | CDC8057 | - | Jul 8, 07:20 UTC | Jul 9, 07:00 UTC | 23h 40m |
| 2026-07-08 | CDC8008 | - | Jul 8, 06:25 UTC | Jul 9, 03:35 UTC | 21h 10m |
| 2026-07-07 | CDC8007 | - | Jul 7, 10:50 UTC | Jul 8, 04:30 UTC | 17h 40m |
| 2026-07-07 | CDC8021 | - | Jul 7, 06:40 UTC | Jul 7, 09:10 UTC | 2h 30m |
| 2026-07-05 | CDC8874 | - | Jul 5, 12:25 UTC | Jul 5, 12:35 UTC | 10m |
| 2026-07-04 | CDC8242 | - | Jul 4, 13:10 UTC | Jul 4, 13:40 UTC | 30m |
| 2026-07-04 | CDC8241 | - | Jul 4, 00:55 UTC | Jul 4, 05:30 UTC | 4h 35m |
| 2026-07-02 | CDC8058 | - | Jul 2, 08:15 UTC | Jul 2, 11:35 UTC | 3h 20m |
| 2026-07-01 | CDC8057 | - | Jul 1, 15:40 UTC | Jul 2, 06:20 UTC | 14h 40m |
| 2026-06-30 | CDC8241 | - | Jun 30, 00:14 UTC | Jun 30, 11:50 UTC | 11h 36m |
| 2026-06-27 | CDC8022 | - | Jun 27, 10:54 UTC | Jun 27, 13:24 UTC | 2h 30m |
| 2026-06-27 | CDC8021 | - | Jun 27, 06:44 UTC | Jun 27, 09:04 UTC | 2h 20m |
| 2026-06-25 | CDC8998 | - | Jun 25, 08:04 UTC | Jun 25, 11:25 UTC | 3h 20m |
| 2026-06-25 | CDC8997 | - | Jun 25, 03:24 UTC | Jun 25, 06:20 UTC | 2h 55m |
| 2026-06-23 | CDC8958 | CGQ → HGH | Jun 23, 14:35 UTC | Jun 23, 15:04 UTC | 30m |
| 2026-06-21 | CDC8597 | - | Jun 21, 11:34 UTC | Jun 21, 11:49 UTC | 15m |
| 2026-06-14 | CDC8590 | - | Jun 14, 07:05 UTC | Jun 14, 07:15 UTC | 10m |
| 2026-06-05 | CDC8539 | XIY → HRB | Jun 5, 13:40 UTC | Jun 6, 01:25 UTC | 11h 45m |
| 2026-06-03 | CDC8656 | - | Jun 3, 08:05 UTC | Jun 3, 08:15 UTC | 10m |
| 2026-06-03 | CDC8655 | - | Jun 3, 06:20 UTC | Jun 3, 06:40 UTC | 20m |
| 2026-06-03 | CDC8655 | - | Jun 3, 01:30 UTC | Jun 3, 01:50 UTC | 20m |
| 2026-05-31 | CDC8656 | - | May 31, 08:50 UTC | May 31, 09:00 UTC | 10m |
| 2026-05-29 | CDC8656 | - | May 29, 09:00 UTC | May 29, 12:55 UTC | 3h 55m |
| 2026-05-29 | CDC8655 | - | May 29, 06:30 UTC | May 29, 06:55 UTC | 25m |
| 2026-05-26 | CDC8656 | - | May 26, 07:49 UTC | May 26, 07:59 UTC | 10m |
| 2026-05-26 | CDC8655 | - | May 26, 04:35 UTC | May 26, 05:00 UTC | 25m |
| 2026-05-26 | CDC8655 | - | May 26, 00:35 UTC | May 26, 04:04 UTC | 3h 30m |
| 2026-05-24 | CDC8022 | BKK → HGH | May 24, 11:30 UTC | May 24, 13:45 UTC | 2h 15m |
| 2026-05-24 | CDC8021 | HGH → BKK | May 24, 08:00 UTC | May 24, 10:20 UTC | 2h 20m |
| 2026-05-12 | CDC8022 | BKK → HGH | May 12, 10:30 UTC | May 12, 12:45 UTC | 2h 15m |
| 2026-05-12 | CDC8021 | HGH → BKK | May 12, 06:30 UTC | May 12, 09:00 UTC | 2h 30m |
| 2026-05-11 | CDC8021 | HGH → BKK | May 11, 09:20 UTC | May 12, 09:00 UTC | 23h 41m |
| 2026-05-11 | CDC8078 | KIX → HGH | May 11, 09:10 UTC | May 12, 06:50 UTC | 21h 40m |
| 2026-05-11 | CDC8077 | HGH → KIX | May 11, 06:35 UTC | May 11, 07:25 UTC | 50m |
| 2026-05-05 | CDC8656 | - | May 5, 06:40 UTC | May 5, 06:50 UTC | 10m |
| 2026-05-05 | CDC8655 | - | May 5, 05:00 UTC | May 5, 05:15 UTC | 15m |
| 2026-05-04 | CDC8655 | - | May 4, 23:35 UTC | May 5, 00:10 UTC | 35m |
| 2026-04-27 | CDC8958 | CGQ → HGH | Apr 27, 14:00 UTC | Apr 28, 12:10 UTC | 22h 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-32AP page for operator, model, and routing details .