sensors Mode-S transponder
780F9E
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7846 · BOEING 737-800
- Hex
- 780F9E
- Octal
- 36007636
- Decimal
- 7,868,318
- Country
- CN
- Tail
- B-7846
- Type
- B738
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 780F9E 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 |
|---|---|---|---|
| CXA8792 | - | 4 | 2026-07-08 |
| CXA8791 | - | 4 | 2026-07-08 |
| CXA8781 | - | 4 | 2026-07-07 |
| CXA8790 | - | 2 | 2026-06-22 |
| CXA8387 | - | 2 | 2026-07-07 |
| CXA8230 | - | 2 | 2026-07-01 |
| CXA8229 | - | 2 | 2026-07-01 |
| CXA8060 | - | 2 | 2026-07-17 |
| CXA8828 | Xiamen Airlines | 1 | 2026-06-24 |
| CXA8827 | Xiamen Airlines | 1 | 2026-06-22 |
| CXA8789 | - | 1 | 2026-06-19 |
| CXA8344 | Xiamen Airlines | 1 | 2026-06-22 |
| CXA8343 | - | 1 | 2026-06-24 |
| CXA8342 | - | 1 | 2026-05-15 |
| CXA8311 | - | 1 | 2026-06-25 |
| CXA8221 | - | 1 | 2026-04-18 |
| CXA8096 | Xiamen Airlines | 1 | 2026-04-22 |
| CXA8093 | - | 1 | 2026-07-16 |
| CXA8044 | Xiamen Airlines | 1 | 2026-06-10 |
| CXA8032 | Xiamen Airlines | 1 | 2026-05-26 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CXA8060 | - | Jul 17, 12:40 UTC | Jul 17, 13:15 UTC | 35m |
| 2026-07-16 | CXA8093 | - | Jul 16, 14:55 UTC | Jul 17, 13:15 UTC | 22h 20m |
| 2026-07-10 | - | - | Jul 10, 08:25 UTC | Jul 10, 08:35 UTC | 10m |
| 2026-07-08 | CXA8792 | - | Jul 8, 14:40 UTC | Jul 8, 14:55 UTC | 15m |
| 2026-07-08 | CXA8791 | - | Jul 8, 12:35 UTC | Jul 8, 13:25 UTC | 50m |
| 2026-07-07 | CXA8387 | - | Jul 7, 23:30 UTC | Jul 8, 05:30 UTC | 6h 0m |
| 2026-07-07 | CXA8781 | - | Jul 7, 04:00 UTC | Jul 7, 23:45 UTC | 19h 45m |
| 2026-07-06 | CXA8781 | - | Jul 6, 23:50 UTC | Jul 7, 23:30 UTC | 23h 40m |
| 2026-07-06 | CXA8781 | - | Jul 6, 09:40 UTC | Jul 7, 04:45 UTC | 19h 5m |
| 2026-07-06 | CXA8781 | - | Jul 6, 09:10 UTC | Jul 7, 04:45 UTC | 19h 35m |
| 2026-07-01 | CXA8230 | - | Jul 1, 12:15 UTC | Jul 1, 12:35 UTC | 20m |
| 2026-07-01 | CXA8229 | - | Jul 1, 04:30 UTC | Jul 1, 04:50 UTC | 20m |
| 2026-06-28 | CXA8230 | - | Jun 28, 12:19 UTC | Jun 28, 12:39 UTC | 20m |
| 2026-06-28 | CXA8229 | - | Jun 28, 03:45 UTC | Jun 28, 03:59 UTC | 15m |
| 2026-06-25 | CXA8311 | - | Jun 25, 13:29 UTC | Jun 25, 13:40 UTC | 10m |
| 2026-06-24 | CXA8828 | ZUH → XMN | Jun 24, 14:00 UTC | Jun 24, 14:09 UTC | 10m |
| 2026-06-24 | CXA8343 | - | Jun 24, 12:04 UTC | Jun 24, 12:30 UTC | 25m |
| 2026-06-22 | CXA8344 | SZX → HGH | Jun 22, 14:10 UTC | Jun 22, 14:19 UTC | 10m |
| 2026-06-22 | CXA8827 | XMN → ZUH | Jun 22, 12:44 UTC | Jun 22, 13:05 UTC | 20m |
| 2026-06-22 | CXA8790 | - | Jun 22, 02:25 UTC | Jun 22, 02:45 UTC | 20m |
| 2026-06-19 | CXA8789 | - | Jun 19, 13:54 UTC | Jun 19, 14:19 UTC | 25m |
| 2026-06-10 | CXA8044 | CGQ → HGH | Jun 10, 06:25 UTC | Jun 10, 07:15 UTC | 50m |
| 2026-06-08 | CXA8790 | - | Jun 8, 14:05 UTC | Jun 9, 08:50 UTC | 18h 45m |
| 2026-06-07 | CXA8060 | SHE → HGH | Jun 7, 10:45 UTC | Jun 7, 11:15 UTC | 30m |
| 2026-06-04 | - | - | Jun 4, 10:05 UTC | Jun 4, 10:20 UTC | 15m |
| 2026-05-26 | CXA8032 | SHE → XMN | May 26, 05:25 UTC | May 26, 07:55 UTC | 2h 30m |
| 2026-05-15 | CXA8342 | - | May 15, 05:45 UTC | May 15, 09:20 UTC | 3h 35m |
| 2026-05-04 | CXA8792 | HAK → FOC | May 4, 13:05 UTC | May 4, 13:15 UTC | 10m |
| 2026-05-04 | CXA8791 | FOC → HAK | May 4, 11:25 UTC | May 4, 11:35 UTC | 10m |
| 2026-05-01 | CXA8792 | HAK → FOC | May 1, 13:00 UTC | May 1, 13:10 UTC | 10m |
| 2026-05-01 | CXA8791 | FOC → HAK | May 1, 11:05 UTC | May 1, 11:30 UTC | 25m |
| 2026-04-30 | CXA8792 | HAK → FOC | Apr 30, 14:25 UTC | Apr 30, 14:35 UTC | 10m |
| 2026-04-30 | CXA8791 | FOC → HAK | Apr 30, 11:20 UTC | Apr 30, 11:35 UTC | 15m |
| 2026-04-30 | CXA8387 | HGH → SZX | Apr 30, 04:45 UTC | Apr 30, 05:00 UTC | 15m |
| 2026-04-24 | CXA8027 | YCU → CGQ | Apr 24, 08:30 UTC | Apr 24, 08:45 UTC | 15m |
| 2026-04-22 | CXA8096 | SHE → PVG | Apr 22, 09:35 UTC | Apr 22, 10:05 UTC | 30m |
| 2026-04-18 | CXA8221 | - | Apr 18, 05:50 UTC | Apr 18, 06:00 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-7846 page for operator, model, and routing details .