sensors Mode-S transponder
782384
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-228E · BOEING 737 MAX 8
- Hex
- 782384
- Octal
- 36021604
- Decimal
- 7,873,412
- Country
- CN
- Tail
- B-228E
- Type
- B38M
- Flights observed
- 54
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Current position
Country allocation
The ICAO 24-bit address 782384 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 |
|---|---|---|---|
| CHH7996 | Hainan Airlines | 4 | 2026-05-26 |
| CHH7995 | Hainan Airlines | 4 | 2026-05-26 |
| CHH430 | Hainan Airlines | 4 | 2026-05-30 |
| CHH7187 | Hainan Airlines | 3 | 2026-05-29 |
| CHH429 | Hainan Airlines | 3 | 2026-05-30 |
| CHH7688 | Hainan Airlines | 2 | 2026-05-17 |
| CHH7567 | Hainan Airlines | 2 | 2026-05-06 |
| CHH7350 | Hainan Airlines | 2 | 2026-05-31 |
| CHH7119 | Hainan Airlines | 2 | 2026-05-20 |
| CHH7772 | - | 1 | 2026-04-20 |
| CHH7771 | - | 1 | 2026-04-20 |
| CHH7744 | Hainan Airlines | 1 | 2026-04-30 |
| CHH7743 | Hainan Airlines | 1 | 2026-04-29 |
| CHH7579 | Hainan Airlines | 1 | 2026-04-28 |
| CHH7577 | Hainan Airlines | 1 | 2026-04-24 |
| CHH7557 | Hainan Airlines | 1 | 2026-04-30 |
| CHH7398 | Hainan Airlines | 1 | 2026-04-19 |
| CHH7397 | - | 1 | 2026-04-20 |
| CHH7367 | - | 1 | 2026-04-21 |
| CHH7349 | Hainan Airlines | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | CHH7349 | SYX → CKG | May 31, 13:35 UTC | May 31, 13:50 UTC | 15m |
| 2026-05-31 | CHH7350 | CKG → SYX | May 31, 10:40 UTC | May 31, 11:10 UTC | 30m |
| 2026-05-30 | CHH7350 | CKG → SYX | May 30, 13:35 UTC | May 31, 11:10 UTC | 21h 35m |
| 2026-05-30 | CHH430 | BKK → PEK | May 30, 07:05 UTC | May 30, 09:00 UTC | 1h 55m |
| 2026-05-30 | CHH429 | PEK → BKK | May 30, 03:10 UTC | May 30, 04:50 UTC | 1h 40m |
| 2026-05-29 | CHH7187 | PEK → WUH | May 29, 00:45 UTC | May 29, 01:00 UTC | 15m |
| 2026-05-28 | CHH7147 | PEK → TFU | May 28, 00:10 UTC | May 28, 00:30 UTC | 20m |
| 2026-05-27 | CHH7279 | PEK → SYX | May 27, 05:59 UTC | May 27, 06:15 UTC | 15m |
| 2026-05-26 | CHH7996 | BKK → PEK | May 26, 17:44 UTC | May 26, 18:40 UTC | 55m |
| 2026-05-26 | CHH7995 | PEK → BKK | May 26, 11:15 UTC | May 26, 15:49 UTC | 4h 35m |
| 2026-05-26 | CHH7238 | XIY → PEK | May 26, 07:34 UTC | May 26, 08:04 UTC | 30m |
| 2026-05-26 | CHH7237 | PEK → XIY | May 26, 03:30 UTC | May 26, 03:45 UTC | 15m |
| 2026-05-25 | CHH7116 | NKG → HAK | May 25, 01:55 UTC | May 25, 06:50 UTC | 4h 55m |
| 2026-05-22 | CHH430 | BKK → PEK | May 22, 06:50 UTC | May 22, 07:50 UTC | 1h 0m |
| 2026-05-22 | CHH429 | PEK → BKK | May 22, 00:25 UTC | May 22, 05:05 UTC | 4h 40m |
| 2026-05-21 | CHH7052 | HGH → HAK | May 21, 01:25 UTC | May 21, 05:55 UTC | 4h 30m |
| 2026-05-20 | CHH7119 | HAK → PVG | May 20, 05:35 UTC | May 21, 01:35 UTC | 20h 0m |
| 2026-05-17 | CHH7688 | NGB → HAK | May 17, 23:45 UTC | May 18, 10:15 UTC | 10h 30m |
| 2026-05-17 | CHH7688 | NGB → HAK | May 17, 13:05 UTC | May 18, 10:15 UTC | 21h 10m |
| 2026-05-17 | CHH7119 | HAK → PVG | May 17, 07:40 UTC | May 17, 23:55 UTC | 16h 15m |
| 2026-05-16 | CHH7216 | NKG → HAK | May 16, 09:10 UTC | May 17, 08:50 UTC | 23h 40m |
| 2026-05-06 | CHH7567 | PEK → CKG | May 6, 11:15 UTC | May 6, 11:25 UTC | 10m |
| 2026-05-01 | CHH7567 | PEK → CKG | May 1, 11:25 UTC | May 1, 11:35 UTC | 10m |
| 2026-04-30 | CHH7557 | SZX → CKG | Apr 30, 14:30 UTC | Apr 30, 14:40 UTC | 10m |
| 2026-04-30 | CHH7744 | SZX → LIY | Apr 30, 12:35 UTC | Apr 30, 13:00 UTC | 25m |
| 2026-04-29 | CHH7743 | NGB → CGQ | Apr 29, 23:05 UTC | Apr 29, 23:15 UTC | 10m |
| 2026-04-29 | CHH7311 | SYX → KHN | Apr 29, 01:40 UTC | Apr 29, 12:45 UTC | 11h 6m |
| 2026-04-28 | CHH7579 | PEK → SYX | Apr 28, 13:25 UTC | Apr 29, 12:45 UTC | 23h 21m |
| 2026-04-28 | CHH7187 | PEK → WUH | Apr 28, 00:45 UTC | Apr 28, 00:55 UTC | 10m |
| 2026-04-26 | CHH7188 | WUH → PEK | Apr 26, 12:35 UTC | Apr 26, 12:45 UTC | 10m |
| 2026-04-25 | CHH7996 | BKK → PEK | Apr 25, 17:50 UTC | Apr 25, 18:10 UTC | 20m |
| 2026-04-25 | CHH7995 | PEK → BKK | Apr 25, 11:15 UTC | Apr 25, 15:40 UTC | 4h 25m |
| 2026-04-24 | CHH7577 | PEK → HGH | Apr 24, 23:15 UTC | Apr 24, 23:25 UTC | 10m |
| 2026-04-24 | CHH7187 | PEK → WUH | Apr 24, 00:55 UTC | Apr 24, 01:20 UTC | 25m |
| 2026-04-23 | CHH7996 | BKK → PEK | Apr 23, 17:45 UTC | Apr 23, 18:45 UTC | 1h 0m |
| 2026-04-23 | CHH7995 | PEK → BKK | Apr 23, 11:10 UTC | Apr 23, 15:55 UTC | 4h 45m |
| 2026-04-23 | CHH7190 | KWE → PEK | Apr 23, 07:20 UTC | Apr 23, 07:35 UTC | 15m |
| 2026-04-23 | CHH7189 | PEK → KWE | Apr 23, 00:40 UTC | Apr 23, 01:05 UTC | 25m |
| 2026-04-21 | CHH7367 | - | Apr 21, 13:50 UTC | Apr 21, 14:01 UTC | 10m |
| 2026-04-21 | CHH7235 | CAN → CGO | Apr 21, 03:15 UTC | Apr 21, 03:25 UTC | 10m |
| 2026-04-20 | CHH7397 | - | Apr 20, 15:05 UTC | Apr 20, 15:15 UTC | 10m |
| 2026-04-20 | CHH7772 | - | Apr 20, 12:25 UTC | Apr 20, 12:35 UTC | 10m |
| 2026-04-20 | CHH7771 | - | Apr 20, 08:30 UTC | Apr 20, 08:40 UTC | 10m |
| 2026-04-20 | CHH7176 | TFU → SZX | Apr 20, 05:40 UTC | Apr 20, 05:50 UTC | 10m |
| 2026-04-20 | CHH7175 | SZX → TFU | Apr 20, 00:10 UTC | Apr 20, 00:20 UTC | 10m |
| 2026-04-19 | CHH7256 | - | Apr 19, 15:25 UTC | Apr 19, 15:50 UTC | 25m |
| 2026-04-19 | - | - | Apr 19, 14:45 UTC | Apr 19, 14:55 UTC | 10m |
| 2026-04-19 | CHH7156 | NKG → SZX | Apr 19, 08:00 UTC | Apr 19, 08:25 UTC | 25m |
| 2026-04-19 | CHH7398 | HGH → SZX | Apr 19, 00:20 UTC | Apr 19, 00:35 UTC | 15m |
| 2026-04-18 | CHH430 | BKK → PEK | Apr 18, 11:10 UTC | Apr 18, 11:20 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-228E page for operator, model, and routing details .