sensors Mode-S transponder
781FF0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32FM · AIRBUS A-320neo
- Hex
- 781FF0
- Octal
- 36017760
- Decimal
- 7,872,496
- Country
- CN
- Tail
- B-32FM
- Type
- A20N
- Flights observed
- 64
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 25, 10:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 781FF0 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 |
|---|---|---|---|
| CQH6411 | - | 5 | 2026-07-12 |
| CQH6523 | Spring Airlines | 4 | 2026-06-02 |
| CQH7679 | Spring Airlines | 3 | 2026-05-17 |
| CQH7355 | Spring Airlines | 3 | 2026-05-18 |
| CQH6524 | Spring Airlines | 3 | 2026-06-02 |
| CQH6293 | Spring Airlines | 3 | 2026-05-12 |
| CQH7135 | - | 2 | 2026-06-27 |
| CQH6731 | - | 2 | 2026-06-30 |
| CQH6596 | Spring Airlines | 2 | 2026-05-05 |
| CQH6540 | Spring Airlines | 2 | 2026-05-02 |
| CQH6294 | Spring Airlines | 2 | 2026-05-12 |
| CQH8952 | Spring Airlines | 1 | 2026-06-01 |
| CQH8951 | Spring Airlines | 1 | 2026-06-01 |
| CQH8933 | Spring Airlines | 1 | 2026-05-30 |
| CQH8875 | - | 1 | 2026-07-02 |
| CQH8779 | Spring Airlines | 1 | 2026-07-20 |
| CQH8753 | Spring Airlines | 1 | 2026-05-19 |
| CQH8688 | - | 1 | 2026-05-09 |
| CQH8687 | - | 1 | 2026-05-06 |
| CQH8684 | Spring Airlines | 1 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CQH7432 | DMK → NGB | Jul 25, 07:30 UTC | Jul 25, 10:55 UTC | 3h 25m |
| 2026-07-25 | CQH7431 | NGB → BKK | Jul 25, 03:10 UTC | Jul 25, 05:40 UTC | 2h 30m |
| 2026-07-24 | CQH7520 | SZX → SHA | Jul 24, 05:25 UTC | Jul 24, 05:35 UTC | 10m |
| 2026-07-24 | CQH7519 | SHA → SZX | Jul 24, 03:15 UTC | Jul 24, 03:50 UTC | 35m |
| 2026-07-22 | CQH7368 | - | Jul 22, 23:15 UTC | Jul 22, 23:35 UTC | 20m |
| 2026-07-20 | CQH8779 | SHA → SYX | Jul 20, 00:10 UTC | Jul 20, 01:25 UTC | 1h 15m |
| 2026-07-12 | CQH6411 | - | Jul 12, 09:55 UTC | Jul 12, 10:15 UTC | 20m |
| 2026-07-10 | CQH6411 | - | Jul 10, 10:15 UTC | Jul 10, 10:25 UTC | 10m |
| 2026-07-02 | CQH8522 | - | Jul 2, 03:45 UTC | Jul 2, 20:25 UTC | 16h 40m |
| 2026-07-02 | CQH8875 | - | Jul 2, 01:50 UTC | Jul 2, 02:10 UTC | 20m |
| 2026-07-01 | CQH8521 | PVG → HKT | Jul 1, 12:20 UTC | Jul 2, 01:10 UTC | 12h 50m |
| 2026-06-30 | CQH6732 | - | Jun 30, 12:10 UTC | Jun 30, 12:35 UTC | 25m |
| 2026-06-30 | CQH6731 | - | Jun 30, 06:10 UTC | Jun 30, 09:50 UTC | 3h 40m |
| 2026-06-29 | CQH6731 | - | Jun 29, 10:15 UTC | Jun 30, 09:50 UTC | 23h 36m |
| 2026-06-28 | CQH7133 | LHW → TSN | Jun 28, 09:50 UTC | Jun 28, 10:15 UTC | 25m |
| 2026-06-27 | CQH7135 | - | Jun 27, 01:00 UTC | Jun 27, 01:24 UTC | 25m |
| 2026-06-12 | CQH6482 | - | Jun 12, 18:05 UTC | Jun 12, 18:15 UTC | 10m |
| 2026-06-12 | CQH6156 | ZUH → SJW | Jun 12, 05:05 UTC | Jun 12, 10:55 UTC | 5h 50m |
| 2026-06-06 | CQH7135 | LHW → TSN | Jun 6, 00:45 UTC | Jun 6, 01:10 UTC | 25m |
| 2026-06-02 | CQH6524 | KUL → PVG | Jun 2, 10:55 UTC | Jun 2, 15:00 UTC | 4h 5m |
| 2026-06-02 | CQH6523 | PVG → KUL | Jun 2, 05:05 UTC | Jun 2, 09:15 UTC | 4h 10m |
| 2026-06-01 | CQH8952 | TPE → PVG | Jun 1, 03:35 UTC | Jun 1, 03:50 UTC | 15m |
| 2026-06-01 | CQH8951 | PVG → TPE | Jun 1, 01:15 UTC | Jun 1, 01:35 UTC | 20m |
| 2026-05-31 | CQH6218 | NRT → PVG | May 31, 11:25 UTC | May 31, 12:55 UTC | 1h 30m |
| 2026-05-31 | CQH6217 | PVG → NRT | May 31, 08:25 UTC | May 31, 09:30 UTC | 1h 5m |
| 2026-05-30 | CQH8933 | CAN → CNX | May 30, 22:50 UTC | May 31, 00:30 UTC | 1h 40m |
| 2026-05-25 | CQH6809 | SHE → KWL | May 25, 23:45 UTC | May 26, 00:09 UTC | 25m |
| 2026-05-24 | CQH8684 | HRB → NGB | May 24, 06:15 UTC | May 24, 06:25 UTC | 10m |
| 2026-05-19 | CQH8753 | SZX → XIY | May 19, 22:50 UTC | May 19, 23:00 UTC | 10m |
| 2026-05-18 | CQH7355 | SZX → LHW | May 18, 23:15 UTC | May 18, 23:25 UTC | 10m |
| 2026-05-17 | CQH7679 | SZX → LHW | May 17, 23:20 UTC | May 17, 23:30 UTC | 10m |
| 2026-05-16 | CQH7355 | SZX → LHW | May 16, 22:40 UTC | May 16, 22:50 UTC | 10m |
| 2026-05-16 | CQH6727 | SZX → NNY | May 16, 13:46 UTC | May 16, 14:01 UTC | 15m |
| 2026-05-15 | CQH6524 | KUL → PVG | May 15, 14:25 UTC | May 16, 01:00 UTC | 10h 34m |
| 2026-05-15 | CQH6524 | KUL → PVG | May 15, 11:00 UTC | May 15, 11:15 UTC | 15m |
| 2026-05-14 | CQH6523 | PVG → KUL | May 14, 15:20 UTC | May 15, 09:25 UTC | 18h 5m |
| 2026-05-14 | CQH6523 | PVG → KUL | May 14, 12:05 UTC | May 15, 09:25 UTC | 21h 20m |
| 2026-05-14 | CQH6523 | PVG → KUL | May 14, 03:00 UTC | May 14, 10:45 UTC | 7h 45m |
| 2026-05-12 | CQH6294 | BKK → XIY | May 12, 20:05 UTC | May 12, 21:01 UTC | 55m |
| 2026-05-12 | CQH6293 | XIY → BKK | May 12, 17:10 UTC | May 12, 18:05 UTC | 55m |
| 2026-05-11 | CQH6293 | XIY → BKK | May 11, 20:05 UTC | May 12, 18:05 UTC | 22h 0m |
| 2026-05-11 | CQH6294 | BKK → XIY | May 11, 19:55 UTC | May 12, 18:00 UTC | 22h 5m |
| 2026-05-11 | CQH6293 | XIY → BKK | May 11, 16:40 UTC | May 11, 17:30 UTC | 51m |
| 2026-05-09 | CQH6481 | SZX → DOY | May 9, 22:34 UTC | May 9, 22:45 UTC | 10m |
| 2026-05-09 | CQH8688 | - | May 9, 17:35 UTC | May 9, 17:55 UTC | 20m |
| 2026-05-07 | CQH7020 | - | May 7, 02:45 UTC | May 7, 14:20 UTC | 11h 35m |
| 2026-05-06 | CQH8687 | - | May 6, 21:55 UTC | May 6, 22:05 UTC | 10m |
| 2026-05-05 | CQH7679 | SZX → LHW | May 5, 22:40 UTC | May 5, 22:55 UTC | 15m |
| 2026-05-05 | CQH6596 | TNA → SZX | May 5, 15:40 UTC | May 5, 15:50 UTC | 10m |
| 2026-05-03 | CQH7679 | SZX → LHW | May 3, 23:15 UTC | May 3, 23:25 UTC | 10m |
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-32FM page for operator, model, and routing details .