sensors Mode-S transponder
781E7A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32CN · AIRBUS A-320neo
- Hex
- 781E7A
- Octal
- 36017172
- Decimal
- 7,872,122
- Country
- CN
- Tail
- B-32CN
- Type
- A20N
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 781E7A 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 |
|---|---|---|---|
| CDC8683 | - | 7 | 2026-07-08 |
| CDC8684 | - | 6 | 2026-07-07 |
| CDC8592 | Zhejiang Loong Airlines | 5 | 2026-05-16 |
| CDC8591 | Zhejiang Loong Airlines | 5 | 2026-05-16 |
| CDC8021 | Zhejiang Loong Airlines | 5 | 2026-06-05 |
| CDC8655 | - | 4 | 2026-06-23 |
| CDC8261 | - | 3 | 2026-05-14 |
| CDC8241 | - | 3 | 2026-06-04 |
| CDC8022 | Zhejiang Loong Airlines | 3 | 2026-06-05 |
| CDC8998 | Zhejiang Loong Airlines | 2 | 2026-05-12 |
| CDC8997 | Zhejiang Loong Airlines | 2 | 2026-05-12 |
| CDC8262 | - | 2 | 2026-05-14 |
| CDC8958 | Zhejiang Loong Airlines | 1 | 2026-06-19 |
| CDC8874 | - | 1 | 2026-07-17 |
| CDC8873 | - | 1 | 2026-07-17 |
| CDC8706 | Zhejiang Loong Airlines | 1 | 2026-06-13 |
| CDC8656 | - | 1 | 2026-06-24 |
| CDC8539 | Zhejiang Loong Airlines | 1 | 2026-06-09 |
| CDC8357 | - | 1 | 2026-06-22 |
| CDC8242 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CDC8874 | - | Jul 17, 10:30 UTC | Jul 17, 10:44 UTC | 15m |
| 2026-07-17 | CDC8873 | - | Jul 17, 09:04 UTC | Jul 17, 09:15 UTC | 10m |
| 2026-07-08 | CDC8683 | - | Jul 8, 00:00 UTC | Jul 8, 00:15 UTC | 15m |
| 2026-07-07 | CDC8684 | - | Jul 7, 20:10 UTC | Jul 7, 20:20 UTC | 10m |
| 2026-07-07 | CDC8683 | - | Jul 7, 04:05 UTC | Jul 7, 04:15 UTC | 10m |
| 2026-07-05 | CDC8683 | - | Jul 5, 23:20 UTC | Jul 5, 23:35 UTC | 15m |
| 2026-07-05 | CDC8684 | - | Jul 5, 18:10 UTC | Jul 5, 18:30 UTC | 20m |
| 2026-07-05 | CDC8683 | - | Jul 5, 00:40 UTC | Jul 5, 00:55 UTC | 15m |
| 2026-07-04 | CDC8684 | - | Jul 4, 21:05 UTC | Jul 4, 21:30 UTC | 25m |
| 2026-07-03 | CDC8683 | - | Jul 3, 23:15 UTC | Jul 3, 23:30 UTC | 15m |
| 2026-07-03 | CDC8684 | - | Jul 3, 16:15 UTC | Jul 3, 16:40 UTC | 25m |
| 2026-07-02 | CDC8683 | - | Jul 2, 23:05 UTC | Jul 2, 23:20 UTC | 15m |
| 2026-07-02 | CDC8684 | - | Jul 2, 16:35 UTC | Jul 2, 16:50 UTC | 15m |
| 2026-07-01 | CDC8683 | - | Jul 1, 23:00 UTC | Jul 1, 23:15 UTC | 15m |
| 2026-07-01 | CDC8684 | - | Jul 1, 16:55 UTC | Jul 1, 17:10 UTC | 15m |
| 2026-06-24 | CDC8656 | - | Jun 24, 13:00 UTC | Jun 24, 13:20 UTC | 20m |
| 2026-06-23 | CDC8655 | - | Jun 23, 11:10 UTC | Jun 24, 06:25 UTC | 19h 15m |
| 2026-06-23 | CDC8655 | - | Jun 23, 07:29 UTC | Jun 24, 06:25 UTC | 22h 55m |
| 2026-06-23 | CDC8655 | - | Jun 23, 04:45 UTC | Jun 23, 05:00 UTC | 15m |
| 2026-06-22 | CDC8655 | - | Jun 22, 08:19 UTC | Jun 23, 00:00 UTC | 15h 40m |
| 2026-06-22 | CDC8357 | - | Jun 22, 05:49 UTC | Jun 22, 06:05 UTC | 15m |
| 2026-06-19 | CDC8958 | CGQ → HGH | Jun 19, 13:34 UTC | Jun 19, 14:04 UTC | 30m |
| 2026-06-13 | CDC8706 | VTE → HGH | Jun 13, 08:25 UTC | Jun 13, 12:00 UTC | 3h 35m |
| 2026-06-09 | CDC8539 | XIY → HRB | Jun 9, 00:55 UTC | Jun 9, 01:10 UTC | 15m |
| 2026-06-05 | CDC8022 | BKK → HGH | Jun 5, 10:45 UTC | Jun 5, 13:00 UTC | 2h 15m |
| 2026-06-05 | CDC8021 | HGH → BKK | Jun 5, 07:15 UTC | Jun 5, 09:30 UTC | 2h 15m |
| 2026-06-04 | CDC8021 | HGH → BKK | Jun 4, 13:05 UTC | Jun 5, 09:30 UTC | 20h 25m |
| 2026-06-04 | CDC8241 | - | Jun 4, 00:15 UTC | Jun 4, 13:50 UTC | 13h 35m |
| 2026-05-16 | CDC8592 | CJJ → DYG | May 16, 07:05 UTC | May 16, 07:25 UTC | 20m |
| 2026-05-16 | CDC8591 | DYG → CJJ | May 16, 05:25 UTC | May 16, 05:46 UTC | 21m |
| 2026-05-14 | CDC8262 | - | May 14, 06:40 UTC | May 14, 07:00 UTC | 20m |
| 2026-05-14 | CDC8261 | - | May 14, 05:15 UTC | May 14, 05:30 UTC | 15m |
| 2026-05-13 | CDC8592 | CJJ → DYG | May 13, 09:40 UTC | May 13, 10:15 UTC | 35m |
| 2026-05-13 | CDC8591 | DYG → CJJ | May 13, 07:50 UTC | May 13, 08:25 UTC | 35m |
| 2026-05-12 | CDC8998 | SIN → DYG | May 12, 08:15 UTC | May 12, 08:30 UTC | 15m |
| 2026-05-12 | CDC8997 | DYG → SIN | May 12, 06:10 UTC | May 12, 06:20 UTC | 10m |
| 2026-05-10 | CDC8022 | BKK → HGH | May 10, 10:55 UTC | May 10, 13:10 UTC | 2h 15m |
| 2026-05-10 | CDC8021 | HGH → BKK | May 10, 07:04 UTC | May 10, 09:35 UTC | 2h 30m |
| 2026-05-08 | CDC8078 | KIX → HGH | May 8, 08:55 UTC | May 8, 09:49 UTC | 55m |
| 2026-05-08 | CDC8077 | HGH → KIX | May 8, 06:20 UTC | May 8, 07:04 UTC | 45m |
| 2026-04-30 | CDC8262 | - | Apr 30, 07:05 UTC | Apr 30, 07:25 UTC | 20m |
| 2026-04-30 | CDC8261 | - | Apr 30, 05:50 UTC | Apr 30, 06:00 UTC | 10m |
| 2026-04-29 | CDC8592 | CJJ → DYG | Apr 29, 09:45 UTC | Apr 29, 10:30 UTC | 45m |
| 2026-04-29 | CDC8591 | DYG → CJJ | Apr 29, 07:55 UTC | Apr 29, 08:25 UTC | 30m |
| 2026-04-25 | CDC8592 | CJJ → DYG | Apr 25, 07:00 UTC | Apr 25, 07:35 UTC | 35m |
| 2026-04-25 | CDC8591 | DYG → CJJ | Apr 25, 05:15 UTC | Apr 25, 05:45 UTC | 30m |
| 2026-04-23 | CDC8261 | - | Apr 23, 05:05 UTC | Apr 23, 05:20 UTC | 15m |
| 2026-04-22 | CDC8592 | CJJ → DYG | Apr 22, 09:30 UTC | Apr 22, 10:05 UTC | 35m |
| 2026-04-22 | CDC8591 | DYG → CJJ | Apr 22, 07:45 UTC | Apr 22, 08:15 UTC | 30m |
| 2026-04-21 | CDC8998 | SIN → DYG | Apr 21, 09:15 UTC | Apr 21, 10:40 UTC | 1h 25m |
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-32CN page for operator, model, and routing details .