sensors Mode-S transponder
780817
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5623 · BOEING 737-800
- Hex
- 780817
- Octal
- 36004027
- Decimal
- 7,866,391
- Country
- CN
- Tail
- B-5623
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 780817 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 |
|---|---|---|---|
| CHH7385 | Hainan Airlines | 4 | 2026-05-08 |
| CHH7777 | - | 2 | 2026-06-24 |
| CHH7569 | - | 2 | 2026-06-28 |
| CHH7535 | - | 2 | 2026-07-02 |
| CHH7386 | Hainan Airlines | 2 | 2026-05-07 |
| CHH7320 | Hainan Airlines | 2 | 2026-05-22 |
| CHH7146 | Hainan Airlines | 2 | 2026-05-03 |
| CHH7074 | Hainan Airlines | 2 | 2026-05-05 |
| CHH6218 | Hainan Airlines | 2 | 2026-07-02 |
| CHH7889 | Hainan Airlines | 1 | 2026-05-03 |
| CHH7873 | - | 1 | 2026-06-30 |
| CHH7870 | - | 1 | 2026-06-30 |
| CHH7815 | Hainan Airlines | 1 | 2026-06-06 |
| CHH7801 | Hainan Airlines | 1 | 2026-05-28 |
| CHH7746 | - | 1 | 2026-05-13 |
| CHH7716 | Hainan Airlines | 1 | 2026-05-11 |
| CHH7688 | - | 1 | 2026-06-19 |
| CHH7644 | - | 1 | 2026-06-25 |
| CHH7638 | - | 1 | 2026-06-27 |
| CHH7627 | Hainan Airlines | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CHH7522 | - | Jul 10, 12:35 UTC | Jul 10, 12:50 UTC | 15m |
| 2026-07-07 | CHH7187 | - | Jul 7, 00:45 UTC | Jul 7, 01:00 UTC | 15m |
| 2026-07-02 | CHH7535 | - | Jul 2, 15:20 UTC | Jul 2, 15:40 UTC | 20m |
| 2026-07-02 | CHH6218 | XIY → PEK | Jul 2, 13:05 UTC | Jul 2, 13:30 UTC | 25m |
| 2026-06-30 | CHH7870 | - | Jun 30, 23:45 UTC | Jul 1, 00:00 UTC | 15m |
| 2026-06-30 | CHH7873 | - | Jun 30, 18:00 UTC | Jun 30, 18:10 UTC | 10m |
| 2026-06-29 | CHH7337 | - | Jun 29, 14:29 UTC | Jun 29, 14:50 UTC | 20m |
| 2026-06-28 | CHH7569 | - | Jun 28, 02:25 UTC | Jun 28, 02:44 UTC | 20m |
| 2026-06-27 | CHH7638 | - | Jun 27, 05:49 UTC | Jun 27, 05:59 UTC | 10m |
| 2026-06-25 | CHH7644 | - | Jun 25, 09:40 UTC | Jun 25, 09:50 UTC | 10m |
| 2026-06-25 | CHH7105 | PEK → DLC | Jun 25, 00:05 UTC | Jun 25, 00:14 UTC | 10m |
| 2026-06-24 | CHH7777 | - | Jun 24, 06:15 UTC | Jun 24, 06:39 UTC | 25m |
| 2026-06-23 | CHH7185 | - | Jun 23, 23:05 UTC | Jun 23, 23:24 UTC | 20m |
| 2026-06-23 | CHH6218 | XIY → PEK | Jun 23, 12:35 UTC | Jun 23, 13:05 UTC | 30m |
| 2026-06-22 | CHH7569 | - | Jun 22, 02:30 UTC | Jun 22, 02:40 UTC | 10m |
| 2026-06-21 | CHH7512 | - | Jun 21, 03:49 UTC | Jun 21, 04:04 UTC | 15m |
| 2026-06-19 | CHH7688 | - | Jun 19, 23:54 UTC | Jun 20, 10:09 UTC | 10h 15m |
| 2026-06-13 | CHH7182 | PEK → HAK | Jun 13, 05:20 UTC | Jun 13, 15:50 UTC | 10h 30m |
| 2026-06-12 | CHH7215 | HAK → NKG | Jun 12, 04:35 UTC | Jun 12, 10:05 UTC | 5h 30m |
| 2026-06-11 | CHH7045 | ZUH → TYN | Jun 11, 05:20 UTC | Jun 11, 05:35 UTC | 15m |
| 2026-06-06 | CHH7815 | PEK → CAN | Jun 6, 12:40 UTC | Jun 6, 13:05 UTC | 25m |
| 2026-06-04 | CHH7627 | TSN → NNG | Jun 4, 00:45 UTC | Jun 4, 00:55 UTC | 10m |
| 2026-05-29 | CHH7247 | PEK → TFU | May 29, 05:00 UTC | May 29, 05:20 UTC | 20m |
| 2026-05-28 | CHH7547 | PEK → TFU | May 28, 12:15 UTC | May 28, 12:35 UTC | 20m |
| 2026-05-28 | CHH7801 | PEK → CAN | May 28, 01:20 UTC | May 28, 01:40 UTC | 20m |
| 2026-05-27 | CHH7777 | PEK → BAR | May 27, 06:25 UTC | May 27, 06:40 UTC | 15m |
| 2026-05-26 | CHH7567 | PEK → CKG | May 26, 11:09 UTC | May 26, 11:30 UTC | 20m |
| 2026-05-22 | CHH7320 | PVG → HAK | May 22, 02:30 UTC | May 22, 02:45 UTC | 15m |
| 2026-05-21 | CHH7320 | PVG → HAK | May 21, 02:25 UTC | May 21, 02:40 UTC | 15m |
| 2026-05-15 | CHH7369 | - | May 15, 00:15 UTC | May 15, 03:40 UTC | 3h 25m |
| 2026-05-14 | CHH7026 | SZX → HAK | May 14, 14:40 UTC | May 14, 14:50 UTC | 10m |
| 2026-05-13 | CHH7746 | - | May 13, 16:10 UTC | May 13, 16:30 UTC | 20m |
| 2026-05-11 | CHH7716 | TNA → SZX | May 11, 12:20 UTC | May 11, 12:30 UTC | 10m |
| 2026-05-08 | CHH7385 | SYX → HGH | May 8, 05:44 UTC | May 8, 10:19 UTC | 4h 35m |
| 2026-05-07 | CHH7386 | HGH → SYX | May 7, 09:55 UTC | May 8, 05:59 UTC | 20h 4m |
| 2026-05-07 | CHH7386 | HGH → SYX | May 7, 05:05 UTC | May 7, 10:10 UTC | 5h 5m |
| 2026-05-06 | CHH7385 | SYX → HGH | May 6, 09:50 UTC | May 7, 05:15 UTC | 19h 24m |
| 2026-05-06 | CHH7385 | SYX → HGH | May 6, 09:35 UTC | May 7, 05:15 UTC | 19h 39m |
| 2026-05-06 | CHH7385 | SYX → HGH | May 6, 05:05 UTC | May 6, 09:50 UTC | 4h 45m |
| 2026-05-05 | CHH7074 | HRB → HAK | May 5, 06:50 UTC | May 6, 05:15 UTC | 22h 25m |
| 2026-05-05 | CHH7074 | HRB → HAK | May 5, 02:35 UTC | May 5, 07:10 UTC | 4h 35m |
| 2026-05-04 | CHH7482 | PEK → HAK | May 4, 01:10 UTC | May 4, 01:24 UTC | 15m |
| 2026-05-03 | CHH7889 | PEK → YZY | May 3, 11:55 UTC | May 3, 12:15 UTC | 20m |
| 2026-05-03 | CHH7146 | URC → PEK | May 3, 09:05 UTC | May 3, 09:25 UTC | 20m |
| 2026-05-02 | CHH7145 | PEK → URC | May 2, 23:35 UTC | May 3, 00:01 UTC | 25m |
| 2026-04-27 | CHH7535 | PEK → CSX | Apr 27, 15:10 UTC | Apr 27, 15:25 UTC | 15m |
| 2026-04-27 | CHH7164 | NKG → SZX | Apr 27, 05:10 UTC | Apr 27, 08:50 UTC | 3h 40m |
| 2026-04-26 | CHH7146 | URC → PEK | Apr 26, 08:50 UTC | Apr 26, 09:05 UTC | 15m |
| 2026-04-25 | CHH7290 | KWE → PEK | Apr 25, 13:50 UTC | Apr 25, 14:00 UTC | 10m |
| 2026-04-24 | CHH7028 | SZX → HAK | Apr 24, 17:40 UTC | Apr 24, 17:55 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-5623 page for operator, model, and routing details .