sensors Mode-S transponder
78056E
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6565 · AIRBUS A-320
- Hex
- 78056E
- Octal
- 36002556
- Decimal
- 7,865,710
- Country
- CN
- Tail
- B-6565
- Type
- A320
- Flights observed
- 52
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address 78056E 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 |
|---|---|---|---|
| CSZ9727 | - | 4 | 2026-06-26 |
| CSZ9605 | Shenzhen Airlines | 3 | 2026-06-09 |
| CSZ9982 | Shenzhen Airlines | 2 | 2026-06-29 |
| CSZ9962 | - | 2 | 2026-07-20 |
| CSZ9728 | - | 2 | 2026-06-23 |
| CSZ9713 | - | 2 | 2026-07-15 |
| CSZ9302 | Shenzhen Airlines | 2 | 2026-04-23 |
| CSZ9204 | Shenzhen Airlines | 2 | 2026-06-06 |
| CSZ9195 | Shenzhen Airlines | 2 | 2026-05-09 |
| CSZ8991 | Shenzhen Airlines | 2 | 2026-05-13 |
| CSZ8565 | - | 2 | 2026-05-23 |
| CSZ8033 | Shenzhen Airlines | 2 | 2026-05-03 |
| CSZ9988 | - | 1 | 2026-07-13 |
| CSZ9961 | - | 1 | 2026-07-05 |
| CSZ9863 | Shenzhen Airlines | 1 | 2026-05-17 |
| CSZ9723 | - | 1 | 2026-06-17 |
| CSZ9711 | - | 1 | 2026-06-25 |
| CSZ9467 | Shenzhen Airlines | 1 | 2026-06-06 |
| CSZ9455 | Shenzhen Airlines | 1 | 2026-04-21 |
| CSZ9453 | Shenzhen Airlines | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CSZ9962 | - | Jul 20, 23:30 UTC | Jul 21, 00:25 UTC | 54m |
| 2026-07-19 | - | - | Jul 19, 14:25 UTC | Jul 19, 14:35 UTC | 10m |
| 2026-07-16 | CSZ8945 | - | Jul 16, 10:20 UTC | Jul 16, 10:29 UTC | 10m |
| 2026-07-15 | CSZ9713 | - | Jul 15, 07:20 UTC | Jul 15, 07:30 UTC | 10m |
| 2026-07-13 | CSZ9988 | - | Jul 13, 12:05 UTC | Jul 13, 12:15 UTC | 10m |
| 2026-07-13 | CSZ9713 | - | Jul 13, 04:15 UTC | Jul 13, 07:35 UTC | 3h 20m |
| 2026-07-10 | CSZ8958 | - | Jul 10, 13:15 UTC | Jul 10, 13:25 UTC | 10m |
| 2026-07-05 | CSZ9961 | - | Jul 5, 23:40 UTC | Jul 5, 23:55 UTC | 15m |
| 2026-07-05 | CSZ8594 | - | Jul 5, 08:10 UTC | Jul 5, 08:20 UTC | 10m |
| 2026-07-05 | CSZ8310 | - | Jul 5, 01:15 UTC | Jul 5, 01:35 UTC | 20m |
| 2026-07-01 | CSZ9962 | - | Jul 1, 00:15 UTC | Jul 1, 00:30 UTC | 15m |
| 2026-06-29 | CSZ9982 | HGH → CAN | Jun 29, 15:45 UTC | Jun 29, 16:00 UTC | 15m |
| 2026-06-26 | CSZ9727 | - | Jun 26, 06:45 UTC | Jun 27, 01:24 UTC | 18h 40m |
| 2026-06-25 | CSZ9727 | - | Jun 25, 12:54 UTC | Jun 26, 09:35 UTC | 20h 40m |
| 2026-06-25 | CSZ9711 | - | Jun 25, 02:05 UTC | Jun 25, 12:54 UTC | 10h 50m |
| 2026-06-23 | CSZ9728 | - | Jun 23, 06:44 UTC | Jun 23, 13:55 UTC | 7h 10m |
| 2026-06-21 | CSZ9728 | - | Jun 21, 09:24 UTC | Jun 21, 13:50 UTC | 4h 25m |
| 2026-06-21 | CSZ9727 | - | Jun 21, 06:44 UTC | Jun 21, 07:04 UTC | 20m |
| 2026-06-18 | CSZ9727 | - | Jun 18, 06:55 UTC | Jun 18, 09:25 UTC | 2h 30m |
| 2026-06-17 | CSZ9723 | - | Jun 17, 02:30 UTC | Jun 17, 11:00 UTC | 8h 30m |
| 2026-06-09 | CSZ9605 | CAN → JDZ | Jun 9, 13:40 UTC | Jun 9, 14:00 UTC | 20m |
| 2026-06-09 | CSZ9605 | CAN → JDZ | Jun 9, 11:20 UTC | Jun 9, 11:30 UTC | 10m |
| 2026-06-08 | CSZ9205 | SZX → XIY | Jun 8, 06:10 UTC | Jun 8, 06:25 UTC | 15m |
| 2026-06-07 | CSZ9203 | SZX → XIY | Jun 7, 02:35 UTC | Jun 7, 02:50 UTC | 15m |
| 2026-06-06 | CSZ9467 | SZX → CKG | Jun 6, 13:34 UTC | Jun 6, 14:25 UTC | 50m |
| 2026-06-06 | CSZ9204 | XIY → SZX | Jun 6, 09:15 UTC | Jun 6, 09:30 UTC | 15m |
| 2026-05-27 | CSZ9605 | CAN → JDZ | May 27, 11:20 UTC | May 27, 11:40 UTC | 20m |
| 2026-05-26 | CSZ8978 | - | May 26, 16:45 UTC | May 26, 16:55 UTC | 10m |
| 2026-05-26 | CSZ8977 | - | May 26, 11:09 UTC | May 26, 11:30 UTC | 20m |
| 2026-05-25 | CSZ9235 | SZX → XNN | May 25, 23:45 UTC | May 26, 00:00 UTC | 15m |
| 2026-05-25 | CSZ9204 | XIY → SZX | May 25, 09:00 UTC | May 25, 09:10 UTC | 10m |
| 2026-05-24 | CSZ8993 | CAN → HAK | May 24, 15:05 UTC | May 24, 15:20 UTC | 15m |
| 2026-05-23 | CSZ8565 | - | May 23, 01:35 UTC | May 23, 05:30 UTC | 3h 54m |
| 2026-05-22 | CSZ8565 | - | May 22, 02:05 UTC | May 22, 02:30 UTC | 25m |
| 2026-05-17 | CSZ9863 | SZX → HGH | May 17, 01:30 UTC | May 17, 01:40 UTC | 10m |
| 2026-05-13 | CSZ8991 | CAN → HAK | May 13, 09:45 UTC | May 13, 10:00 UTC | 15m |
| 2026-05-10 | CSZ8906 | YTY → CAN | May 10, 06:25 UTC | May 10, 06:40 UTC | 15m |
| 2026-05-09 | CSZ9195 | PEK → TFU | May 9, 01:00 UTC | May 9, 01:15 UTC | 15m |
| 2026-05-05 | CSZ9195 | PEK → TFU | May 5, 01:00 UTC | May 5, 01:20 UTC | 20m |
| 2026-05-03 | CSZ8034 | HKG → TFU | May 3, 12:05 UTC | May 3, 12:20 UTC | 15m |
| 2026-05-03 | CSZ8033 | TFU → HKG | May 3, 10:05 UTC | May 3, 10:25 UTC | 20m |
| 2026-05-03 | CSZ8033 | TFU → HKG | May 3, 09:20 UTC | May 3, 09:30 UTC | 10m |
| 2026-04-27 | CSZ8991 | CAN → HAK | Apr 27, 08:35 UTC | Apr 27, 08:45 UTC | 10m |
| 2026-04-23 | CSZ9213 | SZX → XIY | Apr 23, 15:35 UTC | Apr 23, 15:50 UTC | 15m |
| 2026-04-23 | CSZ9302 | CGO → SZX | Apr 23, 12:30 UTC | Apr 23, 12:40 UTC | 10m |
| 2026-04-23 | CSZ9302 | CGO → SZX | Apr 23, 09:25 UTC | Apr 23, 09:35 UTC | 10m |
| 2026-04-23 | CSZ9301 | SZX → CGO | Apr 23, 00:05 UTC | Apr 23, 00:20 UTC | 15m |
| 2026-04-22 | CSZ8984 | - | Apr 22, 14:35 UTC | Apr 22, 14:45 UTC | 10m |
| 2026-04-22 | CSZ8983 | - | Apr 22, 08:40 UTC | Apr 22, 09:05 UTC | 25m |
| 2026-04-22 | CSZ9453 | SZX → KMG | Apr 22, 02:00 UTC | Apr 22, 02:20 UTC | 20m |
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-6565 page for operator, model, and routing details .