sensors Mode-S transponder
781C77
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-326F · AIRBUS A-320neo
- Hex
- 781C77
- Octal
- 36016167
- Decimal
- 7,871,607
- Country
- CN
- Tail
- B-326F
- Type
- A20N
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781C77 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 |
|---|---|---|---|
| CSZ9748 | - | 8 | 2026-06-20 |
| CSZ9747 | - | 6 | 2026-06-20 |
| CSZ9728 | - | 4 | 2026-07-01 |
| CSZ9727 | - | 4 | 2026-07-01 |
| CSZ9723 | - | 3 | 2026-04-28 |
| CSZ9711 | - | 3 | 2026-07-04 |
| CSZ8903 | Shenzhen Airlines | 3 | 2026-06-13 |
| CSZ9944 | Shenzhen Airlines | 2 | 2026-04-16 |
| CSZ9848 | Shenzhen Airlines | 2 | 2026-04-15 |
| CSZ9847 | Shenzhen Airlines | 2 | 2026-04-15 |
| CSZ9234 | - | 2 | 2026-04-16 |
| CSZ9233 | Shenzhen Airlines | 2 | 2026-04-16 |
| CSZ8309 | - | 2 | 2026-07-10 |
| CSZ9994 | - | 1 | 2026-06-11 |
| CSZ9982 | Shenzhen Airlines | 1 | 2026-05-13 |
| CSZ9974 | Shenzhen Airlines | 1 | 2026-06-08 |
| CSZ9973 | Shenzhen Airlines | 1 | 2026-05-23 |
| CSZ9966 | - | 1 | 2026-06-06 |
| CSZ9943 | Shenzhen Airlines | 1 | 2026-04-15 |
| CSZ9843 | Shenzhen Airlines | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | CSZ8594 | - | Jul 11, 07:50 UTC | Jul 11, 08:05 UTC | 15m |
| 2026-07-10 | CSZ8310 | - | Jul 10, 13:50 UTC | Jul 11, 00:50 UTC | 11h 1m |
| 2026-07-10 | CSZ8309 | - | Jul 10, 09:35 UTC | Jul 10, 09:45 UTC | 10m |
| 2026-07-08 | CSZ830Q | - | Jul 8, 06:55 UTC | Jul 8, 10:40 UTC | 3h 45m |
| 2026-07-06 | CSZ9652 | - | Jul 6, 01:20 UTC | Jul 6, 01:35 UTC | 15m |
| 2026-07-04 | CSZ9711 | - | Jul 4, 03:45 UTC | Jul 4, 14:05 UTC | 10h 20m |
| 2026-07-03 | CSZ8309 | - | Jul 3, 11:25 UTC | Jul 3, 11:35 UTC | 10m |
| 2026-07-01 | CSZ9728 | - | Jul 1, 13:35 UTC | Jul 2, 01:35 UTC | 12h 0m |
| 2026-07-01 | CSZ9727 | - | Jul 1, 06:30 UTC | Jul 1, 06:45 UTC | 15m |
| 2026-06-29 | CSZ9651 | - | Jun 29, 13:39 UTC | Jun 29, 13:49 UTC | 10m |
| 2026-06-23 | CSZ9672 | - | Jun 23, 09:49 UTC | Jun 23, 14:19 UTC | 4h 30m |
| 2026-06-20 | CSZ9748 | - | Jun 20, 09:14 UTC | Jun 20, 13:19 UTC | 4h 5m |
| 2026-06-20 | CSZ9747 | - | Jun 20, 06:19 UTC | Jun 20, 06:39 UTC | 20m |
| 2026-06-20 | CSZ9747 | - | Jun 20, 01:34 UTC | Jun 20, 01:44 UTC | 10m |
| 2026-06-19 | CSZ9748 | - | Jun 19, 17:24 UTC | Jun 19, 17:34 UTC | 10m |
| 2026-06-13 | CSZ8903 | CAN → CGO | Jun 13, 00:00 UTC | Jun 13, 00:55 UTC | 55m |
| 2026-06-11 | CSZ9994 | - | Jun 11, 06:15 UTC | Jun 11, 06:30 UTC | 15m |
| 2026-06-10 | CSZ8991 | CAN → HAK | Jun 10, 09:00 UTC | Jun 10, 09:10 UTC | 10m |
| 2026-06-09 | CSZ8903 | CAN → CGO | Jun 9, 00:05 UTC | Jun 9, 00:20 UTC | 15m |
| 2026-06-08 | CSZ9974 | CTU → SZX | Jun 8, 17:25 UTC | Jun 8, 17:35 UTC | 10m |
| 2026-06-06 | CSZ9966 | - | Jun 6, 12:35 UTC | Jun 6, 13:15 UTC | 40m |
| 2026-05-30 | CSZ9748 | YCU → HRB | May 30, 06:30 UTC | May 30, 13:25 UTC | 6h 55m |
| 2026-05-29 | CSZ9748 | YCU → HRB | May 29, 13:10 UTC | May 30, 09:10 UTC | 20h 0m |
| 2026-05-29 | CSZ9748 | YCU → HRB | May 29, 09:10 UTC | May 30, 06:45 UTC | 21h 35m |
| 2026-05-28 | CSZ9747 | YCU → SYX | May 28, 06:15 UTC | May 28, 13:15 UTC | 7h 0m |
| 2026-05-28 | CSZ9747 | YCU → SYX | May 28, 01:30 UTC | May 28, 01:45 UTC | 15m |
| 2026-05-27 | CSZ9748 | YCU → HRB | May 27, 13:05 UTC | May 27, 13:25 UTC | 20m |
| 2026-05-27 | CSZ9747 | YCU → SYX | May 27, 01:39 UTC | May 27, 01:54 UTC | 15m |
| 2026-05-26 | CSZ9748 | YCU → HRB | May 26, 13:00 UTC | May 26, 13:19 UTC | 20m |
| 2026-05-26 | CSZ9747 | YCU → SYX | May 26, 01:34 UTC | May 26, 01:49 UTC | 15m |
| 2026-05-25 | CSZ9748 | YCU → HRB | May 25, 13:20 UTC | May 25, 13:35 UTC | 15m |
| 2026-05-23 | CSZ9973 | SZX → CTU | May 23, 08:55 UTC | May 23, 09:05 UTC | 10m |
| 2026-05-22 | CSZ8945 | - | May 22, 10:20 UTC | May 22, 10:30 UTC | 10m |
| 2026-05-13 | CSZ9982 | HGH → CAN | May 13, 14:40 UTC | May 13, 15:20 UTC | 40m |
| 2026-05-10 | CSZ8946 | - | May 10, 16:30 UTC | May 10, 16:40 UTC | 10m |
| 2026-05-10 | - | - | May 10, 08:15 UTC | May 10, 08:25 UTC | 10m |
| 2026-05-08 | CSZ8903 | CAN → CGO | May 8, 00:09 UTC | May 8, 00:29 UTC | 20m |
| 2026-05-02 | CSZ9728 | CGO → SHE | May 2, 13:35 UTC | May 3, 04:10 UTC | 14h 35m |
| 2026-05-01 | CSZ9728 | CGO → SHE | May 1, 13:50 UTC | May 2, 13:45 UTC | 23h 56m |
| 2026-05-01 | CSZ9727 | CGO → HAK | May 1, 06:30 UTC | May 1, 13:50 UTC | 7h 20m |
| 2026-04-30 | CSZ9728 | CGO → SHE | Apr 30, 13:55 UTC | May 1, 13:45 UTC | 23h 50m |
| 2026-04-30 | CSZ9727 | CGO → HAK | Apr 30, 06:30 UTC | Apr 30, 14:00 UTC | 7h 30m |
| 2026-04-29 | CSZ9727 | CGO → HAK | Apr 29, 12:55 UTC | Apr 30, 06:45 UTC | 17h 49m |
| 2026-04-29 | CSZ9711 | SHE → HFE | Apr 29, 01:50 UTC | Apr 29, 12:55 UTC | 11h 6m |
| 2026-04-28 | CSZ9723 | - | Apr 28, 07:50 UTC | Apr 29, 01:54 UTC | 18h 5m |
| 2026-04-28 | CSZ9723 | - | Apr 28, 06:45 UTC | Apr 29, 01:54 UTC | 19h 10m |
| 2026-04-28 | CSZ9723 | - | Apr 28, 02:05 UTC | Apr 28, 07:55 UTC | 5h 50m |
| 2026-04-27 | CSZ9711 | SHE → HFE | Apr 27, 02:05 UTC | Apr 27, 02:15 UTC | 10m |
| 2026-04-26 | CSZ9302 | CGO → SZX | Apr 26, 05:30 UTC | Apr 26, 06:00 UTC | 30m |
| 2026-04-26 | CSZ9301 | SZX → CGO | Apr 26, 00:05 UTC | Apr 26, 00:20 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-326F page for operator, model, and routing details .