sensors Mode-S transponder
780DD0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1503 · BOEING 737-800
- Hex
- 780DD0
- Octal
- 36006720
- Decimal
- 7,867,856
- Country
- CN
- Tail
- B-1503
- Type
- B738
- Flights observed
- 66
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 780DD0 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CHH7374 | Hainan Airlines | 25 | 2026-05-15 |
| CHH7373 | Hainan Airlines | 17 | 2026-05-16 |
| CHH7750 | Hainan Airlines | 3 | 2026-06-01 |
| CHH7749 | Hainan Airlines | 3 | 2026-05-29 |
| CHH7744 | Hainan Airlines | 3 | 2026-05-30 |
| CHH7743 | Hainan Airlines | 2 | 2026-05-29 |
| CHH7668 | Hainan Airlines | 2 | 2026-04-24 |
| CHH7312 | Hainan Airlines | 2 | 2026-05-29 |
| CHH7735 | Hainan Airlines | 1 | 2026-05-31 |
| CHH7562 | Hainan Airlines | 1 | 2026-06-02 |
| CHH7275 | Hainan Airlines | 1 | 2026-06-01 |
| CHH7256 | Hainan Airlines | 1 | 2026-05-31 |
| CHH7255 | Hainan Airlines | 1 | 2026-05-31 |
| CHH7210 | Hainan Airlines | 1 | 2026-04-27 |
| CHH7209 | Hainan Airlines | 1 | 2026-04-27 |
| CHH7175 | Hainan Airlines | 1 | 2026-05-31 |
| CHH7044 | Hainan Airlines | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | CHH7562 | CGO → SYX | Jun 2, 02:35 UTC | Jun 2, 14:40 UTC | 12h 5m |
| 2026-06-01 | CHH7750 | SZX → SYX | Jun 1, 15:25 UTC | Jun 1, 15:40 UTC | 15m |
| 2026-06-01 | CHH7275 | SZX → TFU | Jun 1, 07:30 UTC | Jun 1, 07:40 UTC | 10m |
| 2026-05-31 | CHH7735 | SZX → CGO | May 31, 22:35 UTC | May 31, 22:45 UTC | 10m |
| 2026-05-31 | CHH7256 | NKG → SZX | May 31, 15:15 UTC | May 31, 15:40 UTC | 25m |
| 2026-05-31 | CHH7255 | SZX → NKG | May 31, 10:15 UTC | May 31, 10:30 UTC | 15m |
| 2026-05-31 | CHH7175 | SZX → TFU | May 31, 00:15 UTC | May 31, 00:30 UTC | 15m |
| 2026-05-30 | CHH7744 | SZX → LIY | May 30, 13:15 UTC | May 30, 13:35 UTC | 20m |
| 2026-05-29 | CHH7743 | NGB → CGQ | May 29, 23:10 UTC | May 29, 23:20 UTC | 10m |
| 2026-05-29 | CHH7749 | SYX → SZX | May 29, 18:45 UTC | May 29, 19:10 UTC | 25m |
| 2026-05-29 | CHH7312 | KHN → SYX | May 29, 01:40 UTC | May 29, 12:15 UTC | 10h 35m |
| 2026-05-25 | CHH7044 | TNA → HAK | May 25, 02:20 UTC | May 25, 08:00 UTC | 5h 40m |
| 2026-05-20 | CHH7750 | SZX → SYX | May 20, 20:15 UTC | May 20, 20:25 UTC | 10m |
| 2026-05-20 | CHH7744 | SZX → LIY | May 20, 18:30 UTC | May 20, 18:45 UTC | 15m |
| 2026-05-19 | CHH7749 | SYX → SZX | May 19, 17:00 UTC | May 19, 17:15 UTC | 15m |
| 2026-05-16 | CHH7373 | SYX → HFE | May 16, 02:30 UTC | May 16, 13:55 UTC | 11h 26m |
| 2026-05-15 | CHH7373 | SYX → HFE | May 15, 13:40 UTC | May 16, 02:45 UTC | 13h 4m |
| 2026-05-15 | CHH7374 | HFE → SYX | May 15, 02:25 UTC | May 15, 13:50 UTC | 11h 25m |
| 2026-05-13 | CHH7374 | HFE → SYX | May 13, 02:15 UTC | May 13, 14:00 UTC | 11h 45m |
| 2026-05-10 | CHH7750 | SZX → SYX | May 10, 15:09 UTC | May 10, 15:24 UTC | 15m |
| 2026-05-10 | CHH7744 | SZX → LIY | May 10, 12:34 UTC | May 10, 12:59 UTC | 25m |
| 2026-05-09 | CHH7743 | NGB → CGQ | May 9, 23:50 UTC | May 10, 00:00 UTC | 10m |
| 2026-05-09 | CHH7749 | SYX → SZX | May 9, 16:00 UTC | May 9, 16:15 UTC | 15m |
| 2026-05-09 | CHH7312 | KHN → SYX | May 9, 01:45 UTC | May 9, 12:00 UTC | 10h 15m |
| 2026-05-08 | CHH7374 | HFE → SYX | May 8, 13:40 UTC | May 9, 12:00 UTC | 22h 20m |
| 2026-05-08 | CHH7374 | HFE → SYX | May 8, 02:09 UTC | May 9, 01:50 UTC | 23h 40m |
| 2026-05-07 | CHH7374 | HFE → SYX | May 7, 13:35 UTC | May 8, 02:14 UTC | 12h 39m |
| 2026-05-07 | CHH7374 | HFE → SYX | May 7, 02:30 UTC | May 7, 13:55 UTC | 11h 25m |
| 2026-05-06 | CHH7374 | HFE → SYX | May 6, 13:50 UTC | May 7, 02:30 UTC | 12h 39m |
| 2026-05-06 | CHH7373 | SYX → HFE | May 6, 02:10 UTC | May 6, 14:00 UTC | 11h 50m |
| 2026-05-05 | CHH7374 | HFE → SYX | May 5, 13:40 UTC | May 6, 02:20 UTC | 12h 40m |
| 2026-05-05 | CHH7374 | HFE → SYX | May 5, 02:10 UTC | May 5, 13:55 UTC | 11h 45m |
| 2026-05-04 | CHH7374 | HFE → SYX | May 4, 14:05 UTC | May 5, 13:55 UTC | 23h 51m |
| 2026-05-04 | CHH7374 | HFE → SYX | May 4, 13:50 UTC | May 5, 02:10 UTC | 12h 21m |
| 2026-05-04 | CHH7374 | HFE → SYX | May 4, 01:50 UTC | May 4, 14:10 UTC | 12h 20m |
| 2026-05-03 | CHH7374 | HFE → SYX | May 3, 14:05 UTC | May 4, 14:00 UTC | 23h 55m |
| 2026-05-03 | CHH7373 | SYX → HFE | May 3, 13:50 UTC | May 4, 02:00 UTC | 12h 10m |
| 2026-05-02 | CHH7374 | HFE → SYX | May 2, 14:05 UTC | May 3, 14:00 UTC | 23h 54m |
| 2026-05-02 | CHH7373 | SYX → HFE | May 2, 02:10 UTC | May 2, 14:05 UTC | 11h 55m |
| 2026-05-01 | CHH7374 | HFE → SYX | May 1, 14:05 UTC | May 2, 14:00 UTC | 23h 55m |
| 2026-05-01 | CHH7374 | HFE → SYX | May 1, 02:10 UTC | May 1, 14:15 UTC | 12h 5m |
| 2026-04-30 | CHH7374 | HFE → SYX | Apr 30, 16:10 UTC | May 1, 14:15 UTC | 22h 5m |
| 2026-04-30 | CHH7373 | SYX → HFE | Apr 30, 02:10 UTC | Apr 30, 16:15 UTC | 14h 5m |
| 2026-04-29 | CHH7374 | HFE → SYX | Apr 29, 13:50 UTC | Apr 30, 02:15 UTC | 12h 24m |
| 2026-04-29 | CHH7373 | SYX → HFE | Apr 29, 02:05 UTC | Apr 29, 14:00 UTC | 11h 56m |
| 2026-04-28 | CHH7373 | SYX → HFE | Apr 28, 13:45 UTC | Apr 29, 02:20 UTC | 12h 35m |
| 2026-04-28 | CHH7374 | HFE → SYX | Apr 28, 02:20 UTC | Apr 28, 14:00 UTC | 11h 40m |
| 2026-04-27 | CHH7374 | HFE → SYX | Apr 27, 15:15 UTC | Apr 28, 14:00 UTC | 22h 45m |
| 2026-04-27 | CHH7210 | TNA → CAN | Apr 27, 09:50 UTC | Apr 28, 02:20 UTC | 16h 30m |
| 2026-04-27 | CHH7209 | TNA → HRB | Apr 27, 04:20 UTC | Apr 28, 02:20 UTC | 22h 0m |
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-1503 page for operator, model, and routing details .