sensors Mode-S transponder
781D05
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-327Z · AIRBUS A-320neo
- Hex
- 781D05
- Octal
- 36016405
- Decimal
- 7,871,749
- Country
- CN
- Tail
- B-327Z
- Type
- A20N
- Flights observed
- 151
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 20:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 781D05 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 |
|---|---|---|---|
| CQH6523 | - | 32 | 2026-07-19 |
| CQH8597 | - | 18 | 2026-07-13 |
| CQH8666 | Spring Airlines | 12 | 2026-07-21 |
| CQH8665 | Spring Airlines | 11 | 2026-07-25 |
| CQH6524 | - | 11 | 2026-07-19 |
| CQH7259 | - | 7 | 2026-06-23 |
| CQH8598 | - | 5 | 2026-07-13 |
| CQH8593 | Spring Airlines | 4 | 2026-07-25 |
| CQH8792 | - | 3 | 2026-06-20 |
| CQH8791 | - | 3 | 2026-06-19 |
| CQH8594 | Spring Airlines | 3 | 2026-07-26 |
| CQH8533 | - | 2 | 2026-05-20 |
| CQH7496 | Spring Airlines | 2 | 2026-05-21 |
| CQH7057 | Spring Airlines | 2 | 2026-06-04 |
| CQH7008 | Spring Airlines | 2 | 2026-05-20 |
| CQH6922 | Spring Airlines | 2 | 2026-04-26 |
| CQH6921 | Spring Airlines | 2 | 2026-04-26 |
| CQH8952 | - | 1 | 2026-07-05 |
| CQH8951 | - | 1 | 2026-07-04 |
| CQH8934 | Spring Airlines | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CQH8594 | BKI → PVG | Jul 26, 20:20 UTC | Jul 26, 20:55 UTC | 35m |
| 2026-07-25 | CQH8593 | PVG → BKI | Jul 25, 22:40 UTC | Jul 26, 19:10 UTC | 20h 31m |
| 2026-07-25 | CQH8551 | PVG → SIN | Jul 25, 20:45 UTC | Jul 25, 20:55 UTC | 10m |
| 2026-07-25 | CQH8665 | PVG → HKT | Jul 25, 02:00 UTC | Jul 25, 17:40 UTC | 15h 40m |
| 2026-07-22 | CQH8594 | - | Jul 22, 00:45 UTC | Jul 22, 03:15 UTC | 2h 30m |
| 2026-07-21 | CQH8593 | - | Jul 21, 23:05 UTC | Jul 21, 23:25 UTC | 20m |
| 2026-07-21 | CQH8666 | HKT → PVG | Jul 21, 02:05 UTC | Jul 21, 21:15 UTC | 19h 10m |
| 2026-07-20 | CQH8666 | HKT → PVG | Jul 20, 16:00 UTC | Jul 21, 10:55 UTC | 18h 55m |
| 2026-07-20 | CQH6515 | PVG → KUL | Jul 20, 04:15 UTC | Jul 20, 13:55 UTC | 9h 40m |
| 2026-07-19 | CQH6524 | - | Jul 19, 12:40 UTC | Jul 20, 01:35 UTC | 12h 55m |
| 2026-07-19 | CQH6523 | - | Jul 19, 11:00 UTC | Jul 19, 11:15 UTC | 15m |
| 2026-07-18 | CQH8594 | - | Jul 18, 23:20 UTC | Jul 19, 08:05 UTC | 8h 45m |
| 2026-07-18 | CQH8593 | - | Jul 18, 05:00 UTC | Jul 18, 22:10 UTC | 17h 10m |
| 2026-07-18 | CQH8593 | - | Jul 18, 03:10 UTC | Jul 18, 22:10 UTC | 19h 0m |
| 2026-07-17 | CQH8665 | PVG → HKT | Jul 17, 13:35 UTC | Jul 18, 08:25 UTC | 18h 51m |
| 2026-07-17 | CQH6899 | - | Jul 17, 12:04 UTC | Jul 17, 12:40 UTC | 35m |
| 2026-07-17 | CQH8602 | NGO → PVG | Jul 17, 07:00 UTC | Jul 17, 08:04 UTC | 1h 5m |
| 2026-07-17 | CQH8601 | PVG → NGO | Jul 17, 04:35 UTC | Jul 17, 05:39 UTC | 1h 5m |
| 2026-07-15 | CQH6524 | - | Jul 15, 10:50 UTC | Jul 15, 15:00 UTC | 4h 10m |
| 2026-07-15 | CQH6523 | - | Jul 15, 09:15 UTC | Jul 15, 09:35 UTC | 20m |
| 2026-07-15 | CQH6523 | - | Jul 15, 05:30 UTC | Jul 15, 06:30 UTC | 1h 0m |
| 2026-07-13 | CQH8598 | - | Jul 13, 08:45 UTC | Jul 13, 12:55 UTC | 4h 10m |
| 2026-07-13 | CQH8597 | - | Jul 13, 03:25 UTC | Jul 13, 06:40 UTC | 3h 15m |
| 2026-07-10 | CQH6524 | - | Jul 10, 13:45 UTC | Jul 10, 17:50 UTC | 4h 5m |
| 2026-07-10 | CQH6523 | - | Jul 10, 12:05 UTC | Jul 10, 12:25 UTC | 20m |
| 2026-07-10 | CQH7050 | - | Jul 10, 04:30 UTC | Jul 10, 08:55 UTC | 4h 25m |
| 2026-07-09 | CQH8666 | - | Jul 9, 07:20 UTC | Jul 10, 03:15 UTC | 19h 55m |
| 2026-07-09 | CQH8665 | - | Jul 9, 07:10 UTC | Jul 10, 03:15 UTC | 20h 5m |
| 2026-07-08 | CQH8665 | - | Jul 8, 11:20 UTC | Jul 9, 09:50 UTC | 22h 30m |
| 2026-07-08 | CQH8666 | - | Jul 8, 09:20 UTC | Jul 9, 09:15 UTC | 23h 55m |
| 2026-07-08 | CQH8666 | - | Jul 8, 03:55 UTC | Jul 8, 13:10 UTC | 9h 15m |
| 2026-07-06 | CQH8665 | - | Jul 6, 03:45 UTC | Jul 6, 11:55 UTC | 8h 10m |
| 2026-07-05 | CQH8952 | - | Jul 5, 03:30 UTC | Jul 5, 04:10 UTC | 40m |
| 2026-07-04 | CQH8951 | - | Jul 4, 10:10 UTC | Jul 5, 02:15 UTC | 16h 5m |
| 2026-07-04 | CQH8597 | - | Jul 4, 05:00 UTC | Jul 4, 08:35 UTC | 3h 35m |
| 2026-07-03 | CQH8597 | - | Jul 3, 13:05 UTC | Jul 4, 08:35 UTC | 19h 30m |
| 2026-07-03 | CQH8597 | - | Jul 3, 09:20 UTC | Jul 4, 08:35 UTC | 23h 15m |
| 2026-07-02 | CQH8597 | - | Jul 2, 14:00 UTC | Jul 3, 07:50 UTC | 17h 50m |
| 2026-07-02 | CQH8597 | - | Jul 2, 10:40 UTC | Jul 3, 07:50 UTC | 21h 10m |
| 2026-07-02 | CQH6523 | - | Jul 2, 08:40 UTC | Jul 2, 08:55 UTC | 15m |
| 2026-07-01 | CQH6523 | - | Jul 1, 14:45 UTC | Jul 2, 05:50 UTC | 15h 5m |
| 2026-07-01 | CQH6524 | - | Jul 1, 10:40 UTC | Jul 2, 05:50 UTC | 19h 10m |
| 2026-07-01 | CQH6523 | - | Jul 1, 08:40 UTC | Jul 1, 09:05 UTC | 25m |
| 2026-07-01 | CQH6523 | - | Jul 1, 04:50 UTC | Jul 1, 05:20 UTC | 30m |
| 2026-06-30 | CQH6523 | - | Jun 30, 09:50 UTC | Jul 1, 05:20 UTC | 19h 30m |
| 2026-06-30 | CQH8666 | - | Jun 30, 07:20 UTC | Jul 1, 05:20 UTC | 22h 0m |
| 2026-06-30 | CQH8666 | - | Jun 30, 07:10 UTC | Jul 1, 05:15 UTC | 22h 5m |
| 2026-06-30 | CQH8665 | - | Jun 30, 01:40 UTC | Jun 30, 09:50 UTC | 8h 10m |
| 2026-06-29 | CQH8665 | - | Jun 29, 13:00 UTC | Jun 30, 09:50 UTC | 20h 51m |
| 2026-06-29 | CQH8665 | - | Jun 29, 09:20 UTC | Jun 30, 09:05 UTC | 23h 46m |
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-327Z page for operator, model, and routing details .