sensors Mode-S transponder
781196
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8593 · AIRBUS A-320
- Hex
- 781196
- Octal
- 36010626
- Decimal
- 7,868,822
- Country
- CN
- Tail
- B-8593
- Type
- A320
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 781196 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 |
|---|---|---|---|
| CDC8874 | - | 3 | 2026-07-16 |
| CDC8021 | Zhejiang Loong Airlines | 3 | 2026-05-14 |
| CDC6094 | - | 3 | 2026-04-21 |
| CDC8870 | - | 2 | 2026-07-17 |
| CDC8656 | - | 2 | 2026-07-05 |
| CDC8655 | - | 2 | 2026-07-05 |
| CDC8540 | Zhejiang Loong Airlines | 2 | 2026-07-02 |
| CDC8539 | - | 2 | 2026-07-06 |
| CDC8241 | - | 2 | 2026-05-14 |
| CDC8095 | Zhejiang Loong Airlines | 2 | 2026-06-30 |
| CDC8022 | Zhejiang Loong Airlines | 2 | 2026-05-15 |
| CDC6030 | - | 2 | 2026-04-17 |
| CDC6029 | - | 2 | 2026-04-17 |
| CDC8989 | Zhejiang Loong Airlines | 1 | 2026-06-05 |
| CDC8958 | Zhejiang Loong Airlines | 1 | 2026-06-27 |
| CDC8873 | - | 1 | 2026-07-16 |
| CDC8866 | - | 1 | 2026-07-12 |
| CDC8358 | - | 1 | 2026-07-03 |
| CDC8008 | - | 1 | 2026-06-15 |
| CDC8007 | - | 1 | 2026-06-15 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CDC8870 | - | Jul 17, 11:50 UTC | Jul 17, 12:10 UTC | 20m |
| 2026-07-16 | CDC8874 | - | Jul 16, 10:50 UTC | Jul 16, 11:05 UTC | 15m |
| 2026-07-16 | CDC8873 | - | Jul 16, 08:00 UTC | Jul 16, 08:10 UTC | 10m |
| 2026-07-15 | CDC8874 | - | Jul 15, 11:55 UTC | Jul 15, 12:05 UTC | 10m |
| 2026-07-12 | CDC8866 | - | Jul 12, 14:25 UTC | Jul 12, 15:15 UTC | 50m |
| 2026-07-06 | CDC8539 | - | Jul 6, 23:55 UTC | Jul 7, 00:05 UTC | 10m |
| 2026-07-05 | CDC8656 | - | Jul 5, 12:45 UTC | Jul 5, 13:00 UTC | 15m |
| 2026-07-05 | CDC8655 | - | Jul 5, 01:20 UTC | Jul 5, 07:25 UTC | 6h 5m |
| 2026-07-03 | CDC8358 | - | Jul 3, 08:30 UTC | Jul 3, 08:45 UTC | 15m |
| 2026-07-02 | CDC8540 | WUH → CGQ | Jul 2, 12:50 UTC | Jul 3, 08:45 UTC | 19h 55m |
| 2026-06-30 | CDC8095 | HGH → SYX | Jun 30, 23:40 UTC | Jul 1, 03:45 UTC | 4h 5m |
| 2026-06-27 | CDC8958 | CGQ → HGH | Jun 27, 14:35 UTC | Jun 27, 15:05 UTC | 30m |
| 2026-06-22 | CDC8539 | XIY → HRB | Jun 22, 12:00 UTC | Jun 23, 01:15 UTC | 13h 15m |
| 2026-06-22 | CDC8656 | - | Jun 22, 08:00 UTC | Jun 22, 08:10 UTC | 10m |
| 2026-06-22 | CDC8655 | - | Jun 22, 06:29 UTC | Jun 22, 06:45 UTC | 15m |
| 2026-06-20 | CDC8540 | WUH → CGQ | Jun 20, 11:20 UTC | Jun 20, 11:34 UTC | 15m |
| 2026-06-15 | CDC8008 | - | Jun 15, 06:24 UTC | Jun 15, 07:29 UTC | 1h 5m |
| 2026-06-15 | CDC8007 | - | Jun 15, 03:19 UTC | Jun 15, 04:20 UTC | 1h 0m |
| 2026-06-05 | CDC8989 | HGH → CAN | Jun 5, 16:25 UTC | Jun 5, 17:00 UTC | 35m |
| 2026-05-24 | CDC8095 | HGH → SYX | May 24, 23:40 UTC | May 25, 03:25 UTC | 3h 45m |
| 2026-05-15 | CDC8022 | BKK → HGH | May 15, 10:40 UTC | May 15, 13:05 UTC | 2h 25m |
| 2026-05-14 | CDC8021 | HGH → BKK | May 14, 13:35 UTC | May 15, 09:20 UTC | 19h 45m |
| 2026-05-14 | CDC8021 | HGH → BKK | May 14, 10:05 UTC | May 15, 09:20 UTC | 23h 15m |
| 2026-05-14 | CDC8241 | - | May 14, 00:00 UTC | May 14, 13:50 UTC | 13h 50m |
| 2026-05-12 | CDC8241 | - | May 12, 04:45 UTC | May 12, 05:05 UTC | 20m |
| 2026-05-08 | CDC8022 | BKK → HGH | May 8, 11:44 UTC | May 8, 14:05 UTC | 2h 20m |
| 2026-05-08 | CDC8021 | HGH → BKK | May 8, 07:04 UTC | May 8, 10:04 UTC | 3h 0m |
| 2026-05-07 | CDC8874 | - | May 7, 10:55 UTC | May 7, 11:05 UTC | 10m |
| 2026-05-06 | CDC8870 | - | May 6, 12:01 UTC | May 6, 12:20 UTC | 20m |
| 2026-04-21 | CDC6094 | - | Apr 21, 03:10 UTC | Apr 21, 03:20 UTC | 10m |
| 2026-04-18 | CDC6094 | - | Apr 18, 04:45 UTC | Apr 18, 04:55 UTC | 10m |
| 2026-04-18 | CDC6094 | - | Apr 18, 04:40 UTC | Apr 18, 04:55 UTC | 15m |
| 2026-04-17 | CDC6030 | - | Apr 17, 09:00 UTC | Apr 17, 09:10 UTC | 10m |
| 2026-04-17 | CDC6030 | - | Apr 17, 07:35 UTC | Apr 17, 08:10 UTC | 35m |
| 2026-04-17 | CDC6029 | - | Apr 17, 05:20 UTC | Apr 17, 05:35 UTC | 15m |
| 2026-04-17 | CDC6029 | - | Apr 17, 04:15 UTC | Apr 17, 05:15 UTC | 1h 1m |
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-8593 page for operator, model, and routing details .