sensors Mode-S transponder
781D3F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-328H · AIRBUS A-320neo
- Hex
- 781D3F
- Octal
- 36016477
- Decimal
- 7,871,807
- Country
- CN
- Tail
- B-328H
- Type
- A20N
- Flights observed
- 97
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 781D3F 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 |
|---|---|---|---|
| CQH6523 | Spring Airlines | 8 | 2026-05-20 |
| CQH8666 | - | 5 | 2026-07-09 |
| CQH8597 | Spring Airlines | 4 | 2026-04-27 |
| CQH8521 | - | 4 | 2026-07-12 |
| CQH7496 | Spring Airlines | 4 | 2026-06-04 |
| CQH6524 | Spring Airlines | 4 | 2026-05-20 |
| CQH6515 | - | 4 | 2026-07-07 |
| CQH6293 | - | 4 | 2026-06-26 |
| CQH8952 | - | 3 | 2026-07-02 |
| CQH8875 | Spring Airlines | 3 | 2026-06-02 |
| CQH8663 | - | 3 | 2026-07-01 |
| CQH6516 | - | 3 | 2026-07-07 |
| CQH8951 | Spring Airlines | 2 | 2026-05-17 |
| CQH8920 | Spring Airlines | 2 | 2026-05-07 |
| CQH8715 | Spring Airlines | 2 | 2026-05-30 |
| CQH8598 | Spring Airlines | 2 | 2026-04-27 |
| CQH8550 | Spring Airlines | 2 | 2026-05-16 |
| CQH8549 | Spring Airlines | 2 | 2026-05-16 |
| CQH7495 | Spring Airlines | 2 | 2026-06-04 |
| CQH7420 | Spring Airlines | 2 | 2026-06-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CQH6900 | - | Jul 13, 13:25 UTC | Jul 14, 06:55 UTC | 17h 30m |
| 2026-07-13 | CQH6899 | - | Jul 13, 11:35 UTC | Jul 13, 11:55 UTC | 20m |
| 2026-07-12 | CQH8521 | - | Jul 12, 12:40 UTC | Jul 13, 06:35 UTC | 17h 55m |
| 2026-07-09 | CQH8666 | - | Jul 9, 20:05 UTC | Jul 10, 12:55 UTC | 16h 50m |
| 2026-07-09 | CQH8593 | - | Jul 9, 03:20 UTC | Jul 9, 18:50 UTC | 15h 30m |
| 2026-07-07 | CQH6516 | - | Jul 7, 15:55 UTC | Jul 7, 20:20 UTC | 4h 25m |
| 2026-07-07 | CQH6515 | - | Jul 7, 09:50 UTC | Jul 7, 13:55 UTC | 4h 5m |
| 2026-07-02 | CQH8952 | - | Jul 2, 03:35 UTC | Jul 2, 04:05 UTC | 30m |
| 2026-07-01 | CQH8663 | - | Jul 1, 07:50 UTC | Jul 2, 02:20 UTC | 18h 30m |
| 2026-07-01 | CQH8663 | - | Jul 1, 06:55 UTC | Jul 2, 02:20 UTC | 19h 25m |
| 2026-06-30 | CQH8663 | - | Jun 30, 14:30 UTC | Jul 1, 13:40 UTC | 23h 10m |
| 2026-06-30 | CQH7049 | - | Jun 30, 03:35 UTC | Jun 30, 13:25 UTC | 9h 50m |
| 2026-06-29 | CQH7057 | - | Jun 29, 11:50 UTC | Jun 30, 08:25 UTC | 20h 36m |
| 2026-06-29 | CQH8666 | - | Jun 29, 09:50 UTC | Jun 30, 08:25 UTC | 22h 36m |
| 2026-06-29 | CQH8666 | - | Jun 29, 09:14 UTC | Jun 30, 03:55 UTC | 18h 41m |
| 2026-06-29 | CQH8666 | - | Jun 29, 05:50 UTC | Jun 30, 03:55 UTC | 22h 6m |
| 2026-06-29 | CQH8666 | - | Jun 29, 03:49 UTC | Jun 30, 03:45 UTC | 23h 56m |
| 2026-06-26 | CQH6294 | - | Jun 26, 19:55 UTC | Jun 26, 20:24 UTC | 30m |
| 2026-06-26 | CQH6293 | - | Jun 26, 16:24 UTC | Jun 26, 17:19 UTC | 55m |
| 2026-06-06 | CQH6538 | FUK → PVG | Jun 6, 09:00 UTC | Jun 6, 09:09 UTC | 10m |
| 2026-06-06 | CQH8806 | - | Jun 6, 03:20 UTC | Jun 6, 03:55 UTC | 35m |
| 2026-06-05 | CQH7286 | BKK → PVG | Jun 5, 01:50 UTC | Jun 5, 13:10 UTC | 11h 20m |
| 2026-06-04 | CQH7419 | CAN → BKK | Jun 4, 22:20 UTC | Jun 5, 00:35 UTC | 2h 15m |
| 2026-06-04 | CQH7496 | SIN → CAN | Jun 4, 16:30 UTC | Jun 4, 17:05 UTC | 35m |
| 2026-06-04 | CQH7496 | SIN → CAN | Jun 4, 13:25 UTC | Jun 4, 13:50 UTC | 25m |
| 2026-06-04 | CQH7495 | CAN → SIN | Jun 4, 11:35 UTC | Jun 4, 11:50 UTC | 15m |
| 2026-06-03 | CQH7348 | SGN → CAN | Jun 3, 13:55 UTC | Jun 3, 14:20 UTC | 25m |
| 2026-06-03 | CQH7347 | CAN → SGN | Jun 3, 08:40 UTC | Jun 3, 08:50 UTC | 10m |
| 2026-06-03 | CQH6922 | KUL → CAN | Jun 3, 05:40 UTC | Jun 3, 06:00 UTC | 20m |
| 2026-06-03 | CQH6922 | KUL → CAN | Jun 3, 02:35 UTC | Jun 3, 02:55 UTC | 20m |
| 2026-06-03 | CQH6921 | CAN → KUL | Jun 3, 00:45 UTC | Jun 3, 01:10 UTC | 25m |
| 2026-06-02 | CQH7420 | BKK → CAN | Jun 2, 14:40 UTC | Jun 2, 16:20 UTC | 1h 40m |
| 2026-06-02 | CQH7285 | - | Jun 2, 03:40 UTC | Jun 2, 13:10 UTC | 9h 30m |
| 2026-06-02 | CQH8875 | PVG → MFM | Jun 2, 00:45 UTC | Jun 2, 02:00 UTC | 1h 15m |
| 2026-05-30 | CQH8716 | HKG → PVG | May 30, 05:35 UTC | May 30, 06:20 UTC | 45m |
| 2026-05-30 | CQH8715 | PVG → HKG | May 30, 03:40 UTC | May 30, 03:55 UTC | 15m |
| 2026-05-30 | CQH8715 | PVG → HKG | May 30, 02:35 UTC | May 30, 03:00 UTC | 25m |
| 2026-05-29 | CQH8512 | CNX → PVG | May 29, 01:45 UTC | May 29, 02:55 UTC | 1h 10m |
| 2026-05-28 | CQH8933 | CAN → CNX | May 28, 22:25 UTC | May 29, 00:25 UTC | 2h 0m |
| 2026-05-28 | CQH7496 | SIN → CAN | May 28, 17:10 UTC | May 28, 17:40 UTC | 30m |
| 2026-05-28 | CQH7496 | SIN → CAN | May 28, 14:05 UTC | May 28, 14:30 UTC | 25m |
| 2026-05-28 | CQH7495 | CAN → SIN | May 28, 08:55 UTC | May 28, 12:20 UTC | 3h 25m |
| 2026-05-26 | CQH7432 | DMK → NGB | May 26, 07:10 UTC | May 26, 10:34 UTC | 3h 25m |
| 2026-05-26 | CQH7431 | NGB → BKK | May 26, 02:39 UTC | May 26, 05:34 UTC | 2h 55m |
| 2026-05-24 | CQH7286 | BKK → PVG | May 24, 01:55 UTC | May 24, 12:40 UTC | 10h 45m |
| 2026-05-24 | CQH7419 | CAN → BKK | May 24, 00:00 UTC | May 24, 00:40 UTC | 40m |
| 2026-05-21 | CQH7420 | BKK → CAN | May 21, 15:10 UTC | May 21, 15:35 UTC | 25m |
| 2026-05-21 | CQH7285 | - | May 21, 03:45 UTC | May 21, 13:45 UTC | 10h 0m |
| 2026-05-21 | CQH8875 | PVG → MFM | May 21, 02:00 UTC | May 21, 02:20 UTC | 20m |
| 2026-05-20 | CQH8875 | PVG → MFM | May 20, 14:00 UTC | May 21, 01:30 UTC | 11h 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-328H page for operator, model, and routing details .