sensors Mode-S transponder
780841
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5636 · BOEING 737-800
- Hex
- 780841
- Octal
- 36004101
- Decimal
- 7,866,433
- Country
- CN
- Tail
- B-5636
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 780841 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 |
|---|---|---|---|
| CHH7306 | Hainan Airlines | 5 | 2026-04-27 |
| CHH7078 | Hainan Airlines | 4 | 2026-05-28 |
| CHH7644 | Hainan Airlines | 3 | 2026-05-24 |
| CHH7688 | Hainan Airlines | 2 | 2026-05-02 |
| CHH7384 | Hainan Airlines | 2 | 2026-04-27 |
| CHH7383 | Hainan Airlines | 2 | 2026-04-20 |
| CHH7328 | Hainan Airlines | 2 | 2026-04-23 |
| CHH7872 | Hainan Airlines | 1 | 2026-05-20 |
| CHH7809 | Hainan Airlines | 1 | 2026-05-27 |
| CHH7750 | - | 1 | 2026-04-13 |
| CHH7746 | - | 1 | 2026-04-13 |
| CHH7745 | - | 1 | 2026-04-13 |
| CHH7731 | Hainan Airlines | 1 | 2026-05-18 |
| CHH7569 | Hainan Airlines | 1 | 2026-05-06 |
| CHH7558 | Hainan Airlines | 1 | 2026-04-13 |
| CHH7347 | Hainan Airlines | 1 | 2026-05-26 |
| CHH7327 | Hainan Airlines | 1 | 2026-04-22 |
| CHH7322 | Hainan Airlines | 1 | 2026-05-08 |
| CHH7185 | Hainan Airlines | 1 | 2026-05-26 |
| CHH706 | Hainan Airlines | 1 | 2026-05-28 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | CHH7078 | KHN → HAK | May 28, 09:45 UTC | May 29, 02:35 UTC | 16h 50m |
| 2026-05-28 | CHH7078 | KHN → HAK | May 28, 06:30 UTC | May 29, 02:35 UTC | 20h 5m |
| 2026-05-28 | CHH706 | HKG → HAK | May 28, 02:20 UTC | May 28, 02:30 UTC | 10m |
| 2026-05-28 | CHH705 | HAK → HKG | May 28, 00:20 UTC | May 28, 00:40 UTC | 20m |
| 2026-05-27 | CHH7809 | PEK → CAN | May 27, 06:44 UTC | May 27, 07:00 UTC | 16m |
| 2026-05-26 | CHH7185 | PEK → YIH | May 26, 23:05 UTC | May 26, 23:25 UTC | 20m |
| 2026-05-26 | CHH7347 | PEK → TFU | May 26, 06:44 UTC | May 26, 07:05 UTC | 20m |
| 2026-05-24 | CHH7644 | ZUH → HFE | May 24, 08:15 UTC | May 24, 08:30 UTC | 15m |
| 2026-05-23 | CHH7644 | ZUH → HFE | May 23, 10:45 UTC | May 23, 11:00 UTC | 15m |
| 2026-05-21 | CHH7078 | KHN → HAK | May 21, 07:20 UTC | May 21, 11:10 UTC | 3h 50m |
| 2026-05-20 | CHH7872 | SZX → XIY | May 20, 05:55 UTC | May 20, 06:05 UTC | 10m |
| 2026-05-18 | CHH7731 | SYX → SZX | May 18, 23:40 UTC | May 18, 23:55 UTC | 15m |
| 2026-05-17 | CHH7644 | ZUH → HFE | May 17, 08:20 UTC | May 17, 08:30 UTC | 10m |
| 2026-05-08 | CHH7322 | PVG → SYX | May 8, 23:35 UTC | May 9, 04:40 UTC | 5h 5m |
| 2026-05-06 | CHH7569 | XIY → SHE | May 6, 02:35 UTC | May 6, 02:50 UTC | 15m |
| 2026-05-02 | CHH7688 | NGB → HAK | May 2, 09:40 UTC | May 3, 02:35 UTC | 16h 55m |
| 2026-05-01 | CHH7688 | NGB → HAK | May 1, 23:45 UTC | May 2, 10:00 UTC | 10h 16m |
| 2026-04-30 | CHH7078 | KHN → HAK | Apr 30, 01:15 UTC | Apr 30, 10:05 UTC | 8h 50m |
| 2026-04-28 | CHH7015 | HAK → SZX | Apr 28, 11:35 UTC | Apr 28, 11:50 UTC | 15m |
| 2026-04-27 | CHH7384 | HGH → SYX | Apr 27, 15:35 UTC | Apr 28, 11:50 UTC | 20h 15m |
| 2026-04-27 | CHH7306 | TFU → SYX | Apr 27, 01:55 UTC | Apr 27, 15:50 UTC | 13h 55m |
| 2026-04-24 | CHH7384 | HGH → SYX | Apr 24, 16:05 UTC | Apr 24, 16:25 UTC | 20m |
| 2026-04-23 | CHH7328 | CTU → SZX | Apr 23, 16:20 UTC | Apr 24, 16:15 UTC | 23h 55m |
| 2026-04-23 | CHH7306 | TFU → SYX | Apr 23, 01:00 UTC | Apr 23, 16:35 UTC | 15h 35m |
| 2026-04-22 | CHH7306 | TFU → SYX | Apr 22, 16:20 UTC | Apr 23, 11:50 UTC | 19h 30m |
| 2026-04-22 | CHH7327 | SZX → CTU | Apr 22, 11:25 UTC | Apr 23, 07:05 UTC | 19h 40m |
| 2026-04-22 | CHH7306 | TFU → SYX | Apr 22, 07:00 UTC | Apr 23, 01:00 UTC | 18h 0m |
| 2026-04-22 | CHH7306 | TFU → SYX | Apr 22, 01:05 UTC | Apr 22, 16:25 UTC | 15h 20m |
| 2026-04-20 | CHH7383 | SYX → HGH | Apr 20, 10:30 UTC | Apr 20, 15:25 UTC | 4h 55m |
| 2026-04-18 | CHH7383 | SYX → HGH | Apr 18, 09:55 UTC | Apr 18, 14:45 UTC | 4h 50m |
| 2026-04-15 | CHH7328 | - | Apr 15, 15:05 UTC | Apr 15, 15:15 UTC | 10m |
| 2026-04-13 | CHH7750 | - | Apr 13, 15:35 UTC | Apr 13, 15:50 UTC | 15m |
| 2026-04-13 | CHH7746 | - | Apr 13, 13:55 UTC | Apr 13, 14:15 UTC | 20m |
| 2026-04-13 | CHH7745 | - | Apr 13, 02:25 UTC | Apr 13, 02:35 UTC | 10m |
| 2026-04-13 | CHH7558 | CKG → SZX | Apr 13, 00:40 UTC | Apr 13, 00:50 UTC | 10m |
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-5636 page for operator, model, and routing details .