sensors Mode-S transponder
7821BD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32K7 · AIRBUS A-320neo
- Hex
- 7821BD
- Octal
- 36020675
- Decimal
- 7,872,957
- Country
- CN
- Tail
- B-32K7
- Type
- A20N
- Flights observed
- 83
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 7821BD 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 |
|---|---|---|---|
| CHH7004 | Hainan Airlines | 11 | 2026-05-19 |
| CHH7090 | Hainan Airlines | 6 | 2026-06-14 |
| CHH7008 | Hainan Airlines | 6 | 2026-05-15 |
| CHH7002 | - | 5 | 2026-07-10 |
| CHH7052 | - | 4 | 2026-07-01 |
| CHH7038 | Hainan Airlines | 4 | 2026-06-03 |
| CHH7089 | - | 3 | 2026-06-29 |
| CHH7044 | - | 3 | 2026-07-05 |
| CHH7687 | Hainan Airlines | 2 | 2026-05-24 |
| CHH7206 | - | 2 | 2026-07-13 |
| CHH7115 | Hainan Airlines | 2 | 2026-06-13 |
| CHH7076 | - | 2 | 2026-06-30 |
| CHH7075 | - | 2 | 2026-06-30 |
| CHH7056 | - | 2 | 2026-07-02 |
| CHH7037 | - | 2 | 2026-07-04 |
| CHH7034 | Hainan Airlines | 2 | 2026-04-25 |
| CHH7018 | Hainan Airlines | 2 | 2026-05-26 |
| CHH7007 | Hainan Airlines | 2 | 2026-05-19 |
| CHH7005 | Hainan Airlines | 2 | 2026-04-19 |
| CHH7940 | - | 1 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CHH7206 | - | Jul 13, 18:15 UTC | Jul 13, 18:25 UTC | 10m |
| 2026-07-13 | CHH7206 | - | Jul 13, 16:55 UTC | Jul 13, 17:05 UTC | 10m |
| 2026-07-12 | CHH7940 | - | Jul 12, 04:10 UTC | Jul 12, 13:55 UTC | 9h 45m |
| 2026-07-12 | CHH7939 | - | Jul 12, 02:30 UTC | Jul 12, 02:45 UTC | 15m |
| 2026-07-11 | CHH7070 | - | Jul 11, 02:05 UTC | Jul 11, 15:40 UTC | 13h 35m |
| 2026-07-10 | CHH7002 | - | Jul 10, 23:30 UTC | Jul 10, 23:50 UTC | 20m |
| 2026-07-10 | CHH7214 | - | Jul 10, 15:30 UTC | Jul 10, 15:45 UTC | 15m |
| 2026-07-08 | CHH7092 | - | Jul 8, 05:55 UTC | Jul 8, 06:10 UTC | 15m |
| 2026-07-06 | CHH7091 | - | Jul 6, 01:30 UTC | Jul 6, 06:10 UTC | 4h 40m |
| 2026-07-05 | CHH7044 | - | Jul 5, 09:15 UTC | Jul 5, 16:00 UTC | 6h 45m |
| 2026-07-04 | CHH7037 | - | Jul 4, 10:15 UTC | Jul 5, 09:15 UTC | 23h 0m |
| 2026-07-03 | CHH7002 | - | Jul 3, 23:25 UTC | Jul 3, 23:35 UTC | 10m |
| 2026-07-02 | CHH7056 | - | Jul 2, 01:10 UTC | Jul 2, 14:55 UTC | 13h 45m |
| 2026-07-01 | CHH7056 | - | Jul 1, 15:25 UTC | Jul 2, 14:55 UTC | 23h 30m |
| 2026-07-01 | CHH7052 | - | Jul 1, 12:15 UTC | Jul 2, 10:25 UTC | 22h 10m |
| 2026-07-01 | CHH7052 | - | Jul 1, 01:10 UTC | Jul 1, 09:45 UTC | 8h 35m |
| 2026-06-30 | CHH7076 | - | Jun 30, 03:55 UTC | Jun 30, 07:25 UTC | 3h 30m |
| 2026-06-30 | CHH7075 | - | Jun 30, 01:09 UTC | Jun 30, 02:05 UTC | 56m |
| 2026-06-29 | CHH7089 | - | Jun 29, 11:14 UTC | Jun 29, 15:00 UTC | 3h 45m |
| 2026-06-29 | CHH7044 | - | Jun 29, 02:14 UTC | Jun 29, 08:29 UTC | 6h 15m |
| 2026-06-28 | CHH7089 | - | Jun 28, 11:25 UTC | Jun 28, 16:14 UTC | 4h 50m |
| 2026-06-24 | - | - | Jun 24, 02:45 UTC | Jun 24, 02:54 UTC | 10m |
| 2026-06-17 | CHH6027 | HAK → CSX | Jun 17, 09:50 UTC | Jun 18, 07:30 UTC | 21h 40m |
| 2026-06-15 | CHH7093 | HAK → KMG | Jun 15, 06:45 UTC | Jun 15, 10:35 UTC | 3h 50m |
| 2026-06-14 | CHH7090 | NKG → HAK | Jun 14, 14:50 UTC | Jun 15, 03:55 UTC | 13h 5m |
| 2026-06-14 | CHH7090 | NKG → HAK | Jun 14, 07:10 UTC | Jun 15, 03:55 UTC | 20h 45m |
| 2026-06-13 | CHH7115 | HAK → NKG | Jun 13, 01:35 UTC | Jun 13, 15:40 UTC | 14h 4m |
| 2026-06-12 | CHH7115 | HAK → NKG | Jun 12, 14:25 UTC | Jun 13, 06:55 UTC | 16h 29m |
| 2026-06-11 | CHH7012 | CAN → HAK | Jun 11, 15:10 UTC | Jun 11, 15:20 UTC | 10m |
| 2026-06-07 | - | - | Jun 7, 05:30 UTC | Jun 7, 05:40 UTC | 10m |
| 2026-06-05 | CHH7052 | HGH → HAK | Jun 5, 05:20 UTC | Jun 6, 00:45 UTC | 19h 25m |
| 2026-06-05 | CHH7052 | HGH → HAK | Jun 5, 01:30 UTC | Jun 6, 00:45 UTC | 23h 15m |
| 2026-06-03 | CHH7038 | HFE → HAK | Jun 3, 14:00 UTC | Jun 4, 07:30 UTC | 17h 30m |
| 2026-06-03 | CHH7038 | HFE → HAK | Jun 3, 03:45 UTC | Jun 4, 02:00 UTC | 22h 15m |
| 2026-06-03 | CHH7038 | HFE → HAK | Jun 3, 00:40 UTC | Jun 3, 14:20 UTC | 13h 40m |
| 2026-06-02 | CHH7076 | FOC → HAK | Jun 2, 03:05 UTC | Jun 2, 04:05 UTC | 1h 0m |
| 2026-06-02 | CHH7075 | HAK → KHN | Jun 2, 00:35 UTC | Jun 2, 00:55 UTC | 20m |
| 2026-05-31 | CHH7090 | NKG → HAK | May 31, 14:45 UTC | Jun 1, 06:20 UTC | 15h 35m |
| 2026-05-30 | CHH7038 | HFE → HAK | May 30, 14:10 UTC | May 30, 14:20 UTC | 10m |
| 2026-05-29 | CHH7089 | HAK → NKG | May 29, 02:30 UTC | May 29, 12:15 UTC | 9h 45m |
| 2026-05-28 | CHH7116 | NKG → HAK | May 28, 01:50 UTC | May 28, 15:30 UTC | 13h 40m |
| 2026-05-27 | CHH7090 | NKG → HAK | May 27, 14:55 UTC | May 28, 06:55 UTC | 16h 0m |
| 2026-05-27 | CHH7090 | NKG → HAK | May 27, 11:00 UTC | May 28, 06:55 UTC | 19h 55m |
| 2026-05-27 | CHH7090 | NKG → HAK | May 27, 02:14 UTC | May 27, 15:15 UTC | 13h 1m |
| 2026-05-26 | CHH7018 | ZUH → HAK | May 26, 02:15 UTC | May 26, 02:24 UTC | 10m |
| 2026-05-24 | CHH7687 | NGB → TAO | May 24, 23:30 UTC | May 25, 10:05 UTC | 10h 35m |
| 2026-05-24 | CHH7687 | NGB → TAO | May 24, 07:50 UTC | May 24, 23:46 UTC | 15h 56m |
| 2026-05-23 | CHH7216 | NKG → HAK | May 23, 04:45 UTC | May 23, 09:35 UTC | 4h 50m |
| 2026-05-23 | CHH7006 | CAN → HAK | May 23, 01:45 UTC | May 23, 02:00 UTC | 15m |
| 2026-05-19 | CHH7007 | HAK → CAN | May 19, 09:00 UTC | May 19, 09:20 UTC | 20m |
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-32K7 page for operator, model, and routing details .