sensors Mode-S transponder
780928
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6932 · AIRBUS A-320
- Hex
- 780928
- Octal
- 36004450
- Decimal
- 7,866,664
- Country
- CN
- Tail
- B-6932
- Type
- A320
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address 780928 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 |
|---|---|---|---|
| CQH7420 | - | 4 | 2026-06-18 |
| CQH7285 | - | 4 | 2026-06-18 |
| CQH7135 | - | 3 | 2026-07-14 |
| CQH6826 | - | 3 | 2026-07-02 |
| CQH6825 | - | 3 | 2026-07-02 |
| CQH8936 | - | 2 | 2026-07-06 |
| CQH8756 | Spring Airlines | 2 | 2026-05-31 |
| CQH8755 | Spring Airlines | 2 | 2026-05-31 |
| CQH8715 | - | 2 | 2026-06-18 |
| CQH7496 | Spring Airlines | 2 | 2026-06-13 |
| CQH7432 | - | 2 | 2026-04-13 |
| CQH7431 | Spring Airlines | 2 | 2026-04-13 |
| CQH7049 | Spring Airlines | 2 | 2026-05-29 |
| CQH8933 | Spring Airlines | 1 | 2026-05-25 |
| CQH8876 | Spring Airlines | 1 | 2026-05-28 |
| CQH8875 | Spring Airlines | 1 | 2026-05-28 |
| CQH8837 | - | 1 | 2026-05-10 |
| CQH8785 | - | 1 | 2026-05-05 |
| CQH8762 | - | 1 | 2026-06-26 |
| CQH8761 | - | 1 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CQH7135 | - | Jul 14, 01:50 UTC | Jul 14, 02:15 UTC | 25m |
| 2026-07-13 | CQH6838 | - | Jul 13, 04:10 UTC | Jul 13, 04:25 UTC | 15m |
| 2026-07-10 | - | - | Jul 10, 13:45 UTC | Jul 10, 13:55 UTC | 10m |
| 2026-07-06 | CQH8936 | - | Jul 6, 04:05 UTC | Jul 6, 15:10 UTC | 11h 5m |
| 2026-07-02 | CQH6826 | - | Jul 2, 12:10 UTC | Jul 2, 14:35 UTC | 2h 25m |
| 2026-07-02 | CQH6825 | - | Jul 2, 08:10 UTC | Jul 2, 10:40 UTC | 2h 30m |
| 2026-06-30 | CQH6873 | - | Jun 30, 06:25 UTC | Jun 30, 06:40 UTC | 15m |
| 2026-06-29 | CQH8753 | - | Jun 29, 22:39 UTC | Jun 29, 22:49 UTC | 10m |
| 2026-06-29 | CQH6728 | - | Jun 29, 15:45 UTC | Jun 29, 15:54 UTC | 10m |
| 2026-06-29 | CQH6727 | - | Jun 29, 10:59 UTC | Jun 29, 11:10 UTC | 10m |
| 2026-06-29 | CQH8672 | - | Jun 29, 09:14 UTC | Jun 29, 09:40 UTC | 25m |
| 2026-06-26 | CQH6370 | - | Jun 26, 14:29 UTC | Jun 26, 14:39 UTC | 10m |
| 2026-06-26 | CQH8762 | - | Jun 26, 08:34 UTC | Jun 26, 08:50 UTC | 15m |
| 2026-06-26 | CQH8761 | - | Jun 26, 04:20 UTC | Jun 26, 04:34 UTC | 15m |
| 2026-06-24 | CQH8611 | - | Jun 24, 09:24 UTC | Jun 24, 09:45 UTC | 20m |
| 2026-06-21 | CQH7135 | - | Jun 21, 04:10 UTC | Jun 21, 04:30 UTC | 20m |
| 2026-06-18 | CQH7420 | - | Jun 18, 16:30 UTC | Jun 18, 18:05 UTC | 1h 35m |
| 2026-06-18 | CQH7285 | HKG → BKK | Jun 18, 06:35 UTC | Jun 18, 15:05 UTC | 8h 30m |
| 2026-06-18 | CQH8715 | - | Jun 18, 03:40 UTC | Jun 18, 04:15 UTC | 35m |
| 2026-06-18 | CQH8715 | - | Jun 18, 02:30 UTC | Jun 18, 03:05 UTC | 35m |
| 2026-06-13 | CQH7496 | SIN → CAN | Jun 13, 17:15 UTC | Jun 13, 17:45 UTC | 30m |
| 2026-06-13 | CQH7496 | SIN → CAN | Jun 13, 14:00 UTC | Jun 13, 14:30 UTC | 30m |
| 2026-06-13 | CQH7495 | CAN → SIN | Jun 13, 09:05 UTC | Jun 13, 12:05 UTC | 3h 0m |
| 2026-06-12 | CQH7008 | PNH → CAN | Jun 12, 16:10 UTC | Jun 12, 16:30 UTC | 20m |
| 2026-06-12 | CQH7286 | - | Jun 12, 01:50 UTC | Jun 12, 10:25 UTC | 8h 35m |
| 2026-06-11 | CQH7419 | CAN → BKK | Jun 11, 22:15 UTC | Jun 12, 00:30 UTC | 2h 15m |
| 2026-06-11 | CQH7420 | BKK → CAN | Jun 11, 14:40 UTC | Jun 11, 16:15 UTC | 1h 35m |
| 2026-06-11 | CQH7285 | - | Jun 11, 03:45 UTC | Jun 11, 13:20 UTC | 9h 35m |
| 2026-06-10 | CQH7282 | BKK → PVG | Jun 10, 10:40 UTC | Jun 11, 02:10 UTC | 15h 30m |
| 2026-06-10 | CQH7281 | PVG → BKK | Jun 10, 06:55 UTC | Jun 10, 09:10 UTC | 2h 15m |
| 2026-06-08 | CQH7135 | LHW → TSN | Jun 8, 04:10 UTC | Jun 8, 04:35 UTC | 25m |
| 2026-06-07 | - | - | Jun 7, 02:45 UTC | Jun 7, 02:55 UTC | 10m |
| 2026-06-06 | CQH7205 | PKX → CJU | Jun 6, 11:14 UTC | Jun 6, 14:04 UTC | 2h 50m |
| 2026-06-06 | CQH7518 | LHW → PKX | Jun 6, 07:20 UTC | Jun 6, 07:35 UTC | 15m |
| 2026-05-31 | CQH8756 | BKK → PVG | May 31, 19:50 UTC | May 31, 22:00 UTC | 2h 10m |
| 2026-05-31 | CQH8755 | PVG → BKK | May 31, 10:20 UTC | May 31, 18:15 UTC | 7h 55m |
| 2026-05-29 | CQH7050 | CJJ → PVG | May 29, 03:20 UTC | May 29, 03:35 UTC | 15m |
| 2026-05-29 | CQH7049 | PVG → CJJ | May 29, 01:45 UTC | May 29, 02:05 UTC | 20m |
| 2026-05-28 | CQH8876 | MFM → PVG | May 28, 03:35 UTC | May 28, 04:50 UTC | 1h 15m |
| 2026-05-28 | CQH8875 | PVG → MFM | May 28, 00:55 UTC | May 28, 02:15 UTC | 1h 20m |
| 2026-05-26 | CQH8756 | BKK → PVG | May 26, 20:00 UTC | May 26, 22:15 UTC | 2h 15m |
| 2026-05-26 | CQH8755 | PVG → BKK | May 26, 11:00 UTC | May 26, 17:55 UTC | 6h 55m |
| 2026-05-26 | CQH8559 | PVG → ICN | May 26, 01:44 UTC | May 26, 09:25 UTC | 7h 40m |
| 2026-05-25 | CQH8933 | CAN → CNX | May 25, 22:25 UTC | May 26, 00:35 UTC | 2h 10m |
| 2026-05-25 | CQH7420 | BKK → CAN | May 25, 15:15 UTC | May 25, 15:55 UTC | 40m |
| 2026-05-25 | CQH7285 | - | May 25, 01:55 UTC | May 25, 13:00 UTC | 11h 5m |
| 2026-05-24 | CQH7420 | BKK → CAN | May 24, 14:45 UTC | May 24, 15:25 UTC | 40m |
| 2026-05-24 | CQH7285 | - | May 24, 03:45 UTC | May 24, 13:10 UTC | 9h 25m |
| 2026-05-23 | CQH6218 | NRT → PVG | May 23, 11:15 UTC | May 24, 02:20 UTC | 15h 5m |
| 2026-05-23 | CQH6217 | PVG → NRT | May 23, 03:15 UTC | May 23, 09:30 UTC | 6h 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-6932 page for operator, model, and routing details .