sensors Mode-S transponder
7819EF
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-320M · AIRBUS A-320neo
- Hex
- 7819EF
- Octal
- 36014757
- Decimal
- 7,870,959
- Country
- CN
- Tail
- B-320M
- Type
- A20N
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 7819EF 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 |
|---|---|---|---|
| CQH8551 | Spring Airlines | 3 | 2026-05-26 |
| CQH8516 | Spring Airlines | 3 | 2026-05-27 |
| CQH8598 | Spring Airlines | 2 | 2026-05-28 |
| CQH8593 | - | 2 | 2026-07-19 |
| CQH8515 | Spring Airlines | 2 | 2026-05-26 |
| CQH7501 | - | 2 | 2026-07-15 |
| CQH7496 | Spring Airlines | 2 | 2026-05-30 |
| CQH7495 | Spring Airlines | 2 | 2026-05-30 |
| CQH6880 | - | 2 | 2026-06-14 |
| CQH6879 | - | 2 | 2026-06-14 |
| CQH6636 | Spring Airlines | 2 | 2026-05-04 |
| CQH6341 | Spring Airlines | 2 | 2026-06-05 |
| CQH8952 | Spring Airlines | 1 | 2026-06-04 |
| CQH8951 | Spring Airlines | 1 | 2026-06-04 |
| CQH8933 | Spring Airlines | 1 | 2026-06-02 |
| CQH8891 | - | 1 | 2026-07-19 |
| CQH8779 | Spring Airlines | 1 | 2026-05-03 |
| CQH8688 | - | 1 | 2026-04-19 |
| CQH8687 | - | 1 | 2026-04-20 |
| CQH8684 | Spring Airlines | 1 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | CQH8594 | - | Jul 19, 20:55 UTC | Jul 20, 11:45 UTC | 14h 50m |
| 2026-07-19 | CQH8593 | - | Jul 19, 19:25 UTC | Jul 19, 19:40 UTC | 15m |
| 2026-07-19 | CQH8593 | - | Jul 19, 06:10 UTC | Jul 19, 17:35 UTC | 11h 25m |
| 2026-07-19 | CQH8891 | - | Jul 19, 04:20 UTC | Jul 19, 04:35 UTC | 15m |
| 2026-07-18 | CQH8684 | HRB → NGB | Jul 18, 08:25 UTC | Jul 19, 03:05 UTC | 18h 40m |
| 2026-07-17 | CQH6294 | - | Jul 17, 19:15 UTC | Jul 18, 09:05 UTC | 13h 51m |
| 2026-07-17 | CQH6293 | - | Jul 17, 16:00 UTC | Jul 17, 17:15 UTC | 1h 15m |
| 2026-07-16 | CQH7588 | - | Jul 16, 03:05 UTC | Jul 16, 03:55 UTC | 50m |
| 2026-07-15 | CQH7587 | - | Jul 15, 10:30 UTC | Jul 16, 00:50 UTC | 14h 20m |
| 2026-07-15 | CQH7502 | - | Jul 15, 04:15 UTC | Jul 16, 00:50 UTC | 20h 35m |
| 2026-07-15 | CQH7501 | - | Jul 15, 02:00 UTC | Jul 15, 02:20 UTC | 20m |
| 2026-07-14 | CQH7501 | - | Jul 14, 06:35 UTC | Jul 15, 01:05 UTC | 18h 29m |
| 2026-06-17 | CQH7636 | - | Jun 17, 02:35 UTC | Jun 17, 02:50 UTC | 15m |
| 2026-06-14 | CQH6880 | - | Jun 14, 15:30 UTC | Jun 14, 15:55 UTC | 25m |
| 2026-06-14 | CQH6879 | - | Jun 14, 12:50 UTC | Jun 14, 13:55 UTC | 1h 5m |
| 2026-06-07 | CQH6880 | BKK → TFU | Jun 7, 15:20 UTC | Jun 7, 16:15 UTC | 55m |
| 2026-06-07 | CQH6879 | TFU → BKK | Jun 7, 13:05 UTC | Jun 7, 14:05 UTC | 1h 0m |
| 2026-06-06 | CQH7508 | - | Jun 6, 07:35 UTC | Jun 6, 07:50 UTC | 15m |
| 2026-06-05 | CQH6341 | SHE → HFE | Jun 5, 03:50 UTC | Jun 5, 04:05 UTC | 15m |
| 2026-06-04 | CQH8952 | TPE → PVG | Jun 4, 03:40 UTC | Jun 4, 04:00 UTC | 20m |
| 2026-06-04 | CQH8951 | PVG → TPE | Jun 4, 01:20 UTC | Jun 4, 01:55 UTC | 35m |
| 2026-06-03 | CQH8512 | CNX → PVG | Jun 3, 01:45 UTC | Jun 3, 03:05 UTC | 1h 20m |
| 2026-06-02 | CQH8933 | CAN → CNX | Jun 2, 22:50 UTC | Jun 3, 00:35 UTC | 1h 45m |
| 2026-05-30 | CQH7496 | SIN → CAN | May 30, 16:35 UTC | May 30, 16:55 UTC | 20m |
| 2026-05-30 | CQH7496 | SIN → CAN | May 30, 13:20 UTC | May 30, 13:45 UTC | 25m |
| 2026-05-30 | CQH7495 | CAN → SIN | May 30, 11:35 UTC | May 30, 11:45 UTC | 10m |
| 2026-05-30 | CQH7495 | CAN → SIN | May 30, 08:45 UTC | May 30, 08:55 UTC | 10m |
| 2026-05-29 | CQH7420 | BKK → CAN | May 29, 14:45 UTC | May 29, 16:20 UTC | 1h 35m |
| 2026-05-29 | CQH7285 | - | May 29, 11:40 UTC | May 29, 13:25 UTC | 1h 45m |
| 2026-05-28 | CQH8598 | HKG → PVG | May 28, 12:15 UTC | May 29, 11:45 UTC | 23h 30m |
| 2026-05-28 | CQH8598 | HKG → PVG | May 28, 09:00 UTC | May 28, 13:05 UTC | 4h 5m |
| 2026-05-27 | CQH8516 | HND → PVG | May 27, 16:10 UTC | May 28, 03:50 UTC | 11h 40m |
| 2026-05-26 | CQH8515 | PVG → HND | May 26, 22:25 UTC | May 27, 13:50 UTC | 15h 25m |
| 2026-05-26 | CQH8551 | PVG → SIN | May 26, 20:34 UTC | May 26, 20:45 UTC | 10m |
| 2026-05-26 | CQH7057 | PVG → UBN | May 26, 01:55 UTC | May 26, 17:30 UTC | 15h 35m |
| 2026-05-25 | CQH8516 | HND → PVG | May 25, 17:50 UTC | May 26, 17:30 UTC | 23h 40m |
| 2026-05-25 | CQH8516 | HND → PVG | May 25, 17:30 UTC | May 26, 06:39 UTC | 13h 9m |
| 2026-05-25 | CQH8515 | PVG → HND | May 25, 14:50 UTC | May 25, 16:10 UTC | 1h 20m |
| 2026-05-19 | CQH8521 | PVG → HKT | May 19, 12:20 UTC | May 19, 18:05 UTC | 5h 45m |
| 2026-05-17 | CQH6760 | SHE → PVG | May 17, 10:25 UTC | May 17, 11:01 UTC | 35m |
| 2026-05-10 | CQH7596 | ZUH → YTY | May 10, 06:15 UTC | May 10, 06:25 UTC | 10m |
| 2026-05-08 | CQH6341 | SHE → HFE | May 8, 04:00 UTC | May 8, 04:09 UTC | 10m |
| 2026-05-04 | CQH6636 | KUL → PVG | May 4, 01:40 UTC | May 4, 02:25 UTC | 45m |
| 2026-05-03 | CQH6636 | KUL → PVG | May 3, 22:30 UTC | May 3, 22:49 UTC | 20m |
| 2026-05-03 | CQH6515 | PVG → KUL | May 3, 13:50 UTC | May 3, 14:15 UTC | 25m |
| 2026-05-03 | CQH8779 | SHA → SYX | May 3, 00:20 UTC | May 3, 11:00 UTC | 10h 39m |
| 2026-04-30 | CQH7282 | BKK → PVG | Apr 30, 10:25 UTC | May 1, 04:50 UTC | 18h 25m |
| 2026-04-29 | CQH7281 | PVG → BKK | Apr 29, 22:25 UTC | Apr 30, 08:50 UTC | 10h 24m |
| 2026-04-29 | CQH8551 | PVG → SIN | Apr 29, 02:35 UTC | Apr 29, 20:55 UTC | 18h 21m |
| 2026-04-28 | CQH8551 | PVG → SIN | Apr 28, 23:50 UTC | Apr 29, 20:55 UTC | 21h 6m |
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-320M page for operator, model, and routing details .