sensors Mode-S transponder
7821F4
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32KS · AIRBUS A-320neo
- Hex
- 7821F4
- Octal
- 36020764
- Decimal
- 7,873,012
- Country
- CN
- Tail
- B-32KS
- Type
- A20N
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 7821F4 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 |
|---|---|---|---|
| CQH8892 | Spring Airlines | 3 | 2026-04-15 |
| CQH7588 | Spring Airlines | 3 | 2026-06-13 |
| CQH8933 | Spring Airlines | 2 | 2026-06-04 |
| CQH8891 | Spring Airlines | 2 | 2026-04-15 |
| CQH8731 | Spring Airlines | 2 | 2026-06-11 |
| CQH8598 | Spring Airlines | 2 | 2026-04-20 |
| CQH8522 | Spring Airlines | 2 | 2026-05-27 |
| CQH7587 | Spring Airlines | 2 | 2026-06-14 |
| CQH6887 | Spring Airlines | 2 | 2026-06-10 |
| CQH6566 | - | 2 | 2026-04-13 |
| CQH6218 | Spring Airlines | 2 | 2026-06-05 |
| CQH6217 | Spring Airlines | 2 | 2026-06-05 |
| CQH8934 | Spring Airlines | 1 | 2026-05-21 |
| CQH8781 | - | 1 | 2026-07-02 |
| CQH8762 | - | 1 | 2026-07-06 |
| CQH8761 | - | 1 | 2026-07-06 |
| CQH8753 | Spring Airlines | 1 | 2026-05-30 |
| CQH8688 | - | 1 | 2026-07-02 |
| CQH8672 | - | 1 | 2026-06-27 |
| CQH8661 | Spring Airlines | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | CQH7368 | - | Jul 6, 14:45 UTC | Jul 6, 23:45 UTC | 9h 0m |
| 2026-07-06 | CQH8762 | - | Jul 6, 08:45 UTC | Jul 6, 08:55 UTC | 10m |
| 2026-07-06 | CQH8761 | - | Jul 6, 04:35 UTC | Jul 6, 04:50 UTC | 15m |
| 2026-07-02 | CQH7654 | - | Jul 2, 23:25 UTC | Jul 3, 05:10 UTC | 5h 45m |
| 2026-07-02 | CQH8781 | - | Jul 2, 22:25 UTC | Jul 2, 22:40 UTC | 15m |
| 2026-07-02 | CQH8688 | - | Jul 2, 18:10 UTC | Jul 2, 18:20 UTC | 10m |
| 2026-07-02 | CQH7019 | - | Jul 2, 12:45 UTC | Jul 2, 13:00 UTC | 15m |
| 2026-06-28 | CQH7520 | - | Jun 28, 05:55 UTC | Jun 28, 06:05 UTC | 10m |
| 2026-06-27 | CQH6728 | - | Jun 27, 16:44 UTC | Jun 27, 16:55 UTC | 10m |
| 2026-06-27 | CQH6727 | - | Jun 27, 10:34 UTC | Jun 27, 10:50 UTC | 15m |
| 2026-06-27 | CQH8672 | - | Jun 27, 08:39 UTC | Jun 27, 08:55 UTC | 15m |
| 2026-06-24 | CQH7133 | LHW → TSN | Jun 24, 11:20 UTC | Jun 24, 11:45 UTC | 25m |
| 2026-06-16 | CQH6481 | - | Jun 16, 22:30 UTC | Jun 16, 22:45 UTC | 15m |
| 2026-06-16 | CQH7355 | - | Jun 16, 03:05 UTC | Jun 16, 03:20 UTC | 15m |
| 2026-06-14 | CQH7587 | SHE → CJU | Jun 14, 00:05 UTC | Jun 14, 10:05 UTC | 10h 0m |
| 2026-06-13 | CQH7588 | CJU → SHE | Jun 13, 03:10 UTC | Jun 14, 03:00 UTC | 23h 49m |
| 2026-06-12 | CQH7587 | SHE → CJU | Jun 12, 06:15 UTC | Jun 13, 00:50 UTC | 18h 35m |
| 2026-06-11 | CQH8731 | SHE → NGB | Jun 11, 14:20 UTC | Jun 12, 06:30 UTC | 16h 10m |
| 2026-06-11 | CQH7588 | CJU → SHE | Jun 11, 00:25 UTC | Jun 11, 14:45 UTC | 14h 20m |
| 2026-06-10 | CQH7588 | CJU → SHE | Jun 10, 14:40 UTC | Jun 11, 03:30 UTC | 12h 50m |
| 2026-06-10 | CQH6887 | SHE → TYN | Jun 10, 12:05 UTC | Jun 10, 12:25 UTC | 20m |
| 2026-06-08 | CQH7286 | BKK → PVG | Jun 8, 01:50 UTC | Jun 8, 04:05 UTC | 2h 15m |
| 2026-06-07 | CQH7419 | CAN → BKK | Jun 7, 22:50 UTC | Jun 8, 00:20 UTC | 1h 30m |
| 2026-06-07 | CQH7750 | NGB → CAN | Jun 7, 17:10 UTC | Jun 7, 17:20 UTC | 10m |
| 2026-06-07 | CQH8632 | ZUH → NGB | Jun 7, 12:15 UTC | Jun 7, 12:30 UTC | 15m |
| 2026-06-07 | CQH8631 | NGB → ZUH | Jun 7, 10:00 UTC | Jun 7, 10:50 UTC | 50m |
| 2026-06-06 | CQH8731 | SHE → NGB | Jun 6, 11:25 UTC | Jun 6, 14:54 UTC | 3h 30m |
| 2026-06-05 | CQH6218 | NRT → PVG | Jun 5, 11:10 UTC | Jun 5, 12:45 UTC | 1h 35m |
| 2026-06-05 | CQH6217 | PVG → NRT | Jun 5, 01:40 UTC | Jun 5, 09:30 UTC | 7h 50m |
| 2026-06-04 | CQH8933 | CAN → CNX | Jun 4, 23:55 UTC | Jun 5, 00:30 UTC | 35m |
| 2026-06-01 | CQH6313 | CGQ → NGB | Jun 1, 03:25 UTC | Jun 1, 03:55 UTC | 30m |
| 2026-05-30 | CQH8753 | SZX → XIY | May 30, 22:40 UTC | May 30, 22:55 UTC | 15m |
| 2026-05-30 | CQH6482 | DOY → SZX | May 30, 16:25 UTC | May 30, 16:50 UTC | 25m |
| 2026-05-30 | CQH8661 | SJW → CGQ | May 30, 09:25 UTC | May 30, 09:45 UTC | 20m |
| 2026-05-27 | CQH8522 | HKT → PVG | May 27, 12:20 UTC | May 27, 20:45 UTC | 8h 25m |
| 2026-05-24 | CQH7050 | CJJ → PVG | May 24, 03:05 UTC | May 24, 03:30 UTC | 25m |
| 2026-05-24 | CQH7049 | PVG → CJJ | May 24, 01:35 UTC | May 24, 02:00 UTC | 25m |
| 2026-05-22 | CQH6218 | NRT → PVG | May 22, 11:35 UTC | May 22, 12:45 UTC | 1h 10m |
| 2026-05-22 | CQH6217 | PVG → NRT | May 22, 02:00 UTC | May 22, 09:35 UTC | 7h 35m |
| 2026-05-21 | CQH8933 | CAN → CNX | May 21, 22:40 UTC | May 22, 01:00 UTC | 2h 20m |
| 2026-05-21 | CQH8934 | CNX → CAN | May 21, 14:35 UTC | May 21, 14:50 UTC | 15m |
| 2026-05-21 | CQH8511 | PVG → CNX | May 21, 05:05 UTC | May 21, 13:25 UTC | 8h 20m |
| 2026-05-17 | CQH6838 | ZUH → LHW | May 17, 03:30 UTC | May 17, 03:40 UTC | 10m |
| 2026-05-10 | CQH6538 | FUK → PVG | May 10, 09:00 UTC | May 10, 09:10 UTC | 10m |
| 2026-05-10 | CQH6537 | PVG → FUK | May 10, 07:19 UTC | May 10, 07:30 UTC | 10m |
| 2026-05-09 | CQH6826 | - | May 9, 10:45 UTC | May 10, 03:00 UTC | 16h 15m |
| 2026-05-09 | CQH6825 | - | May 9, 06:55 UTC | May 9, 09:20 UTC | 2h 25m |
| 2026-05-05 | CQH6628 | CNX → XIY | May 5, 14:45 UTC | May 5, 15:01 UTC | 15m |
| 2026-05-05 | CQH6627 | XIY → CNX | May 5, 12:55 UTC | May 5, 13:15 UTC | 20m |
| 2026-05-05 | CQH6836 | ZUH → KHN | May 5, 03:55 UTC | May 5, 04:10 UTC | 15m |
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-32KS page for operator, model, and routing details .