sensors Mode-S transponder
781856
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30D5 · AIRBUS A-320neo
- Hex
- 781856
- Octal
- 36014126
- Decimal
- 7,870,550
- Country
- CN
- Tail
- B-30D5
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 781856 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 |
|---|---|---|---|
| CQH8598 | Spring Airlines | 3 | 2026-05-31 |
| CQH6293 | Spring Airlines | 3 | 2026-06-09 |
| CQH8715 | Spring Airlines | 2 | 2026-05-05 |
| CQH8515 | Spring Airlines | 2 | 2026-05-03 |
| CQH6922 | Spring Airlines | 2 | 2026-04-27 |
| CQH6921 | Spring Airlines | 2 | 2026-04-27 |
| CQH8934 | Spring Airlines | 1 | 2026-04-24 |
| CQH8875 | Spring Airlines | 1 | 2026-04-24 |
| CQH8832 | Spring Airlines | 1 | 2026-06-10 |
| CQH8782 | Spring Airlines | 1 | 2026-05-01 |
| CQH8779 | Spring Airlines | 1 | 2026-05-18 |
| CQH8716 | Spring Airlines | 1 | 2026-05-05 |
| CQH8665 | Spring Airlines | 1 | 2026-04-29 |
| CQH861Q | - | 1 | 2026-05-01 |
| CQH8597 | Spring Airlines | 1 | 2026-05-26 |
| CQH8522 | Spring Airlines | 1 | 2026-05-22 |
| CQH8516 | Spring Airlines | 1 | 2026-05-03 |
| CQH8511 | Spring Airlines | 1 | 2026-04-24 |
| CQH7420 | Spring Airlines | 1 | 2026-05-18 |
| CQH7419 | Spring Airlines | 1 | 2026-04-27 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | CQH8832 | XIY → SHE | Jun 10, 23:55 UTC | Jun 11, 03:05 UTC | 3h 10m |
| 2026-06-09 | CQH6294 | BKK → XIY | Jun 9, 20:35 UTC | Jun 9, 21:00 UTC | 25m |
| 2026-06-09 | CQH6293 | XIY → BKK | Jun 9, 17:05 UTC | Jun 9, 17:55 UTC | 50m |
| 2026-06-08 | CQH6293 | XIY → BKK | Jun 8, 20:00 UTC | Jun 9, 17:55 UTC | 21h 55m |
| 2026-06-08 | CQH6293 | XIY → BKK | Jun 8, 16:40 UTC | Jun 8, 17:10 UTC | 30m |
| 2026-06-07 | CQH6887 | SHE → TYN | Jun 7, 12:00 UTC | Jun 7, 12:15 UTC | 15m |
| 2026-06-06 | CQH6334 | TGO → PVG | Jun 6, 05:10 UTC | Jun 6, 05:25 UTC | 15m |
| 2026-05-31 | CQH8598 | HKG → PVG | May 31, 12:30 UTC | Jun 1, 10:00 UTC | 21h 30m |
| 2026-05-31 | CQH8598 | HKG → PVG | May 31, 09:30 UTC | May 31, 12:45 UTC | 3h 15m |
| 2026-05-27 | CQH8598 | HKG → PVG | May 27, 08:40 UTC | May 27, 12:50 UTC | 4h 10m |
| 2026-05-26 | CQH8597 | PVG → HKG | May 26, 12:54 UTC | May 27, 06:29 UTC | 17h 35m |
| 2026-05-26 | CQH7049 | PVG → CJJ | May 26, 11:09 UTC | May 26, 11:39 UTC | 30m |
| 2026-05-22 | CQH8522 | HKT → PVG | May 22, 12:20 UTC | May 23, 04:50 UTC | 16h 29m |
| 2026-05-18 | CQH7420 | BKK → CAN | May 18, 15:10 UTC | May 18, 15:40 UTC | 30m |
| 2026-05-18 | CQH8779 | SHA → SYX | May 18, 00:20 UTC | May 18, 13:05 UTC | 12h 45m |
| 2026-05-10 | CQH7259 | PVG → PEN | May 10, 01:50 UTC | May 10, 11:45 UTC | 9h 55m |
| 2026-05-06 | CQH7091 | SJW → ZQZ | May 6, 10:01 UTC | May 6, 10:10 UTC | 10m |
| 2026-05-05 | CQH8716 | HKG → PVG | May 5, 05:55 UTC | May 5, 06:55 UTC | 1h 0m |
| 2026-05-05 | CQH8715 | PVG → HKG | May 5, 04:00 UTC | May 5, 04:25 UTC | 25m |
| 2026-05-05 | CQH8715 | PVG → HKG | May 5, 02:50 UTC | May 5, 03:25 UTC | 35m |
| 2026-05-03 | CQH8516 | HND → PVG | May 3, 16:05 UTC | May 3, 17:40 UTC | 1h 35m |
| 2026-05-03 | CQH8515 | PVG → HND | May 3, 12:15 UTC | May 3, 13:40 UTC | 1h 25m |
| 2026-05-02 | CQH8515 | PVG → HND | May 2, 13:35 UTC | May 3, 13:30 UTC | 23h 55m |
| 2026-05-02 | CQH6900 | PUS → PVG | May 2, 07:15 UTC | May 2, 13:40 UTC | 6h 25m |
| 2026-05-01 | CQH8782 | HKT → SZX | May 1, 19:05 UTC | May 1, 19:20 UTC | 15m |
| 2026-05-01 | CQH861Q | - | May 1, 13:30 UTC | May 1, 17:30 UTC | 4h 0m |
| 2026-04-29 | CQH8665 | PVG → HKT | Apr 29, 10:30 UTC | Apr 29, 16:05 UTC | 5h 35m |
| 2026-04-28 | CQH7286 | BKK → PVG | Apr 28, 01:55 UTC | Apr 28, 04:10 UTC | 2h 15m |
| 2026-04-27 | CQH7419 | CAN → BKK | Apr 27, 22:10 UTC | Apr 28, 00:40 UTC | 2h 30m |
| 2026-04-27 | CQH7348 | SGN → CAN | Apr 27, 13:55 UTC | Apr 27, 14:10 UTC | 15m |
| 2026-04-27 | CQH6922 | KUL → CAN | Apr 27, 06:05 UTC | Apr 27, 06:20 UTC | 15m |
| 2026-04-27 | CQH6922 | KUL → CAN | Apr 27, 02:55 UTC | Apr 27, 03:15 UTC | 20m |
| 2026-04-27 | CQH6921 | CAN → KUL | Apr 27, 01:05 UTC | Apr 27, 01:25 UTC | 20m |
| 2026-04-26 | CQH6921 | CAN → KUL | Apr 26, 21:55 UTC | Apr 26, 22:10 UTC | 15m |
| 2026-04-24 | CQH8934 | CNX → CAN | Apr 24, 14:50 UTC | Apr 24, 15:20 UTC | 30m |
| 2026-04-24 | CQH8511 | PVG → CNX | Apr 24, 03:50 UTC | Apr 24, 13:50 UTC | 10h 0m |
| 2026-04-24 | CQH8875 | PVG → MFM | Apr 24, 00:55 UTC | Apr 24, 02:25 UTC | 1h 30m |
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-30D5 page for operator, model, and routing details .