sensors Mode-S transponder
780CE0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1892 · AIRBUS A-320
- Hex
- 780CE0
- Octal
- 36006340
- Decimal
- 7,867,616
- Country
- CN
- Tail
- B-1892
- Type
- A320
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 780CE0 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 |
|---|---|---|---|
| CQH6900 | - | 3 | 2026-07-14 |
| CQH7420 | - | 2 | 2026-06-30 |
| CQH7285 | - | 2 | 2026-06-30 |
| CQH7206 | Spring Airlines | 2 | 2026-04-23 |
| CQH6540 | - | 2 | 2026-07-04 |
| CQH6539 | - | 2 | 2026-07-04 |
| CQH6300 | - | 2 | 2026-04-14 |
| CQH6299 | Spring Airlines | 2 | 2026-04-14 |
| CQH8860 | - | 1 | 2026-07-05 |
| CQH8755 | Spring Airlines | 1 | 2026-04-18 |
| CQH8716 | - | 1 | 2026-07-14 |
| CQH8715 | - | 1 | 2026-07-14 |
| CQH8671 | - | 1 | 2026-07-04 |
| CQH7596 | Spring Airlines | 1 | 2026-05-25 |
| CQH7595 | Spring Airlines | 1 | 2026-05-25 |
| CQH7558 | Spring Airlines | 1 | 2026-04-30 |
| CQH7520 | Spring Airlines | 1 | 2026-05-08 |
| CQH7518 | Spring Airlines | 1 | 2026-04-23 |
| CQH7502 | Spring Airlines | 1 | 2026-05-23 |
| CQH7501 | Spring Airlines | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CQH6900 | - | Jul 14, 13:20 UTC | Jul 14, 13:40 UTC | 20m |
| 2026-07-14 | CQH6899 | - | Jul 14, 11:45 UTC | Jul 14, 12:10 UTC | 25m |
| 2026-07-14 | CQH8716 | - | Jul 14, 05:45 UTC | Jul 14, 06:40 UTC | 55m |
| 2026-07-14 | CQH8715 | - | Jul 14, 02:20 UTC | Jul 14, 03:40 UTC | 1h 20m |
| 2026-07-10 | CQH6600 | - | Jul 10, 10:25 UTC | Jul 10, 14:25 UTC | 4h 0m |
| 2026-07-09 | CQH6628 | - | Jul 9, 14:50 UTC | Jul 10, 10:35 UTC | 19h 45m |
| 2026-07-09 | CQH6627 | - | Jul 9, 12:10 UTC | Jul 9, 13:00 UTC | 50m |
| 2026-07-06 | CQH6610 | - | Jul 6, 03:05 UTC | Jul 6, 03:35 UTC | 30m |
| 2026-07-06 | CQH6609 | PVG → FUK | Jul 6, 01:00 UTC | Jul 6, 01:20 UTC | 20m |
| 2026-07-05 | CQH6900 | - | Jul 5, 13:30 UTC | Jul 5, 13:55 UTC | 25m |
| 2026-07-05 | CQH6900 | - | Jul 5, 11:55 UTC | Jul 5, 12:15 UTC | 20m |
| 2026-07-05 | CQH8860 | - | Jul 5, 07:35 UTC | Jul 5, 08:20 UTC | 45m |
| 2026-07-04 | CQH8671 | - | Jul 4, 23:00 UTC | Jul 4, 23:10 UTC | 10m |
| 2026-07-04 | CQH6540 | - | Jul 4, 18:55 UTC | Jul 4, 19:15 UTC | 20m |
| 2026-07-04 | CQH6540 | - | Jul 4, 12:30 UTC | Jul 4, 12:45 UTC | 15m |
| 2026-07-04 | CQH6539 | - | Jul 4, 09:45 UTC | Jul 4, 10:00 UTC | 15m |
| 2026-07-04 | CQH6539 | - | Jul 4, 05:25 UTC | Jul 4, 05:35 UTC | 10m |
| 2026-07-03 | CQH6874 | - | Jul 3, 22:35 UTC | Jul 3, 22:50 UTC | 15m |
| 2026-07-01 | CQH7286 | - | Jul 1, 01:55 UTC | Jul 1, 13:10 UTC | 11h 15m |
| 2026-06-30 | CQH7419 | - | Jun 30, 22:30 UTC | Jul 1, 00:45 UTC | 2h 15m |
| 2026-06-30 | CQH7420 | - | Jun 30, 14:50 UTC | Jun 30, 16:30 UTC | 1h 40m |
| 2026-06-30 | CQH7285 | - | Jun 30, 10:55 UTC | Jun 30, 13:10 UTC | 2h 15m |
| 2026-06-27 | CQH7415 | - | Jun 27, 09:50 UTC | Jun 27, 12:29 UTC | 2h 40m |
| 2026-06-26 | CQH6888 | TYN → SHE | Jun 26, 14:35 UTC | Jun 27, 12:29 UTC | 21h 55m |
| 2026-06-26 | CQH6887 | SHE → TYN | Jun 26, 12:00 UTC | Jun 26, 12:14 UTC | 15m |
| 2026-06-23 | CQH6150 | - | Jun 23, 22:49 UTC | Jun 23, 23:00 UTC | 10m |
| 2026-05-25 | - | - | May 25, 13:10 UTC | May 25, 13:20 UTC | 10m |
| 2026-05-25 | CQH7596 | ZUH → YTY | May 25, 06:05 UTC | May 25, 06:20 UTC | 15m |
| 2026-05-25 | CQH7595 | YTY → ZUH | May 25, 04:10 UTC | May 25, 04:30 UTC | 20m |
| 2026-05-23 | CQH7502 | BKK → TFU | May 23, 04:25 UTC | May 23, 10:20 UTC | 5h 55m |
| 2026-05-23 | CQH7501 | TFU → BKK | May 23, 01:40 UTC | May 23, 02:45 UTC | 1h 4m |
| 2026-05-08 | CQH7520 | SZX → SHA | May 8, 05:39 UTC | May 8, 05:59 UTC | 20m |
| 2026-05-02 | CQH7432 | DMK → NGB | May 2, 07:20 UTC | May 2, 10:20 UTC | 3h 0m |
| 2026-05-02 | CQH7431 | NGB → BKK | May 2, 02:40 UTC | May 2, 06:00 UTC | 3h 20m |
| 2026-04-30 | CQH7558 | SGN → PVG | Apr 30, 08:35 UTC | Apr 30, 14:50 UTC | 6h 15m |
| 2026-04-28 | CQH7302 | BKK → FOC | Apr 28, 09:15 UTC | Apr 28, 11:30 UTC | 2h 15m |
| 2026-04-27 | CQH7301 | FOC → BKK | Apr 27, 13:15 UTC | Apr 28, 07:55 UTC | 18h 40m |
| 2026-04-27 | CQH6731 | - | Apr 27, 11:10 UTC | Apr 27, 11:25 UTC | 15m |
| 2026-04-25 | CQH6595 | SZX → TNA | Apr 25, 22:50 UTC | Apr 25, 23:00 UTC | 10m |
| 2026-04-25 | CQH6728 | NNY → SZX | Apr 25, 15:00 UTC | Apr 25, 15:15 UTC | 15m |
| 2026-04-25 | CQH6727 | SZX → NNY | Apr 25, 10:30 UTC | Apr 25, 10:45 UTC | 15m |
| 2026-04-23 | CQH7206 | CJU → PKX | Apr 23, 14:05 UTC | Apr 24, 13:45 UTC | 23h 39m |
| 2026-04-23 | CQH7206 | CJU → PKX | Apr 23, 13:30 UTC | Apr 23, 14:05 UTC | 35m |
| 2026-04-23 | CQH7205 | PKX → CJU | Apr 23, 11:25 UTC | Apr 23, 11:45 UTC | 20m |
| 2026-04-23 | CQH7518 | LHW → PKX | Apr 23, 07:20 UTC | Apr 23, 07:35 UTC | 15m |
| 2026-04-22 | CQH6156 | ZUH → SJW | Apr 22, 06:01 UTC | Apr 22, 06:25 UTC | 25m |
| 2026-04-22 | CQH6155 | SJW → ZUH | Apr 22, 03:50 UTC | Apr 22, 04:05 UTC | 15m |
| 2026-04-19 | CQH7420 | BKK → CAN | Apr 19, 14:40 UTC | Apr 19, 15:25 UTC | 45m |
| 2026-04-18 | CQH7285 | - | Apr 18, 20:00 UTC | Apr 19, 13:20 UTC | 17h 20m |
| 2026-04-18 | CQH8755 | PVG → BKK | Apr 18, 15:45 UTC | Apr 18, 18:05 UTC | 2h 20m |
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-1892 page for operator, model, and routing details .