sensors Mode-S transponder
781D67
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-328T · AIRBUS A-320neo
- Hex
- 781D67
- Octal
- 36016547
- Decimal
- 7,871,847
- Country
- CN
- Tail
- B-328T
- Type
- A20N
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781D67 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 |
|---|---|---|---|
| CQH6921 | Spring Airlines | 4 | 2026-05-29 |
| CQH6293 | - | 4 | 2026-07-13 |
| CQH7348 | Spring Airlines | 3 | 2026-05-29 |
| CQH6922 | Spring Airlines | 3 | 2026-05-29 |
| CQH6411 | - | 3 | 2026-07-17 |
| CQH6294 | - | 3 | 2026-07-13 |
| CQH8715 | Spring Airlines | 2 | 2026-04-23 |
| CQH7588 | Spring Airlines | 2 | 2026-07-01 |
| CQH7502 | - | 2 | 2026-07-12 |
| CQH7501 | - | 2 | 2026-07-12 |
| CQH7419 | Spring Airlines | 2 | 2026-05-29 |
| CQH7356 | Spring Airlines | 2 | 2026-05-16 |
| CQH7286 | Spring Airlines | 2 | 2026-05-30 |
| CQH6515 | Spring Airlines | 2 | 2026-04-25 |
| CQH6466 | Spring Airlines | 2 | 2026-05-06 |
| CQH6465 | Spring Airlines | 2 | 2026-05-06 |
| CQH6342 | - | 2 | 2026-07-06 |
| CQH8832 | Spring Airlines | 1 | 2026-07-04 |
| CQH8804 | - | 1 | 2026-05-07 |
| CQH8782 | Spring Airlines | 1 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CQH6411 | - | Jul 17, 09:55 UTC | Jul 17, 10:15 UTC | 20m |
| 2026-07-14 | CQH7636 | - | Jul 14, 23:40 UTC | Jul 15, 03:10 UTC | 3h 30m |
| 2026-07-13 | CQH6294 | - | Jul 13, 20:10 UTC | Jul 13, 21:30 UTC | 1h 20m |
| 2026-07-13 | CQH6293 | - | Jul 13, 17:25 UTC | Jul 13, 17:35 UTC | 10m |
| 2026-07-13 | CQH6293 | - | Jul 13, 16:15 UTC | Jul 13, 16:50 UTC | 35m |
| 2026-07-12 | CQH7502 | - | Jul 12, 04:20 UTC | Jul 12, 10:35 UTC | 6h 15m |
| 2026-07-12 | CQH7501 | - | Jul 12, 01:10 UTC | Jul 12, 02:30 UTC | 1h 20m |
| 2026-07-08 | CQH6294 | - | Jul 8, 20:10 UTC | Jul 8, 21:35 UTC | 1h 25m |
| 2026-07-08 | CQH6293 | - | Jul 8, 15:55 UTC | Jul 8, 17:15 UTC | 1h 20m |
| 2026-07-06 | CQH6776 | - | Jul 6, 23:55 UTC | Jul 7, 16:25 UTC | 16h 30m |
| 2026-07-06 | CQH6342 | - | Jul 6, 16:40 UTC | Jul 7, 07:15 UTC | 14h 35m |
| 2026-07-06 | CQH6342 | - | Jul 6, 04:05 UTC | Jul 7, 00:05 UTC | 20h 0m |
| 2026-07-04 | CQH8832 | XIY → SHE | Jul 4, 23:45 UTC | Jul 5, 03:00 UTC | 3h 15m |
| 2026-07-03 | CQH6294 | - | Jul 3, 20:00 UTC | Jul 3, 21:20 UTC | 1h 20m |
| 2026-07-03 | CQH6293 | - | Jul 3, 16:05 UTC | Jul 3, 17:25 UTC | 1h 20m |
| 2026-07-01 | CQH6775 | - | Jul 1, 23:55 UTC | Jul 2, 00:05 UTC | 10m |
| 2026-07-01 | CQH7588 | CJU → SHE | Jul 1, 03:20 UTC | Jul 2, 00:05 UTC | 20h 45m |
| 2026-06-30 | CQH7588 | CJU → SHE | Jun 30, 23:55 UTC | Jul 1, 03:45 UTC | 3h 50m |
| 2026-06-27 | CQH7684 | - | Jun 27, 23:14 UTC | Jun 27, 23:29 UTC | 15m |
| 2026-06-19 | CQH7556 | SZX → SHA | Jun 19, 22:14 UTC | Jun 19, 22:24 UTC | 10m |
| 2026-06-19 | CQH7555 | SHA → SZX | Jun 19, 16:44 UTC | Jun 19, 17:09 UTC | 25m |
| 2026-06-17 | CQH7461 | - | Jun 17, 10:25 UTC | Jun 17, 13:45 UTC | 3h 20m |
| 2026-06-14 | CQH7520 | SZX → SHA | Jun 14, 06:00 UTC | Jun 14, 06:15 UTC | 15m |
| 2026-06-05 | CQH6838 | ZUH → LHW | Jun 5, 04:05 UTC | Jun 5, 04:15 UTC | 10m |
| 2026-05-30 | CQH7286 | BKK → PVG | May 30, 02:00 UTC | May 30, 12:35 UTC | 10h 35m |
| 2026-05-29 | CQH7419 | CAN → BKK | May 29, 22:55 UTC | May 30, 00:50 UTC | 1h 55m |
| 2026-05-29 | CQH7348 | SGN → CAN | May 29, 16:00 UTC | May 29, 16:25 UTC | 25m |
| 2026-05-29 | CQH6922 | KUL → CAN | May 29, 05:45 UTC | May 29, 06:05 UTC | 20m |
| 2026-05-29 | CQH6922 | KUL → CAN | May 29, 02:30 UTC | May 29, 02:50 UTC | 20m |
| 2026-05-29 | CQH6921 | CAN → KUL | May 29, 00:40 UTC | May 29, 01:10 UTC | 30m |
| 2026-05-22 | CQH8552 | SIN → PVG | May 22, 22:30 UTC | May 23, 02:25 UTC | 3h 55m |
| 2026-05-22 | CQH8551 | PVG → SIN | May 22, 12:30 UTC | May 22, 20:45 UTC | 8h 15m |
| 2026-05-21 | CQH8632 | ZUH → NGB | May 21, 15:35 UTC | May 21, 15:50 UTC | 15m |
| 2026-05-21 | CQH8631 | NGB → ZUH | May 21, 11:50 UTC | May 21, 12:10 UTC | 20m |
| 2026-05-21 | CQH755U | - | May 21, 03:15 UTC | May 21, 03:55 UTC | 40m |
| 2026-05-16 | CQH6481 | SZX → DOY | May 16, 22:30 UTC | May 16, 22:40 UTC | 10m |
| 2026-05-16 | CQH7356 | LHW → SZX | May 16, 16:00 UTC | May 16, 16:10 UTC | 10m |
| 2026-05-15 | CQH7355 | SZX → LHW | May 15, 23:05 UTC | May 15, 23:15 UTC | 10m |
| 2026-05-14 | CQH7679 | SZX → LHW | May 14, 22:45 UTC | May 14, 23:00 UTC | 15m |
| 2026-05-14 | CQH7356 | LHW → SZX | May 14, 18:15 UTC | May 14, 18:25 UTC | 10m |
| 2026-05-13 | CQH7502 | BKK → TFU | May 13, 04:25 UTC | May 13, 10:25 UTC | 6h 0m |
| 2026-05-13 | CQH7501 | TFU → BKK | May 13, 01:55 UTC | May 13, 02:50 UTC | 55m |
| 2026-05-11 | - | - | May 11, 14:30 UTC | May 11, 14:40 UTC | 10m |
| 2026-05-11 | CQH7020 | - | May 11, 02:40 UTC | May 11, 02:50 UTC | 10m |
| 2026-05-10 | CQH8687 | - | May 10, 21:59 UTC | May 10, 22:09 UTC | 10m |
| 2026-05-10 | CQH8782 | HKT → SZX | May 10, 19:15 UTC | May 10, 19:30 UTC | 15m |
| 2026-05-10 | CQH7653 | TFU → HKT | May 10, 13:19 UTC | May 10, 17:49 UTC | 4h 30m |
| 2026-05-07 | CQH8804 | - | May 7, 14:20 UTC | May 7, 14:40 UTC | 20m |
| 2026-05-06 | CQH6466 | BKK → NNG | May 6, 08:25 UTC | May 6, 09:25 UTC | 1h 0m |
| 2026-05-06 | CQH6465 | NNG → BKK | May 6, 06:05 UTC | May 6, 06:50 UTC | 45m |
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-328T page for operator, model, and routing details .