sensors Mode-S transponder
7817A5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30AD · AIRBUS A-320neo
- Hex
- 7817A5
- Octal
- 36013645
- Decimal
- 7,870,373
- Country
- CN
- Tail
- B-30AD
- Type
- A20N
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7817A5 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 |
|---|---|---|---|
| CQH6524 | Spring Airlines | 3 | 2026-06-06 |
| CQH6523 | Spring Airlines | 3 | 2026-06-06 |
| CQH8715 | Spring Airlines | 2 | 2026-05-23 |
| CQH8631 | Spring Airlines | 2 | 2026-05-07 |
| CQH7496 | Spring Airlines | 2 | 2026-06-02 |
| CQH7259 | Spring Airlines | 2 | 2026-05-22 |
| CQH6922 | Spring Airlines | 2 | 2026-04-24 |
| CQH8934 | Spring Airlines | 1 | 2026-04-26 |
| CQH8933 | Spring Airlines | 1 | 2026-06-03 |
| CQH8875 | Spring Airlines | 1 | 2026-05-19 |
| CQH8786 | - | 1 | 2026-05-08 |
| CQH8731 | Spring Airlines | 1 | 2026-05-07 |
| CQH8666 | Spring Airlines | 1 | 2026-04-27 |
| CQH8632 | Spring Airlines | 1 | 2026-05-08 |
| CQH8598 | Spring Airlines | 1 | 2026-05-20 |
| CQH8597 | Spring Airlines | 1 | 2026-05-20 |
| CQH8560 | Spring Airlines | 1 | 2026-05-19 |
| CQH8559 | Spring Airlines | 1 | 2026-05-19 |
| CQH8534 | - | 1 | 2026-04-20 |
| CQH8522 | Spring Airlines | 1 | 2026-05-15 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | CQH6524 | KUL → PVG | Jun 6, 10:39 UTC | Jun 6, 14:50 UTC | 4h 10m |
| 2026-06-06 | CQH6523 | PVG → KUL | Jun 6, 04:35 UTC | Jun 6, 08:55 UTC | 4h 20m |
| 2026-06-04 | CQH8512 | CNX → PVG | Jun 4, 01:55 UTC | Jun 4, 03:15 UTC | 1h 20m |
| 2026-06-03 | CQH8933 | CAN → CNX | Jun 3, 22:05 UTC | Jun 4, 00:25 UTC | 2h 20m |
| 2026-06-02 | CQH7496 | SIN → CAN | Jun 2, 16:30 UTC | Jun 2, 16:50 UTC | 20m |
| 2026-06-02 | CQH7496 | SIN → CAN | Jun 2, 13:20 UTC | Jun 2, 13:45 UTC | 25m |
| 2026-06-02 | CQH7495 | CAN → SIN | Jun 2, 08:35 UTC | Jun 2, 08:50 UTC | 15m |
| 2026-05-23 | CQH7420 | BKK → CAN | May 23, 15:15 UTC | May 23, 15:50 UTC | 35m |
| 2026-05-23 | CQH7285 | HKG → BKK | May 23, 05:40 UTC | May 23, 13:15 UTC | 7h 35m |
| 2026-05-23 | CQH8715 | PVG → HKG | May 23, 03:30 UTC | May 23, 03:35 UTC | 5m |
| 2026-05-22 | CQH8715 | PVG → HKG | May 22, 11:05 UTC | May 23, 02:50 UTC | 15h 45m |
| 2026-05-22 | CQH7259 | PVG → PEN | May 22, 01:50 UTC | May 22, 11:55 UTC | 10h 5m |
| 2026-05-21 | CQH7259 | PVG → PEN | May 21, 06:45 UTC | May 22, 02:55 UTC | 20h 10m |
| 2026-05-20 | CQH7057 | PVG → UBN | May 20, 12:45 UTC | May 21, 06:55 UTC | 18h 10m |
| 2026-05-20 | CQH8598 | HKG → PVG | May 20, 08:35 UTC | May 21, 06:55 UTC | 22h 20m |
| 2026-05-20 | CQH8597 | PVG → HKG | May 20, 03:40 UTC | May 20, 06:25 UTC | 2h 46m |
| 2026-05-19 | CQH8560 | ICN → PVG | May 19, 10:35 UTC | May 20, 06:25 UTC | 19h 51m |
| 2026-05-19 | CQH8559 | PVG → ICN | May 19, 03:35 UTC | May 19, 09:10 UTC | 5h 35m |
| 2026-05-19 | CQH8875 | PVG → MFM | May 19, 01:35 UTC | May 19, 01:50 UTC | 15m |
| 2026-05-18 | CQH6524 | KUL → PVG | May 18, 14:00 UTC | May 18, 15:00 UTC | 1h 0m |
| 2026-05-18 | CQH6524 | KUL → PVG | May 18, 10:50 UTC | May 18, 11:05 UTC | 15m |
| 2026-05-18 | CQH6523 | PVG → KUL | May 18, 08:55 UTC | May 18, 09:15 UTC | 20m |
| 2026-05-18 | CQH6523 | PVG → KUL | May 18, 04:55 UTC | May 18, 06:01 UTC | 1h 5m |
| 2026-05-17 | CQH7360 | YSQ → PVG | May 17, 03:30 UTC | May 17, 04:05 UTC | 35m |
| 2026-05-15 | CQH8522 | HKT → PVG | May 15, 14:05 UTC | May 15, 19:50 UTC | 5h 44m |
| 2026-05-08 | CQH8786 | - | May 8, 23:50 UTC | May 9, 14:50 UTC | 15h 0m |
| 2026-05-08 | CQH8632 | ZUH → NGB | May 8, 10:04 UTC | May 8, 10:14 UTC | 10m |
| 2026-05-07 | CQH8631 | NGB → ZUH | May 7, 14:15 UTC | May 8, 08:49 UTC | 18h 34m |
| 2026-05-07 | CQH8631 | NGB → ZUH | May 7, 11:25 UTC | May 8, 08:49 UTC | 21h 24m |
| 2026-05-07 | CQH8731 | SHE → NGB | May 7, 02:30 UTC | May 7, 14:50 UTC | 12h 20m |
| 2026-05-03 | CQH7282 | BKK → PVG | May 3, 10:10 UTC | May 3, 12:15 UTC | 2h 5m |
| 2026-05-03 | CQH7281 | PVG → BKK | May 3, 07:55 UTC | May 3, 08:50 UTC | 55m |
| 2026-05-01 | CQH6628 | CNX → XIY | May 1, 14:45 UTC | May 2, 03:05 UTC | 12h 20m |
| 2026-05-01 | CQH6627 | XIY → CNX | May 1, 12:55 UTC | May 1, 13:15 UTC | 20m |
| 2026-05-01 | CQH6836 | ZUH → KHN | May 1, 03:15 UTC | May 1, 03:25 UTC | 10m |
| 2026-04-27 | CQH8666 | HKT → PVG | Apr 27, 12:20 UTC | Apr 27, 17:55 UTC | 5h 35m |
| 2026-04-26 | CQH8934 | CNX → CAN | Apr 26, 14:45 UTC | Apr 26, 15:05 UTC | 20m |
| 2026-04-26 | CQH8511 | PVG → CNX | Apr 26, 13:20 UTC | Apr 26, 13:45 UTC | 25m |
| 2026-04-25 | CQH7286 | BKK → PVG | Apr 25, 01:55 UTC | Apr 25, 04:55 UTC | 3h 0m |
| 2026-04-24 | CQH7419 | CAN → BKK | Apr 24, 22:35 UTC | Apr 25, 00:55 UTC | 2h 20m |
| 2026-04-24 | CQH7348 | SGN → CAN | Apr 24, 13:55 UTC | Apr 24, 14:25 UTC | 30m |
| 2026-04-24 | CQH7347 | CAN → SGN | Apr 24, 08:45 UTC | Apr 24, 08:55 UTC | 10m |
| 2026-04-24 | CQH6922 | KUL → CAN | Apr 24, 05:55 UTC | Apr 24, 06:25 UTC | 30m |
| 2026-04-24 | CQH6922 | KUL → CAN | Apr 24, 02:45 UTC | Apr 24, 04:10 UTC | 1h 25m |
| 2026-04-23 | CQH6921 | CAN → KUL | Apr 23, 23:40 UTC | Apr 24, 01:10 UTC | 1h 30m |
| 2026-04-21 | CQH7008 | PNH → CAN | Apr 21, 16:05 UTC | Apr 21, 16:20 UTC | 15m |
| 2026-04-20 | CQH8534 | - | Apr 20, 17:50 UTC | Apr 21, 10:20 UTC | 16h 30m |
| 2026-04-20 | CQH7007 | - | Apr 20, 11:45 UTC | Apr 20, 11:55 UTC | 10m |
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-30AD page for operator, model, and routing details .