sensors Mode-S transponder
780568
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6569 · AIRBUS A-320
- Hex
- 780568
- Octal
- 36002550
- Decimal
- 7,865,704
- Country
- CN
- Tail
- B-6569
- Type
- A320
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 780568 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 |
|---|---|---|---|
| CSZ9195 | Shenzhen Airlines | 5 | 2026-07-26 |
| CSZ9196 | Shenzhen Airlines | 4 | 2026-07-26 |
| CSZ8565 | - | 4 | 2026-07-07 |
| CSZ9964 | Shenzhen Airlines | 2 | 2026-06-05 |
| CSZ9962 | - | 2 | 2026-07-14 |
| CSZ9415 | Shenzhen Airlines | 2 | 2026-06-17 |
| CSZ8423 | - | 2 | 2026-07-04 |
| CSZ9966 | - | 1 | 2026-06-09 |
| CSZ9961 | - | 1 | 2026-07-13 |
| CSZ9870 | - | 1 | 2026-06-25 |
| CSZ9857 | Shenzhen Airlines | 1 | 2026-05-19 |
| CSZ9850 | Shenzhen Airlines | 1 | 2026-04-29 |
| CSZ9843 | Shenzhen Airlines | 1 | 2026-04-29 |
| CSZ9723 | - | 1 | 2026-05-16 |
| CSZ9606 | Shenzhen Airlines | 1 | 2026-05-17 |
| CSZ9455 | Shenzhen Airlines | 1 | 2026-05-19 |
| CSZ9121 | - | 1 | 2026-07-16 |
| CSZ8996 | - | 1 | 2026-07-15 |
| CSZ8995 | - | 1 | 2026-07-15 |
| CSZ8993 | Shenzhen Airlines | 1 | 2026-05-07 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CSZ9196 | TFU → PEK | Jul 26, 14:45 UTC | Jul 26, 15:10 UTC | 25m |
| 2026-07-26 | CSZ9195 | PEK → TFU | Jul 26, 01:20 UTC | Jul 26, 01:40 UTC | 20m |
| 2026-07-25 | CSZ9196 | TFU → PEK | Jul 25, 09:45 UTC | Jul 25, 15:15 UTC | 5h 30m |
| 2026-07-22 | CSZ8897 | CAN → HAK | Jul 22, 23:35 UTC | Jul 22, 23:45 UTC | 10m |
| 2026-07-19 | CSZ9195 | - | Jul 19, 01:10 UTC | Jul 19, 01:35 UTC | 25m |
| 2026-07-18 | CSZ9196 | - | Jul 18, 01:05 UTC | Jul 18, 15:05 UTC | 14h 1m |
| 2026-07-17 | CSZ9196 | - | Jul 17, 15:25 UTC | Jul 17, 16:04 UTC | 40m |
| 2026-07-16 | CSZ9121 | - | Jul 16, 00:25 UTC | Jul 16, 00:35 UTC | 10m |
| 2026-07-15 | CSZ8996 | - | Jul 15, 17:10 UTC | Jul 15, 17:20 UTC | 10m |
| 2026-07-15 | CSZ8995 | - | Jul 15, 11:15 UTC | Jul 15, 11:25 UTC | 10m |
| 2026-07-14 | CSZ9962 | - | Jul 14, 23:45 UTC | Jul 15, 00:20 UTC | 35m |
| 2026-07-13 | CSZ9961 | - | Jul 13, 23:15 UTC | Jul 14, 00:05 UTC | 50m |
| 2026-07-09 | CSZ9195 | - | Jul 9, 01:25 UTC | Jul 9, 01:45 UTC | 20m |
| 2026-07-07 | CSZ8565 | - | Jul 7, 01:40 UTC | Jul 7, 05:45 UTC | 4h 5m |
| 2026-07-06 | CSZ8565 | - | Jul 6, 01:35 UTC | Jul 6, 04:45 UTC | 3h 10m |
| 2026-07-04 | CSZ8423 | - | Jul 4, 06:20 UTC | Jul 4, 10:45 UTC | 4h 25m |
| 2026-07-03 | CSZ8424 | - | Jul 3, 11:40 UTC | Jul 4, 06:35 UTC | 18h 55m |
| 2026-07-03 | CSZ8423 | - | Jul 3, 07:15 UTC | Jul 3, 11:55 UTC | 4h 40m |
| 2026-06-25 | CSZ9870 | - | Jun 25, 16:24 UTC | Jun 25, 16:39 UTC | 15m |
| 2026-06-17 | CSZ9415 | SZX → CTU | Jun 17, 22:50 UTC | Jun 17, 23:00 UTC | 10m |
| 2026-06-14 | CSZ8946 | - | Jun 14, 16:20 UTC | Jun 14, 16:30 UTC | 10m |
| 2026-06-09 | CSZ9966 | - | Jun 9, 10:10 UTC | Jun 9, 10:35 UTC | 25m |
| 2026-06-05 | CSZ9964 | HGH → SZX | Jun 5, 09:25 UTC | Jun 5, 10:10 UTC | 45m |
| 2026-05-28 | CSZ9195 | PEK → TFU | May 28, 01:05 UTC | May 28, 01:30 UTC | 25m |
| 2026-05-27 | CSZ9195 | PEK → TFU | May 27, 01:14 UTC | May 27, 01:39 UTC | 25m |
| 2026-05-25 | CSZ8566 | - | May 25, 05:00 UTC | May 25, 05:10 UTC | 10m |
| 2026-05-25 | CSZ8565 | - | May 25, 02:10 UTC | May 25, 02:30 UTC | 20m |
| 2026-05-21 | CSZ8565 | - | May 21, 02:55 UTC | May 21, 05:55 UTC | 3h 0m |
| 2026-05-19 | CSZ9857 | SZX → CGQ | May 19, 13:55 UTC | May 19, 14:05 UTC | 10m |
| 2026-05-19 | CSZ9455 | SZX → KMG | May 19, 04:20 UTC | May 19, 04:35 UTC | 15m |
| 2026-05-17 | CSZ9606 | JDZ → CAN | May 17, 13:01 UTC | May 18, 02:35 UTC | 13h 35m |
| 2026-05-16 | CSZ9723 | - | May 16, 02:10 UTC | May 16, 10:35 UTC | 8h 26m |
| 2026-05-14 | CSZ8991 | CAN → HAK | May 14, 09:25 UTC | May 14, 09:35 UTC | 10m |
| 2026-05-09 | CSZ9964 | HGH → SZX | May 9, 07:45 UTC | May 9, 07:55 UTC | 10m |
| 2026-05-07 | CSZ8993 | CAN → HAK | May 7, 14:55 UTC | May 7, 15:05 UTC | 10m |
| 2026-05-04 | CSZ9962 | - | May 4, 00:15 UTC | May 4, 00:34 UTC | 20m |
| 2026-04-29 | CSZ9415 | SZX → CTU | Apr 29, 22:40 UTC | Apr 29, 22:55 UTC | 15m |
| 2026-04-29 | CSZ9850 | NKG → SZX | Apr 29, 15:55 UTC | Apr 29, 16:15 UTC | 20m |
| 2026-04-29 | CSZ9843 | SZX → URC | Apr 29, 01:45 UTC | Apr 29, 01:59 UTC | 15m |
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-6569 page for operator, model, and routing details .