sensors Mode-S transponder
780DD4
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1793 · BOEING 737-800
- Hex
- 780DD4
- Octal
- 36006724
- Decimal
- 7,867,860
- Country
- CN
- Tail
- B-1793
- Type
- B738
- Flights observed
- 46
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 780DD4 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 |
|---|---|---|---|
| CHH7209 | Hainan Airlines | 8 | 2026-05-05 |
| CHH7061 | Hainan Airlines | 6 | 2026-06-06 |
| CHH7308 | Hainan Airlines | 4 | 2026-05-11 |
| CHH7528 | Hainan Airlines | 3 | 2026-05-02 |
| CHH7374 | Hainan Airlines | 3 | 2026-04-27 |
| CHH7668 | Hainan Airlines | 2 | 2026-04-25 |
| CHH7094 | Hainan Airlines | 2 | 2026-05-31 |
| CHH7048 | - | 2 | 2026-06-05 |
| CHH7807 | Hainan Airlines | 1 | 2026-05-30 |
| CHH7750 | Hainan Airlines | 1 | 2026-05-14 |
| CHH7749 | Hainan Airlines | 1 | 2026-05-13 |
| CHH7744 | Hainan Airlines | 1 | 2026-05-14 |
| CHH7743 | Hainan Airlines | 1 | 2026-05-13 |
| CHH7373 | Hainan Airlines | 1 | 2026-05-17 |
| CHH7326 | Hainan Airlines | 1 | 2026-06-02 |
| CHH7312 | Hainan Airlines | 1 | 2026-05-01 |
| CHH7310 | Hainan Airlines | 1 | 2026-05-15 |
| CHH7306 | Hainan Airlines | 1 | 2026-05-07 |
| CHH7216 | Hainan Airlines | 1 | 2026-05-10 |
| CHH7047 | - | 1 | 2026-06-04 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | CHH7061 | HAK → HGH | Jun 6, 14:45 UTC | Jun 7, 06:10 UTC | 15h 25m |
| 2026-06-06 | CHH7061 | HAK → HGH | Jun 6, 06:20 UTC | Jun 6, 14:50 UTC | 8h 30m |
| 2026-06-05 | CHH7061 | HAK → HGH | Jun 5, 14:10 UTC | Jun 6, 06:35 UTC | 16h 25m |
| 2026-06-05 | CHH7048 | - | Jun 5, 08:15 UTC | Jun 6, 06:35 UTC | 22h 20m |
| 2026-06-04 | CHH7048 | - | Jun 4, 12:25 UTC | Jun 5, 00:15 UTC | 11h 50m |
| 2026-06-04 | CHH7047 | - | Jun 4, 00:05 UTC | Jun 4, 08:15 UTC | 8h 10m |
| 2026-06-03 | CHH7010 | CAN → HAK | Jun 3, 13:05 UTC | Jun 3, 13:20 UTC | 15m |
| 2026-06-02 | CHH7326 | WMT → SYX | Jun 2, 05:55 UTC | Jun 2, 06:15 UTC | 20m |
| 2026-06-01 | CHH6032 | ZUH → SYX | Jun 1, 15:05 UTC | Jun 2, 01:15 UTC | 10h 10m |
| 2026-06-01 | CHH7045 | ZUH → TYN | Jun 1, 05:15 UTC | Jun 1, 05:30 UTC | 15m |
| 2026-05-31 | CHH7094 | KMG → HAK | May 31, 10:15 UTC | May 31, 10:25 UTC | 10m |
| 2026-05-30 | CHH7807 | PEK → CAN | May 30, 04:55 UTC | May 30, 05:05 UTC | 10m |
| 2026-05-29 | CHH7094 | KMG → HAK | May 29, 10:30 UTC | May 29, 10:40 UTC | 10m |
| 2026-05-28 | CHH7061 | HAK → HGH | May 28, 06:15 UTC | May 28, 06:35 UTC | 20m |
| 2026-05-27 | CHH7061 | HAK → HGH | May 27, 05:59 UTC | May 27, 14:55 UTC | 8h 55m |
| 2026-05-26 | CHH7061 | HAK → HGH | May 26, 05:59 UTC | May 26, 06:14 UTC | 15m |
| 2026-05-17 | CHH7373 | SYX → HFE | May 17, 02:15 UTC | May 17, 13:50 UTC | 11h 36m |
| 2026-05-15 | CHH7310 | CAN → SYX | May 15, 15:45 UTC | May 15, 16:00 UTC | 15m |
| 2026-05-14 | CHH7750 | SZX → SYX | May 14, 16:15 UTC | May 14, 16:30 UTC | 15m |
| 2026-05-14 | CHH7744 | SZX → LIY | May 14, 14:05 UTC | May 14, 14:25 UTC | 20m |
| 2026-05-13 | CHH7743 | NGB → CGQ | May 13, 23:10 UTC | May 13, 23:20 UTC | 10m |
| 2026-05-13 | CHH7749 | SYX → SZX | May 13, 16:15 UTC | May 13, 16:25 UTC | 10m |
| 2026-05-11 | CHH7308 | CAN → SYX | May 11, 00:15 UTC | May 11, 00:25 UTC | 10m |
| 2026-05-10 | CHH7216 | NKG → HAK | May 10, 04:34 UTC | May 10, 09:35 UTC | 5h 0m |
| 2026-05-08 | CHH7012 | CAN → HAK | May 8, 15:20 UTC | May 8, 15:30 UTC | 10m |
| 2026-05-07 | CHH7306 | TFU → SYX | May 7, 01:05 UTC | May 7, 16:00 UTC | 14h 56m |
| 2026-05-05 | CHH7209 | TNA → HRB | May 5, 15:15 UTC | May 6, 09:50 UTC | 18h 35m |
| 2026-05-04 | CHH7209 | TNA → HRB | May 4, 15:20 UTC | May 5, 09:50 UTC | 18h 31m |
| 2026-05-04 | CHH7209 | TNA → HRB | May 4, 09:30 UTC | May 5, 04:25 UTC | 18h 56m |
| 2026-05-04 | CHH7209 | TNA → HRB | May 4, 04:00 UTC | May 4, 15:25 UTC | 11h 25m |
| 2026-05-03 | CHH7209 | TNA → HRB | May 3, 10:35 UTC | May 4, 04:24 UTC | 17h 50m |
| 2026-05-03 | CHH7209 | TNA → HRB | May 3, 06:20 UTC | May 4, 04:24 UTC | 22h 5m |
| 2026-05-02 | CHH7528 | HRB → SYX | May 2, 10:15 UTC | May 3, 06:40 UTC | 20h 24m |
| 2026-05-02 | CHH7528 | HRB → SYX | May 2, 05:10 UTC | May 2, 10:40 UTC | 5h 30m |
| 2026-05-01 | CHH7528 | HRB → SYX | May 1, 11:45 UTC | May 2, 10:40 UTC | 22h 55m |
| 2026-05-01 | CHH7312 | KHN → SYX | May 1, 01:35 UTC | May 1, 12:00 UTC | 10h 25m |
| 2026-04-29 | CHH7209 | TNA → HRB | Apr 29, 16:25 UTC | Apr 30, 09:45 UTC | 17h 19m |
| 2026-04-29 | CHH7209 | TNA → HRB | Apr 29, 07:45 UTC | Apr 29, 12:00 UTC | 4h 16m |
| 2026-04-27 | CHH7374 | HFE → SYX | Apr 27, 13:55 UTC | Apr 28, 04:30 UTC | 14h 35m |
| 2026-04-27 | CHH7374 | HFE → SYX | Apr 27, 02:10 UTC | Apr 27, 14:10 UTC | 12h 0m |
| 2026-04-26 | CHH7308 | CAN → SYX | Apr 26, 00:05 UTC | Apr 26, 00:20 UTC | 15m |
| 2026-04-25 | CHH7668 | NGB → SZX | Apr 25, 07:15 UTC | Apr 25, 11:10 UTC | 3h 55m |
| 2026-04-21 | CHH7374 | - | Apr 21, 02:25 UTC | Apr 21, 14:31 UTC | 12h 5m |
| 2026-04-19 | CHH7668 | NGB → SZX | Apr 19, 05:10 UTC | Apr 19, 09:45 UTC | 4h 35m |
| 2026-04-18 | CHH7308 | CAN → SYX | Apr 18, 00:20 UTC | Apr 18, 00:30 UTC | 10m |
| 2026-04-16 | CHH7308 | CAN → SYX | Apr 16, 00:00 UTC | Apr 16, 00:15 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-1793 page for operator, model, and routing details .