sensors Mode-S transponder
782292
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32MS · AIRBUS A-320neo
- Hex
- 782292
- Octal
- 36021222
- Decimal
- 7,873,170
- Country
- CN
- Tail
- B-32MS
- Type
- A20N
- Flights observed
- 86
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 782292 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 |
|---|---|---|---|
| CQH7281 | Spring Airlines | 4 | 2026-06-08 |
| CQH8522 | Spring Airlines | 3 | 2026-05-17 |
| CQH8521 | Spring Airlines | 3 | 2026-05-18 |
| CQH6879 | - | 3 | 2026-06-22 |
| CQH8933 | - | 2 | 2026-07-07 |
| CQH8878 | - | 2 | 2026-07-08 |
| CQH8877 | Spring Airlines | 2 | 2026-06-06 |
| CQH8792 | Spring Airlines | 2 | 2026-06-09 |
| CQH8753 | Spring Airlines | 2 | 2026-05-29 |
| CQH8632 | - | 2 | 2026-07-10 |
| CQH8631 | - | 2 | 2026-07-10 |
| CQH8598 | Spring Airlines | 2 | 2026-05-08 |
| CQH8597 | Spring Airlines | 2 | 2026-05-08 |
| CQH8545 | - | 2 | 2026-07-09 |
| CQH8512 | - | 2 | 2026-07-08 |
| CQH7282 | Spring Airlines | 2 | 2026-04-17 |
| CQH6987 | - | 2 | 2026-05-29 |
| CQH6728 | Spring Airlines | 2 | 2026-06-04 |
| CQH6727 | Spring Airlines | 2 | 2026-06-04 |
| CQH6341 | Spring Airlines | 2 | 2026-06-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | CQH7588 | - | Jul 12, 07:55 UTC | Jul 12, 08:30 UTC | 35m |
| 2026-07-12 | CQH7587 | - | Jul 12, 05:05 UTC | Jul 12, 05:50 UTC | 45m |
| 2026-07-10 | CQH8832 | - | Jul 10, 11:20 UTC | Jul 11, 03:20 UTC | 16h 0m |
| 2026-07-10 | CQH8632 | - | Jul 10, 10:10 UTC | Jul 10, 10:20 UTC | 10m |
| 2026-07-10 | CQH8631 | - | Jul 10, 08:25 UTC | Jul 10, 08:45 UTC | 20m |
| 2026-07-09 | CQH8545 | - | Jul 9, 13:55 UTC | Jul 10, 04:40 UTC | 14h 45m |
| 2026-07-08 | CQH8545 | - | Jul 8, 16:30 UTC | Jul 9, 14:25 UTC | 21h 55m |
| 2026-07-08 | CQH8878 | - | Jul 8, 10:25 UTC | Jul 8, 16:30 UTC | 6h 5m |
| 2026-07-08 | CQH8512 | CNX → KHH | Jul 8, 01:50 UTC | Jul 8, 09:15 UTC | 7h 25m |
| 2026-07-07 | CQH8933 | - | Jul 7, 22:15 UTC | Jul 8, 00:35 UTC | 2h 20m |
| 2026-07-06 | CQH8894 | - | Jul 6, 18:10 UTC | Jul 6, 19:45 UTC | 1h 35m |
| 2026-07-06 | CQH8893 | CAN → BKK | Jul 6, 15:05 UTC | Jul 6, 17:10 UTC | 2h 5m |
| 2026-07-06 | CQH7520 | - | Jul 6, 06:25 UTC | Jul 6, 06:35 UTC | 10m |
| 2026-07-06 | CQH7519 | - | Jul 6, 04:35 UTC | Jul 6, 04:55 UTC | 20m |
| 2026-07-02 | CQH6278 | - | Jul 2, 18:30 UTC | Jul 2, 18:45 UTC | 15m |
| 2026-07-02 | CQH6278 | - | Jul 2, 15:20 UTC | Jul 2, 15:45 UTC | 25m |
| 2026-07-02 | CQH6277 | - | Jul 2, 13:35 UTC | Jul 2, 14:00 UTC | 25m |
| 2026-07-02 | CQH6277 | - | Jul 2, 10:40 UTC | Jul 2, 10:55 UTC | 15m |
| 2026-06-30 | CQH6294 | - | Jun 30, 20:05 UTC | Jun 30, 21:30 UTC | 1h 25m |
| 2026-06-30 | CQH6293 | - | Jun 30, 16:15 UTC | Jun 30, 17:35 UTC | 1h 20m |
| 2026-06-24 | CQH7596 | - | Jun 24, 06:20 UTC | Jun 24, 06:35 UTC | 15m |
| 2026-06-24 | CQH7595 | - | Jun 24, 04:39 UTC | Jun 24, 04:59 UTC | 20m |
| 2026-06-23 | CQH7502 | - | Jun 23, 04:35 UTC | Jun 23, 10:29 UTC | 5h 55m |
| 2026-06-22 | CQH6880 | - | Jun 22, 15:24 UTC | Jun 23, 02:45 UTC | 11h 20m |
| 2026-06-22 | CQH6879 | - | Jun 22, 12:59 UTC | Jun 22, 13:54 UTC | 55m |
| 2026-06-21 | CQH6879 | - | Jun 21, 15:25 UTC | Jun 22, 13:54 UTC | 22h 30m |
| 2026-06-21 | CQH6879 | - | Jun 21, 13:34 UTC | Jun 21, 14:19 UTC | 45m |
| 2026-06-10 | CQH6341 | SHE → HFE | Jun 10, 04:00 UTC | Jun 10, 04:10 UTC | 10m |
| 2026-06-09 | CQH8792 | CTS → PVG | Jun 9, 06:35 UTC | Jun 10, 04:10 UTC | 21h 35m |
| 2026-06-09 | CQH8792 | CTS → PVG | Jun 9, 05:00 UTC | Jun 10, 04:10 UTC | 23h 10m |
| 2026-06-08 | CQH8791 | PVG → CTS | Jun 8, 10:05 UTC | Jun 9, 03:20 UTC | 17h 15m |
| 2026-06-08 | CQH7281 | PVG → BKK | Jun 8, 06:25 UTC | Jun 8, 08:55 UTC | 2h 30m |
| 2026-06-07 | CQH7281 | PVG → BKK | Jun 7, 12:50 UTC | Jun 8, 08:55 UTC | 20h 5m |
| 2026-06-07 | CQH8512 | CNX → PVG | Jun 7, 01:50 UTC | Jun 7, 13:25 UTC | 11h 35m |
| 2026-06-06 | CQH8933 | CAN → CNX | Jun 6, 22:10 UTC | Jun 7, 00:30 UTC | 2h 20m |
| 2026-06-06 | CQH8934 | CNX → CAN | Jun 6, 14:30 UTC | Jun 6, 15:39 UTC | 1h 10m |
| 2026-06-06 | CQH8878 | KHH → PVG | Jun 6, 05:10 UTC | Jun 6, 13:20 UTC | 8h 10m |
| 2026-06-06 | CQH8877 | PVG → KHH | Jun 6, 03:10 UTC | Jun 6, 04:10 UTC | 1h 0m |
| 2026-06-05 | CQH8877 | PVG → KHH | Jun 5, 06:55 UTC | Jun 6, 04:10 UTC | 21h 15m |
| 2026-06-04 | CQH8671 | HIA → HRB | Jun 4, 23:05 UTC | Jun 4, 23:20 UTC | 15m |
| 2026-06-04 | CQH6728 | NNY → SZX | Jun 4, 17:40 UTC | Jun 4, 17:50 UTC | 10m |
| 2026-06-04 | CQH6727 | SZX → NNY | Jun 4, 12:20 UTC | Jun 4, 12:35 UTC | 15m |
| 2026-06-04 | CQH8672 | HIA → SZX | Jun 4, 10:40 UTC | Jun 4, 10:50 UTC | 10m |
| 2026-06-03 | CQH8936 | CGQ → PVG | Jun 3, 14:25 UTC | Jun 3, 14:50 UTC | 25m |
| 2026-05-30 | CQH6873 | SZX → NGB | May 30, 07:55 UTC | May 30, 08:25 UTC | 30m |
| 2026-05-29 | CQH8753 | SZX → XIY | May 29, 23:15 UTC | May 29, 23:30 UTC | 15m |
| 2026-05-29 | CQH6596 | TNA → SZX | May 29, 17:35 UTC | May 29, 18:00 UTC | 25m |
| 2026-05-29 | CQH6988 | - | May 29, 07:25 UTC | May 29, 09:05 UTC | 1h 40m |
| 2026-05-29 | CQH6987 | - | May 29, 04:40 UTC | May 29, 06:05 UTC | 1h 25m |
| 2026-05-28 | CQH6987 | - | May 28, 09:50 UTC | May 29, 06:05 UTC | 20h 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-32MS page for operator, model, and routing details .