sensors Mode-S transponder
780F04
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8327 · AIRBUS A-320
- Hex
- 780F04
- Octal
- 36007404
- Decimal
- 7,868,164
- Country
- CN
- Tail
- B-8327
- Type
- A320
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 12:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 780F04 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 |
|---|---|---|---|
| CQH7432 | Spring Airlines | 4 | 2026-06-02 |
| CQH7206 | - | 4 | 2026-07-11 |
| CQH6887 | Spring Airlines | 4 | 2026-07-26 |
| CQH6466 | Spring Airlines | 4 | 2026-07-24 |
| CQH6217 | - | 4 | 2026-06-29 |
| CQH6465 | Spring Airlines | 3 | 2026-07-24 |
| CQH6218 | - | 3 | 2026-06-30 |
| CQH8933 | Spring Airlines | 2 | 2026-05-23 |
| CQH8756 | Spring Airlines | 2 | 2026-05-22 |
| CQH8755 | Spring Airlines | 2 | 2026-05-22 |
| CQH8731 | - | 2 | 2026-07-18 |
| CQH8728 | - | 2 | 2026-06-16 |
| CQH7518 | Spring Airlines | 2 | 2026-04-28 |
| CQH7512 | Spring Airlines | 2 | 2026-06-05 |
| CQH7501 | - | 2 | 2026-06-21 |
| CQH7431 | Spring Airlines | 2 | 2026-06-02 |
| CQH7348 | - | 2 | 2026-07-21 |
| CQH6609 | Spring Airlines | 2 | 2026-05-22 |
| CQH8934 | Spring Airlines | 1 | 2026-05-23 |
| CQH8920 | Spring Airlines | 1 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CQH6887 | SHE → TYN | Jul 26, 11:55 UTC | Jul 26, 12:10 UTC | 15m |
| 2026-07-25 | CQH8920 | SHE → HGH | Jul 25, 06:55 UTC | Jul 25, 10:35 UTC | 3h 40m |
| 2026-07-25 | CQH6787 | SJW → LHW | Jul 25, 00:00 UTC | Jul 25, 00:10 UTC | 10m |
| 2026-07-24 | CQH6466 | BKK → NNG | Jul 24, 14:40 UTC | Jul 24, 14:55 UTC | 15m |
| 2026-07-24 | CQH6466 | BKK → NNG | Jul 24, 08:35 UTC | Jul 24, 09:00 UTC | 25m |
| 2026-07-24 | CQH6465 | NNG → BKK | Jul 24, 05:20 UTC | Jul 24, 07:00 UTC | 1h 40m |
| 2026-07-21 | CQH7348 | - | Jul 21, 14:50 UTC | Jul 21, 15:10 UTC | 20m |
| 2026-07-21 | CQH7347 | CAN → SGN | Jul 21, 09:35 UTC | Jul 21, 09:45 UTC | 10m |
| 2026-07-20 | CQH8772 | HKT → CAN | Jul 20, 14:50 UTC | Jul 20, 18:30 UTC | 3h 40m |
| 2026-07-20 | CQH8771 | CAN → HKT | Jul 20, 13:10 UTC | Jul 20, 13:20 UTC | 10m |
| 2026-07-18 | CQH8731 | - | Jul 18, 13:25 UTC | Jul 18, 14:05 UTC | 40m |
| 2026-07-17 | CQH6887 | - | Jul 17, 11:55 UTC | Jul 17, 12:15 UTC | 20m |
| 2026-07-17 | CQH7050 | - | Jul 17, 03:14 UTC | Jul 17, 03:55 UTC | 40m |
| 2026-07-17 | CQH7049 | - | Jul 17, 01:29 UTC | Jul 17, 02:05 UTC | 35m |
| 2026-07-16 | CQH6900 | - | Jul 16, 13:20 UTC | Jul 16, 13:40 UTC | 20m |
| 2026-07-16 | CQH6899 | - | Jul 16, 11:50 UTC | Jul 16, 12:09 UTC | 20m |
| 2026-07-16 | CQH8810 | - | Jul 16, 03:45 UTC | Jul 16, 04:25 UTC | 40m |
| 2026-07-14 | CQH8892 | - | Jul 14, 06:20 UTC | Jul 14, 08:40 UTC | 2h 20m |
| 2026-07-14 | CQH8891 | - | Jul 14, 02:15 UTC | Jul 14, 03:05 UTC | 50m |
| 2026-07-11 | CQH7206 | - | Jul 11, 13:50 UTC | Jul 11, 14:10 UTC | 20m |
| 2026-07-10 | CQH6732 | - | Jul 10, 13:10 UTC | Jul 11, 04:50 UTC | 15h 40m |
| 2026-07-09 | CQH6731 | - | Jul 9, 23:55 UTC | Jul 10, 11:10 UTC | 11h 15m |
| 2026-07-06 | CQH7348 | - | Jul 6, 17:50 UTC | Jul 6, 18:15 UTC | 25m |
| 2026-07-05 | CQH7256 | - | Jul 5, 13:20 UTC | Jul 5, 13:35 UTC | 15m |
| 2026-07-05 | CQH7255 | - | Jul 5, 08:20 UTC | Jul 5, 08:30 UTC | 10m |
| 2026-07-04 | CQH7588 | CJU → SHE | Jul 4, 03:00 UTC | Jul 4, 03:30 UTC | 30m |
| 2026-07-03 | CQH7587 | SHE → CJU | Jul 3, 11:05 UTC | Jul 4, 01:25 UTC | 14h 20m |
| 2026-07-02 | CQH8786 | - | Jul 2, 02:25 UTC | Jul 2, 11:35 UTC | 9h 10m |
| 2026-07-01 | CQH7606 | - | Jul 1, 15:05 UTC | Jul 2, 11:35 UTC | 20h 30m |
| 2026-06-30 | CQH6218 | - | Jun 30, 11:30 UTC | Jul 1, 06:10 UTC | 18h 40m |
| 2026-06-29 | CQH6217 | - | Jun 29, 14:14 UTC | Jun 30, 10:20 UTC | 20h 6m |
| 2026-06-29 | CQH6217 | - | Jun 29, 10:24 UTC | Jun 30, 09:00 UTC | 22h 36m |
| 2026-06-28 | CQH7277 | - | Jun 28, 02:25 UTC | Jun 28, 02:34 UTC | 10m |
| 2026-06-25 | CQH7596 | - | Jun 25, 07:05 UTC | Jun 25, 07:19 UTC | 15m |
| 2026-06-22 | CQH6888 | TYN → SHE | Jun 22, 14:34 UTC | Jun 22, 14:49 UTC | 15m |
| 2026-06-22 | CQH6887 | SHE → TYN | Jun 22, 11:54 UTC | Jun 22, 12:05 UTC | 10m |
| 2026-06-21 | CQH7507 | - | Jun 21, 10:14 UTC | Jun 22, 02:45 UTC | 16h 30m |
| 2026-06-21 | CQH7502 | - | Jun 21, 04:14 UTC | Jun 22, 02:45 UTC | 22h 30m |
| 2026-06-21 | CQH7501 | - | Jun 21, 02:10 UTC | Jun 21, 02:35 UTC | 25m |
| 2026-06-20 | CQH7501 | - | Jun 20, 06:35 UTC | Jun 21, 02:35 UTC | 20h 0m |
| 2026-06-19 | CQH7508 | - | Jun 19, 14:49 UTC | Jun 20, 06:45 UTC | 15h 55m |
| 2026-06-19 | CQH6887 | SHE → TYN | Jun 19, 12:09 UTC | Jun 19, 12:25 UTC | 15m |
| 2026-06-18 | CQH6320 | - | Jun 18, 08:50 UTC | Jun 18, 09:00 UTC | 10m |
| 2026-06-16 | CQH8728 | - | Jun 16, 04:05 UTC | Jun 16, 09:20 UTC | 5h 15m |
| 2026-06-12 | CQH8804 | - | Jun 12, 14:30 UTC | Jun 12, 14:55 UTC | 25m |
| 2026-06-05 | CQH7556 | SZX → SHA | Jun 5, 22:15 UTC | Jun 5, 22:25 UTC | 10m |
| 2026-06-05 | CQH6874 | NGB → SZX | Jun 5, 17:30 UTC | Jun 5, 17:40 UTC | 10m |
| 2026-06-05 | CQH8632 | ZUH → NGB | Jun 5, 13:00 UTC | Jun 5, 13:10 UTC | 10m |
| 2026-06-05 | CQH7512 | NGB → CAN | Jun 5, 01:20 UTC | Jun 5, 02:00 UTC | 40m |
| 2026-06-04 | CQH7512 | NGB → CAN | Jun 4, 05:00 UTC | Jun 5, 02:00 UTC | 21h 0m |
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-8327 page for operator, model, and routing details .