sensors Mode-S transponder
780688
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5540 · BOEING 737-800
- Hex
- 780688
- Octal
- 36003210
- Decimal
- 7,865,992
- Country
- CN
- Tail
- B-5540
- Type
- B738
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 780688 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 |
|---|---|---|---|
| CHH7648 | Hainan Airlines | 4 | 2026-05-25 |
| CHH7987 | Hainan Airlines | 3 | 2026-04-27 |
| CHH7988 | Hainan Airlines | 2 | 2026-04-27 |
| CHH7982 | Hainan Airlines | 2 | 2026-05-30 |
| CHH7735 | Hainan Airlines | 2 | 2026-04-15 |
| CHH7672 | - | 2 | 2026-05-04 |
| CHH7981 | Hainan Airlines | 1 | 2026-05-30 |
| CHH7889 | Hainan Airlines | 1 | 2026-04-19 |
| CHH7778 | Hainan Airlines | 1 | 2026-04-26 |
| CHH7774 | Hainan Airlines | 1 | 2026-04-14 |
| CHH7773 | - | 1 | 2026-04-14 |
| CHH7748 | - | 1 | 2026-04-15 |
| CHH7747 | Hainan Airlines | 1 | 2026-04-15 |
| CHH7732 | - | 1 | 2026-04-14 |
| CHH7674 | - | 1 | 2026-05-26 |
| CHH7673 | - | 1 | 2026-05-26 |
| CHH7671 | - | 1 | 2026-05-02 |
| CHH7638 | Hainan Airlines | 1 | 2026-05-21 |
| CHH7582 | Hainan Airlines | 1 | 2026-05-27 |
| CHH7569 | Hainan Airlines | 1 | 2026-05-01 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CHH7982 | TPE → CAN | May 30, 05:05 UTC | May 30, 05:20 UTC | 15m |
| 2026-05-30 | CHH7982 | TPE → CAN | May 30, 04:05 UTC | May 30, 04:35 UTC | 30m |
| 2026-05-30 | CHH7981 | CAN → TPE | May 30, 00:25 UTC | May 30, 01:50 UTC | 1h 25m |
| 2026-05-27 | CHH7582 | PEK → HAK | May 27, 08:35 UTC | May 27, 11:25 UTC | 2h 50m |
| 2026-05-27 | CHH7136 | CSX → PEK | May 27, 05:29 UTC | May 27, 05:45 UTC | 15m |
| 2026-05-26 | CHH7135 | PEK → CSX | May 26, 23:25 UTC | May 26, 23:45 UTC | 20m |
| 2026-05-26 | CHH7674 | - | May 26, 14:24 UTC | May 26, 14:45 UTC | 20m |
| 2026-05-26 | CHH7673 | - | May 26, 09:35 UTC | May 26, 09:45 UTC | 10m |
| 2026-05-25 | CHH7648 | SHE → HAK | May 25, 11:15 UTC | May 25, 11:40 UTC | 25m |
| 2026-05-21 | CHH7638 | ZUH → CGO | May 21, 07:50 UTC | May 21, 08:05 UTC | 15m |
| 2026-05-09 | CHH7310 | CAN → SYX | May 9, 15:20 UTC | May 9, 15:30 UTC | 10m |
| 2026-05-04 | CHH7672 | - | May 4, 15:10 UTC | May 4, 15:30 UTC | 20m |
| 2026-05-03 | CHH7672 | - | May 3, 14:55 UTC | May 4, 07:25 UTC | 16h 30m |
| 2026-05-02 | CHH7671 | - | May 2, 13:30 UTC | May 3, 07:15 UTC | 17h 44m |
| 2026-05-01 | CHH7569 | XIY → SHE | May 1, 02:40 UTC | May 1, 02:50 UTC | 10m |
| 2026-04-30 | CHH7512 | ZUH → XIY | Apr 30, 04:00 UTC | Apr 30, 04:10 UTC | 10m |
| 2026-04-29 | CHH7337 | PEK → XIY | Apr 29, 14:15 UTC | Apr 29, 14:35 UTC | 20m |
| 2026-04-29 | CHH7247 | PEK → TFU | Apr 29, 05:09 UTC | Apr 29, 05:25 UTC | 15m |
| 2026-04-28 | CHH7079 | PEK → SYX | Apr 28, 00:45 UTC | Apr 28, 00:55 UTC | 10m |
| 2026-04-27 | CHH7134 | - | Apr 27, 16:30 UTC | Apr 27, 16:45 UTC | 15m |
| 2026-04-27 | CHH7133 | - | Apr 27, 12:10 UTC | Apr 27, 12:30 UTC | 20m |
| 2026-04-27 | CHH7988 | TPE → PEK | Apr 27, 05:15 UTC | Apr 27, 05:40 UTC | 25m |
| 2026-04-27 | CHH7987 | PEK → TPE | Apr 27, 02:05 UTC | Apr 27, 02:35 UTC | 30m |
| 2026-04-26 | CHH7987 | PEK → TPE | Apr 26, 23:55 UTC | Apr 27, 00:05 UTC | 10m |
| 2026-04-26 | CHH7778 | BAR → PEK | Apr 26, 14:20 UTC | Apr 26, 14:30 UTC | 10m |
| 2026-04-26 | CHH7138 | XIY → PEK | Apr 26, 04:00 UTC | Apr 26, 04:20 UTC | 20m |
| 2026-04-23 | CHH7237 | PEK → XIY | Apr 23, 03:15 UTC | Apr 23, 03:35 UTC | 20m |
| 2026-04-22 | CHH6394 | - | Apr 22, 14:05 UTC | Apr 22, 14:20 UTC | 15m |
| 2026-04-21 | CHH7648 | SHE → HAK | Apr 21, 11:35 UTC | Apr 22, 05:01 UTC | 17h 25m |
| 2026-04-21 | CHH7648 | SHE → HAK | Apr 21, 08:00 UTC | Apr 22, 05:01 UTC | 21h 0m |
| 2026-04-20 | CHH7648 | SHE → HAK | Apr 20, 12:15 UTC | Apr 21, 12:01 UTC | 23h 46m |
| 2026-04-20 | CHH7146 | URC → PEK | Apr 20, 08:50 UTC | Apr 20, 09:10 UTC | 20m |
| 2026-04-19 | CHH7145 | PEK → URC | Apr 19, 23:45 UTC | Apr 20, 00:00 UTC | 15m |
| 2026-04-19 | CHH7889 | PEK → YZY | Apr 19, 12:00 UTC | Apr 19, 12:15 UTC | 15m |
| 2026-04-19 | CHH7988 | TPE → PEK | Apr 19, 05:15 UTC | Apr 19, 05:35 UTC | 20m |
| 2026-04-19 | CHH7987 | PEK → TPE | Apr 19, 02:25 UTC | Apr 19, 02:50 UTC | 25m |
| 2026-04-17 | CHH7120 | PVG → HAK | Apr 17, 11:40 UTC | Apr 17, 12:00 UTC | 20m |
| 2026-04-17 | CHH7119 | HAK → PVG | Apr 17, 05:20 UTC | Apr 17, 06:15 UTC | 55m |
| 2026-04-16 | CHH7028 | SZX → HAK | Apr 16, 15:15 UTC | Apr 16, 15:30 UTC | 15m |
| 2026-04-15 | CHH7735 | SZX → CGO | Apr 15, 22:35 UTC | Apr 15, 22:45 UTC | 10m |
| 2026-04-15 | CHH7748 | - | Apr 15, 17:05 UTC | Apr 15, 17:25 UTC | 20m |
| 2026-04-15 | CHH7747 | SZX → TYN | Apr 15, 09:20 UTC | Apr 15, 09:40 UTC | 20m |
| 2026-04-14 | CHH7735 | SZX → CGO | Apr 14, 22:25 UTC | Apr 14, 22:35 UTC | 10m |
| 2026-04-14 | CHH7774 | KWE → SZX | Apr 14, 16:20 UTC | Apr 14, 16:30 UTC | 10m |
| 2026-04-14 | CHH7773 | - | Apr 14, 12:05 UTC | Apr 14, 12:15 UTC | 10m |
| 2026-04-14 | CHH7732 | - | Apr 14, 10:35 UTC | Apr 14, 10:45 UTC | 10m |
| 2026-04-13 | CHH7078 | - | Apr 13, 09:45 UTC | Apr 13, 10:05 UTC | 20m |
| 2026-04-13 | CHH7077 | - | Apr 13, 06:35 UTC | Apr 13, 06:50 UTC | 15m |
| 2026-04-13 | CHH7370 | - | Apr 13, 00:40 UTC | Apr 13, 03:55 UTC | 3h 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-5540 page for operator, model, and routing details .