sensors Mode-S transponder
780DD6
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1505 · BOEING 737-800
- Hex
- 780DD6
- Octal
- 36006726
- Decimal
- 7,867,862
- Country
- CN
- Tail
- B-1505
- Type
- B738
- Flights observed
- 46
- Distinct callsigns
- 19
- Country
- CN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 780DD6 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CHH7312 | Hainan Airlines | 8 | 2026-05-30 |
| CHH7374 | Hainan Airlines | 5 | 2026-05-09 |
| CHH7750 | Hainan Airlines | 4 | 2026-06-05 |
| CHH7311 | Hainan Airlines | 4 | 2026-06-04 |
| CHH7749 | Hainan Airlines | 3 | 2026-06-04 |
| CHH7744 | Hainan Airlines | 3 | 2026-06-05 |
| CHH7308 | Hainan Airlines | 3 | 2026-05-07 |
| CHH7668 | Hainan Airlines | 2 | 2026-05-07 |
| CHH7562 | Hainan Airlines | 2 | 2026-06-01 |
| CHH7326 | Hainan Airlines | 2 | 2026-06-07 |
| CHH7304 | Hainan Airlines | 2 | 2026-06-03 |
| CHH7743 | Hainan Airlines | 1 | 2026-06-04 |
| CHH7388 | - | 1 | 2026-06-02 |
| CHH7373 | Hainan Airlines | 1 | 2026-04-23 |
| CHH7370 | - | 1 | 2026-04-28 |
| CHH7310 | Hainan Airlines | 1 | 2026-05-10 |
| CHH7275 | Hainan Airlines | 1 | 2026-04-30 |
| CHH7119 | Hainan Airlines | 1 | 2026-04-29 |
| CHH7012 | Hainan Airlines | 1 | 2026-04-26 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | CHH7326 | WMT → SYX | Jun 7, 05:50 UTC | Jun 7, 06:15 UTC | 25m |
| 2026-06-06 | CHH7326 | WMT → SYX | Jun 6, 05:40 UTC | Jun 6, 06:00 UTC | 20m |
| 2026-06-05 | CHH7750 | SZX → SYX | Jun 5, 15:15 UTC | Jun 5, 15:30 UTC | 15m |
| 2026-06-05 | CHH7744 | SZX → LIY | Jun 5, 13:35 UTC | Jun 5, 13:50 UTC | 15m |
| 2026-06-04 | CHH7743 | NGB → CGQ | Jun 4, 23:50 UTC | Jun 5, 00:05 UTC | 15m |
| 2026-06-04 | CHH7749 | SYX → SZX | Jun 4, 16:40 UTC | Jun 4, 16:55 UTC | 15m |
| 2026-06-04 | CHH7311 | SYX → KHN | Jun 4, 01:30 UTC | Jun 4, 12:45 UTC | 11h 15m |
| 2026-06-03 | CHH7304 | TFU → SYX | Jun 3, 05:40 UTC | Jun 4, 01:40 UTC | 20h 0m |
| 2026-06-03 | CHH7304 | TFU → SYX | Jun 3, 01:00 UTC | Jun 3, 06:05 UTC | 5h 5m |
| 2026-06-02 | CHH7388 | - | Jun 2, 04:00 UTC | Jun 2, 15:05 UTC | 11h 5m |
| 2026-06-01 | CHH7562 | CGO → SYX | Jun 1, 02:50 UTC | Jun 1, 14:35 UTC | 11h 45m |
| 2026-05-31 | CHH7562 | CGO → SYX | May 31, 14:15 UTC | Jun 1, 02:50 UTC | 12h 35m |
| 2026-05-30 | CHH7312 | KHN → SYX | May 30, 01:35 UTC | May 30, 12:30 UTC | 10h 55m |
| 2026-05-29 | CHH7750 | SZX → SYX | May 29, 16:45 UTC | May 29, 17:00 UTC | 15m |
| 2026-05-29 | CHH7744 | SZX → LIY | May 29, 14:45 UTC | May 29, 15:25 UTC | 40m |
| 2026-05-28 | CHH7749 | SYX → SZX | May 28, 16:30 UTC | May 28, 16:50 UTC | 20m |
| 2026-05-28 | CHH7312 | KHN → SYX | May 28, 01:45 UTC | May 28, 13:30 UTC | 11h 45m |
| 2026-05-27 | CHH7312 | KHN → SYX | May 27, 14:05 UTC | May 28, 13:30 UTC | 23h 25m |
| 2026-05-26 | CHH7311 | SYX → KHN | May 26, 01:40 UTC | May 26, 12:05 UTC | 10h 25m |
| 2026-05-25 | CHH7311 | SYX → KHN | May 25, 15:05 UTC | May 26, 12:05 UTC | 20h 59m |
| 2026-05-25 | CHH7311 | SYX → KHN | May 25, 10:35 UTC | May 26, 01:55 UTC | 15h 20m |
| 2026-05-12 | CHH7750 | SZX → SYX | May 12, 15:20 UTC | May 12, 15:35 UTC | 15m |
| 2026-05-12 | CHH7744 | SZX → LIY | May 12, 12:30 UTC | May 12, 12:50 UTC | 20m |
| 2026-05-11 | CHH7749 | SYX → SZX | May 11, 16:05 UTC | May 11, 16:15 UTC | 10m |
| 2026-05-11 | CHH7312 | KHN → SYX | May 11, 01:40 UTC | May 11, 12:00 UTC | 10h 20m |
| 2026-05-10 | CHH7312 | KHN → SYX | May 10, 15:35 UTC | May 11, 12:00 UTC | 20h 25m |
| 2026-05-10 | CHH7310 | CAN → SYX | May 10, 15:19 UTC | May 11, 12:00 UTC | 20h 40m |
| 2026-05-09 | CHH7374 | HFE → SYX | May 9, 02:20 UTC | May 9, 13:50 UTC | 11h 30m |
| 2026-05-07 | CHH7308 | CAN → SYX | May 7, 23:59 UTC | May 8, 00:09 UTC | 10m |
| 2026-05-07 | CHH7668 | NGB → SZX | May 7, 04:45 UTC | May 7, 09:20 UTC | 4h 35m |
| 2026-04-30 | CHH7750 | SZX → SYX | Apr 30, 15:15 UTC | Apr 30, 15:35 UTC | 20m |
| 2026-04-30 | CHH7275 | SZX → TFU | Apr 30, 06:35 UTC | Apr 30, 06:45 UTC | 10m |
| 2026-04-29 | CHH7119 | HAK → PVG | Apr 29, 06:19 UTC | Apr 29, 13:20 UTC | 7h 1m |
| 2026-04-28 | CHH7370 | - | Apr 28, 04:05 UTC | Apr 28, 04:30 UTC | 25m |
| 2026-04-26 | CHH7012 | CAN → HAK | Apr 26, 15:05 UTC | Apr 26, 15:15 UTC | 10m |
| 2026-04-25 | CHH7312 | KHN → SYX | Apr 25, 11:45 UTC | Apr 26, 04:35 UTC | 16h 50m |
| 2026-04-25 | CHH7312 | KHN → SYX | Apr 25, 01:45 UTC | Apr 25, 12:05 UTC | 10h 20m |
| 2026-04-24 | CHH7312 | KHN → SYX | Apr 24, 13:45 UTC | Apr 25, 12:05 UTC | 22h 20m |
| 2026-04-24 | CHH7374 | HFE → SYX | Apr 24, 02:30 UTC | Apr 24, 14:00 UTC | 11h 30m |
| 2026-04-23 | CHH7374 | HFE → SYX | Apr 23, 14:25 UTC | Apr 24, 02:30 UTC | 12h 4m |
| 2026-04-23 | CHH7373 | SYX → HFE | Apr 23, 02:50 UTC | Apr 23, 14:40 UTC | 11h 50m |
| 2026-04-22 | CHH7374 | HFE → SYX | Apr 22, 15:50 UTC | Apr 23, 14:40 UTC | 22h 50m |
| 2026-04-22 | CHH7374 | HFE → SYX | Apr 22, 02:10 UTC | Apr 22, 15:55 UTC | 13h 45m |
| 2026-04-20 | CHH7308 | CAN → SYX | Apr 20, 23:55 UTC | Apr 21, 00:05 UTC | 10m |
| 2026-04-20 | CHH7668 | NGB → SZX | Apr 20, 05:00 UTC | Apr 20, 09:45 UTC | 4h 45m |
| 2026-04-15 | CHH7308 | CAN → SYX | Apr 15, 00:00 UTC | Apr 15, 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-1505 page for operator, model, and routing details .