sensors Mode-S transponder
780552
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6562 · AIRBUS A-320
- Hex
- 780552
- Octal
- 36002522
- Decimal
- 7,865,682
- Country
- CN
- Tail
- B-6562
- Type
- A320
- Flights observed
- 67
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 780552 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 |
|---|---|---|---|
| CQH7596 | - | 4 | 2026-07-08 |
| CQH6540 | Spring Airlines | 4 | 2026-04-19 |
| CQH8753 | - | 3 | 2026-07-02 |
| CQH7595 | - | 3 | 2026-07-08 |
| CQH7302 | - | 3 | 2026-04-14 |
| CQH6873 | - | 3 | 2026-07-03 |
| CQH6539 | Spring Airlines | 3 | 2026-04-19 |
| CQH8684 | Spring Airlines | 2 | 2026-05-21 |
| CQH8632 | Spring Airlines | 2 | 2026-06-14 |
| CQH7502 | Spring Airlines | 2 | 2026-05-24 |
| CQH7501 | Spring Airlines | 2 | 2026-05-24 |
| CQH6596 | Spring Airlines | 2 | 2026-07-02 |
| CQH8933 | - | 1 | 2026-06-20 |
| CQH8754 | - | 1 | 2026-07-03 |
| CQH8673 | Spring Airlines | 1 | 2026-05-09 |
| CQH8672 | Spring Airlines | 1 | 2026-04-21 |
| CQH8671 | Spring Airlines | 1 | 2026-04-19 |
| CQH8631 | Spring Airlines | 1 | 2026-04-23 |
| CQH8614 | Spring Airlines | 1 | 2026-04-18 |
| CQH8545 | Spring Airlines | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | CQH7596 | - | Jul 8, 07:50 UTC | Jul 8, 08:00 UTC | 10m |
| 2026-07-08 | CQH7595 | - | Jul 8, 06:00 UTC | Jul 8, 06:20 UTC | 20m |
| 2026-07-08 | CQH7595 | - | Jul 8, 04:25 UTC | Jul 8, 04:50 UTC | 25m |
| 2026-07-06 | CQH7596 | - | Jul 6, 06:50 UTC | Jul 6, 07:00 UTC | 10m |
| 2026-07-04 | CQH6775 | - | Jul 4, 23:20 UTC | Jul 5, 13:20 UTC | 14h 0m |
| 2026-07-03 | CQH6873 | - | Jul 3, 08:05 UTC | Jul 3, 08:15 UTC | 10m |
| 2026-07-03 | CQH8754 | - | Jul 3, 04:50 UTC | Jul 3, 05:00 UTC | 10m |
| 2026-07-02 | CQH8753 | - | Jul 2, 22:40 UTC | Jul 2, 23:00 UTC | 20m |
| 2026-07-02 | CQH6596 | TNA → SZX | Jul 2, 16:30 UTC | Jul 2, 16:55 UTC | 25m |
| 2026-06-29 | CQH6156 | - | Jun 29, 05:34 UTC | Jun 29, 05:50 UTC | 15m |
| 2026-06-26 | CQH7347 | - | Jun 26, 09:10 UTC | Jun 26, 09:20 UTC | 10m |
| 2026-06-24 | CQH6743 | - | Jun 24, 15:29 UTC | Jun 24, 15:39 UTC | 10m |
| 2026-06-23 | CQH6538 | - | Jun 23, 09:20 UTC | Jun 23, 09:45 UTC | 25m |
| 2026-06-23 | CQH6537 | - | Jun 23, 06:59 UTC | Jun 23, 07:19 UTC | 20m |
| 2026-06-21 | CQH8512 | - | Jun 21, 01:39 UTC | Jun 21, 13:34 UTC | 11h 55m |
| 2026-06-20 | CQH8933 | - | Jun 20, 22:05 UTC | Jun 21, 00:14 UTC | 2h 10m |
| 2026-06-14 | CQH8632 | ZUH → NGB | Jun 14, 10:50 UTC | Jun 14, 11:05 UTC | 15m |
| 2026-06-12 | CQH7385 | NGB → SYX | Jun 12, 11:25 UTC | Jun 12, 14:45 UTC | 3h 20m |
| 2026-06-12 | CQH6873 | SZX → NGB | Jun 12, 06:20 UTC | Jun 12, 06:30 UTC | 10m |
| 2026-06-11 | CQH8753 | SZX → XIY | Jun 11, 22:45 UTC | Jun 11, 23:00 UTC | 15m |
| 2026-06-11 | CQH6874 | NGB → SZX | Jun 11, 16:35 UTC | Jun 11, 17:30 UTC | 55m |
| 2026-06-07 | CQH6600 | KHN → HRB | Jun 7, 10:15 UTC | Jun 7, 14:30 UTC | 4h 15m |
| 2026-06-05 | CQH7050 | CJJ → PVG | Jun 5, 03:15 UTC | Jun 5, 10:40 UTC | 7h 25m |
| 2026-06-05 | CQH7049 | PVG → CJJ | Jun 5, 01:15 UTC | Jun 5, 01:55 UTC | 40m |
| 2026-05-27 | CQH6809 | SHE → KWL | May 27, 09:20 UTC | May 28, 00:25 UTC | 15h 5m |
| 2026-05-25 | CQH6888 | TYN → SHE | May 25, 14:30 UTC | May 25, 14:40 UTC | 10m |
| 2026-05-24 | CQH7502 | BKK → TFU | May 24, 04:30 UTC | May 24, 10:15 UTC | 5h 45m |
| 2026-05-24 | CQH7501 | TFU → BKK | May 24, 01:55 UTC | May 24, 02:55 UTC | 1h 0m |
| 2026-05-22 | CQH6313 | CGQ → NGB | May 22, 03:30 UTC | May 22, 04:05 UTC | 35m |
| 2026-05-21 | CQH8684 | HRB → NGB | May 21, 06:15 UTC | May 22, 04:05 UTC | 21h 50m |
| 2026-05-20 | CQH8684 | HRB → NGB | May 20, 12:15 UTC | May 21, 06:30 UTC | 18h 15m |
| 2026-05-20 | CQH8545 | CGQ → NGB | May 20, 04:15 UTC | May 20, 12:20 UTC | 8h 6m |
| 2026-05-18 | CQH7416 | CSX → LHW | May 18, 09:10 UTC | May 18, 09:35 UTC | 25m |
| 2026-05-13 | CQH7251 | - | May 13, 11:15 UTC | May 13, 11:25 UTC | 10m |
| 2026-05-13 | CQH7596 | ZUH → YTY | May 13, 06:05 UTC | May 13, 06:20 UTC | 15m |
| 2026-05-09 | CQH8673 | SJW → HRB | May 9, 08:55 UTC | May 9, 13:15 UTC | 4h 20m |
| 2026-05-04 | CQH7025 | SHE → HDG | May 4, 05:30 UTC | May 4, 05:40 UTC | 10m |
| 2026-05-03 | CQH6887 | SHE → TYN | May 3, 11:50 UTC | May 3, 12:05 UTC | 15m |
| 2026-04-30 | CQH7596 | ZUH → YTY | Apr 30, 07:05 UTC | Apr 30, 07:15 UTC | 10m |
| 2026-04-30 | CQH7595 | YTY → ZUH | Apr 30, 04:35 UTC | Apr 30, 04:45 UTC | 10m |
| 2026-04-29 | CQH7502 | BKK → TFU | Apr 29, 04:29 UTC | Apr 29, 10:15 UTC | 5h 46m |
| 2026-04-29 | CQH7501 | TFU → BKK | Apr 29, 02:20 UTC | Apr 29, 02:55 UTC | 35m |
| 2026-04-28 | CQH7508 | - | Apr 28, 06:40 UTC | Apr 28, 06:50 UTC | 10m |
| 2026-04-28 | CQH6173 | - | Apr 28, 04:15 UTC | Apr 28, 04:30 UTC | 15m |
| 2026-04-24 | CQH6954 | SHE → SJW | Apr 24, 13:55 UTC | Apr 24, 14:05 UTC | 10m |
| 2026-04-23 | CQH8632 | ZUH → NGB | Apr 23, 13:00 UTC | Apr 23, 13:10 UTC | 10m |
| 2026-04-23 | CQH8631 | NGB → ZUH | Apr 23, 10:10 UTC | Apr 23, 11:10 UTC | 1h 0m |
| 2026-04-22 | CQH6873 | SZX → NGB | Apr 22, 06:25 UTC | Apr 22, 06:35 UTC | 10m |
| 2026-04-21 | CQH8753 | SZX → XIY | Apr 21, 22:40 UTC | Apr 21, 22:50 UTC | 10m |
| 2026-04-21 | CQH6728 | NNY → SZX | Apr 21, 17:30 UTC | Apr 21, 17:45 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-6562 page for operator, model, and routing details .