sensors Mode-S transponder
7816D1
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-308V · AIRBUS A-320neo
- Hex
- 7816D1
- Octal
- 36013321
- Decimal
- 7,870,161
- Country
- CN
- Tail
- B-308V
- Type
- A20N
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 7816D1 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 | - | 7 | 2026-06-13 |
| CQH8875 | Spring Airlines | 3 | 2026-04-29 |
| CQH8521 | Spring Airlines | 3 | 2026-06-29 |
| CQH7260 | Spring Airlines | 3 | 2026-04-26 |
| CQH6524 | Spring Airlines | 3 | 2026-06-13 |
| CQH6294 | - | 3 | 2026-07-09 |
| CQH6293 | - | 3 | 2026-07-09 |
| CQH8952 | - | 2 | 2026-06-30 |
| CQH8876 | Spring Airlines | 2 | 2026-04-30 |
| CQH8597 | - | 2 | 2026-07-15 |
| CQH8516 | - | 2 | 2026-07-01 |
| CQH8515 | - | 2 | 2026-07-01 |
| CQH7496 | Spring Airlines | 2 | 2026-05-23 |
| CQH7342 | - | 2 | 2026-06-24 |
| CQH7341 | - | 2 | 2026-06-24 |
| CQH7286 | - | 2 | 2026-07-14 |
| CQH6922 | Spring Airlines | 2 | 2026-05-24 |
| CQH6921 | Spring Airlines | 2 | 2026-05-24 |
| CQH6610 | - | 2 | 2026-06-14 |
| CQH6596 | Spring Airlines | 2 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | CQH8598 | - | Jul 15, 10:25 UTC | Jul 15, 14:40 UTC | 4h 15m |
| 2026-07-15 | CQH8597 | - | Jul 15, 05:15 UTC | Jul 15, 08:35 UTC | 3h 20m |
| 2026-07-14 | CQH7286 | - | Jul 14, 01:50 UTC | Jul 14, 03:25 UTC | 1h 35m |
| 2026-07-11 | CQH6278 | - | Jul 11, 17:45 UTC | Jul 11, 18:05 UTC | 20m |
| 2026-07-11 | CQH6278 | - | Jul 11, 14:35 UTC | Jul 11, 15:05 UTC | 30m |
| 2026-07-11 | CQH6277 | - | Jul 11, 09:55 UTC | Jul 11, 13:25 UTC | 3h 30m |
| 2026-07-09 | CQH6294 | - | Jul 9, 20:10 UTC | Jul 9, 21:35 UTC | 1h 25m |
| 2026-07-09 | CQH6293 | - | Jul 9, 17:00 UTC | Jul 9, 18:15 UTC | 1h 15m |
| 2026-07-08 | CQH6341 | - | Jul 8, 04:00 UTC | Jul 8, 14:35 UTC | 10h 35m |
| 2026-07-07 | CQH6732 | - | Jul 7, 09:25 UTC | Jul 8, 04:15 UTC | 18h 50m |
| 2026-07-06 | CQH6411 | - | Jul 6, 10:30 UTC | Jul 7, 09:35 UTC | 23h 5m |
| 2026-07-05 | CQH6838 | - | Jul 5, 04:05 UTC | Jul 5, 04:15 UTC | 10m |
| 2026-07-01 | CQH8516 | - | Jul 1, 16:15 UTC | Jul 1, 17:55 UTC | 1h 40m |
| 2026-07-01 | CQH8515 | - | Jul 1, 04:35 UTC | Jul 1, 13:50 UTC | 9h 15m |
| 2026-06-30 | CQH8952 | - | Jun 30, 03:20 UTC | Jun 30, 03:50 UTC | 30m |
| 2026-06-29 | CQH8521 | PVG → HKT | Jun 29, 12:34 UTC | Jun 30, 02:05 UTC | 13h 31m |
| 2026-06-28 | CQH8521 | PVG → HKT | Jun 28, 16:19 UTC | Jun 29, 15:09 UTC | 22h 50m |
| 2026-06-28 | CQH8516 | - | Jun 28, 16:09 UTC | Jun 28, 17:50 UTC | 1h 40m |
| 2026-06-28 | CQH8515 | ICN → HND | Jun 28, 08:05 UTC | Jun 28, 13:40 UTC | 5h 35m |
| 2026-06-28 | CQH8559 | - | Jun 28, 05:55 UTC | Jun 28, 06:34 UTC | 40m |
| 2026-06-25 | CQH8832 | XIY → SHE | Jun 25, 23:39 UTC | Jun 26, 03:39 UTC | 4h 0m |
| 2026-06-24 | CQH7556 | SZX → SHA | Jun 24, 22:10 UTC | Jun 24, 22:19 UTC | 10m |
| 2026-06-24 | CQH7342 | - | Jun 24, 17:40 UTC | Jun 24, 17:59 UTC | 20m |
| 2026-06-24 | CQH7342 | - | Jun 24, 13:10 UTC | Jun 24, 14:34 UTC | 1h 25m |
| 2026-06-24 | CQH7341 | - | Jun 24, 11:14 UTC | Jun 24, 11:29 UTC | 15m |
| 2026-06-24 | CQH7341 | - | Jun 24, 06:59 UTC | Jun 24, 07:10 UTC | 10m |
| 2026-06-23 | CQH8753 | - | Jun 23, 22:44 UTC | Jun 23, 23:00 UTC | 15m |
| 2026-06-23 | CQH6596 | TNA → SZX | Jun 23, 15:44 UTC | Jun 23, 15:59 UTC | 15m |
| 2026-06-21 | CQH6595 | - | Jun 21, 22:44 UTC | Jun 21, 22:54 UTC | 10m |
| 2026-06-21 | CQH7555 | SHA → SZX | Jun 21, 16:49 UTC | Jun 21, 17:15 UTC | 25m |
| 2026-06-20 | CQH7684 | - | Jun 20, 22:59 UTC | Jun 20, 23:25 UTC | 25m |
| 2026-06-17 | CQH6294 | - | Jun 17, 20:20 UTC | Jun 17, 20:45 UTC | 25m |
| 2026-06-17 | CQH6293 | - | Jun 17, 16:55 UTC | Jun 17, 17:25 UTC | 30m |
| 2026-06-14 | CQH6610 | - | Jun 14, 04:45 UTC | Jun 14, 05:05 UTC | 20m |
| 2026-06-13 | CQH6524 | KUL → PVG | Jun 13, 10:45 UTC | Jun 13, 14:50 UTC | 4h 5m |
| 2026-06-13 | CQH6523 | - | Jun 13, 08:40 UTC | Jun 13, 09:10 UTC | 30m |
| 2026-06-12 | CQH8756 | - | Jun 12, 19:50 UTC | Jun 13, 05:50 UTC | 9h 59m |
| 2026-06-12 | CQH8755 | PVG → BKK | Jun 12, 11:00 UTC | Jun 12, 18:25 UTC | 7h 25m |
| 2026-06-12 | CQH6610 | - | Jun 12, 03:30 UTC | Jun 12, 03:40 UTC | 10m |
| 2026-06-12 | CQH6609 | PVG → FUK | Jun 12, 02:00 UTC | Jun 12, 02:10 UTC | 10m |
| 2026-06-11 | CQH6524 | KUL → PVG | Jun 11, 10:55 UTC | Jun 11, 14:15 UTC | 3h 20m |
| 2026-06-10 | CQH8522 | HKT → PVG | Jun 10, 14:20 UTC | Jun 11, 09:25 UTC | 19h 5m |
| 2026-06-10 | CQH8521 | PVG → HKT | Jun 10, 12:25 UTC | Jun 11, 09:25 UTC | 21h 0m |
| 2026-06-05 | CQH6411 | CGO → CGQ | Jun 5, 09:50 UTC | Jun 5, 10:10 UTC | 20m |
| 2026-06-03 | CQH6341 | SHE → HFE | Jun 3, 03:50 UTC | Jun 3, 04:05 UTC | 15m |
| 2026-06-01 | - | - | Jun 1, 07:10 UTC | Jun 1, 07:20 UTC | 10m |
| 2026-05-30 | CQH8792 | CTS → PVG | May 30, 05:00 UTC | May 30, 07:15 UTC | 2h 15m |
| 2026-05-29 | CQH8791 | PVG → CTS | May 29, 19:30 UTC | May 30, 03:20 UTC | 7h 50m |
| 2026-05-27 | CQH6294 | BKK → XIY | May 27, 20:05 UTC | May 27, 21:05 UTC | 1h 0m |
| 2026-05-27 | CQH6293 | XIY → BKK | May 27, 16:20 UTC | May 27, 17:20 UTC | 1h 0m |
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-308V page for operator, model, and routing details .