sensors Mode-S transponder
780F20
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7197 · BOEING 737-800
- Hex
- 780F20
- Octal
- 36007440
- Decimal
- 7,868,192
- Country
- CN
- Tail
- B-7197
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 780F20 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 |
|---|---|---|---|
| CXA8343 | - | 3 | 2026-07-07 |
| CXA8828 | - | 2 | 2026-07-07 |
| CXA8790 | - | 2 | 2026-05-03 |
| CXA8782 | Xiamen Airlines | 2 | 2026-06-11 |
| CXA8605 | - | 2 | 2026-04-13 |
| CXA8430 | Xiamen Airlines | 2 | 2026-04-13 |
| CXA828 | - | 2 | 2026-07-08 |
| CXA827 | - | 2 | 2026-07-08 |
| CXA8783 | Xiamen Airlines | 1 | 2026-05-17 |
| CXA8781 | Xiamen Airlines | 1 | 2026-06-11 |
| CXA878 | Xiamen Airlines | 1 | 2026-05-11 |
| CXA877 | Xiamen Airlines | 1 | 2026-05-11 |
| CXA8728 | - | 1 | 2026-07-09 |
| CXA8555 | - | 1 | 2026-07-03 |
| CXA8397 | - | 1 | 2026-06-01 |
| CXA8323 | Xiamen Airlines | 1 | 2026-04-18 |
| CXA8230 | - | 1 | 2026-06-23 |
| CXA8229 | - | 1 | 2026-06-23 |
| CXA8222 | - | 1 | 2026-07-13 |
| CXA8221 | - | 1 | 2026-07-13 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CXA8221 | - | Jul 13, 05:35 UTC | Jul 13, 05:45 UTC | 10m |
| 2026-07-13 | CXA8222 | - | Jul 13, 03:55 UTC | Jul 13, 04:05 UTC | 10m |
| 2026-07-09 | CXA8728 | - | Jul 9, 10:30 UTC | Jul 9, 11:35 UTC | 1h 5m |
| 2026-07-08 | CXA828 | - | Jul 8, 04:35 UTC | Jul 8, 14:40 UTC | 10h 5m |
| 2026-07-08 | CXA827 | - | Jul 8, 02:00 UTC | Jul 8, 02:35 UTC | 35m |
| 2026-07-07 | CXA8828 | - | Jul 7, 15:25 UTC | Jul 7, 15:35 UTC | 10m |
| 2026-07-07 | CXA8343 | - | Jul 7, 13:55 UTC | Jul 7, 14:10 UTC | 15m |
| 2026-07-07 | CXA8343 | - | Jul 7, 13:10 UTC | Jul 7, 13:20 UTC | 10m |
| 2026-07-03 | CXA8555 | - | Jul 3, 01:00 UTC | Jul 3, 15:00 UTC | 14h 0m |
| 2026-07-02 | CXA8093 | - | Jul 2, 14:35 UTC | Jul 3, 10:25 UTC | 19h 50m |
| 2026-07-02 | CXA828 | - | Jul 2, 04:15 UTC | Jul 2, 05:20 UTC | 1h 5m |
| 2026-07-02 | CXA827 | - | Jul 2, 00:55 UTC | Jul 2, 02:10 UTC | 1h 15m |
| 2026-06-25 | CXA8076 | - | Jun 25, 10:25 UTC | Jun 25, 10:39 UTC | 15m |
| 2026-06-23 | CXA8230 | - | Jun 23, 12:20 UTC | Jun 23, 12:40 UTC | 20m |
| 2026-06-23 | CXA8229 | - | Jun 23, 03:34 UTC | Jun 23, 03:54 UTC | 20m |
| 2026-06-21 | CXA8828 | ZUH → XMN | Jun 21, 13:50 UTC | Jun 21, 14:05 UTC | 15m |
| 2026-06-21 | CXA8343 | - | Jun 21, 12:04 UTC | Jun 21, 12:24 UTC | 20m |
| 2026-06-11 | CXA8088 | SHE → HGH | Jun 11, 10:40 UTC | Jun 11, 23:30 UTC | 12h 50m |
| 2026-06-11 | CXA8782 | SYX → FOC | Jun 11, 08:50 UTC | Jun 11, 09:05 UTC | 15m |
| 2026-06-11 | CXA8782 | SYX → FOC | Jun 11, 07:10 UTC | Jun 11, 08:10 UTC | 1h 0m |
| 2026-06-11 | CXA8781 | SHE → FOC | Jun 11, 04:20 UTC | Jun 11, 04:45 UTC | 25m |
| 2026-06-10 | CXA8096 | SHE → PVG | Jun 10, 10:25 UTC | Jun 10, 23:45 UTC | 13h 20m |
| 2026-06-01 | CXA8397 | - | Jun 1, 00:45 UTC | Jun 1, 04:45 UTC | 4h 0m |
| 2026-05-17 | CXA8783 | FOC → HAK | May 17, 11:05 UTC | May 17, 14:25 UTC | 3h 20m |
| 2026-05-11 | CXA878 | ICN → FOC | May 11, 12:00 UTC | May 11, 12:25 UTC | 25m |
| 2026-05-11 | CXA877 | FOC → ICN | May 11, 08:55 UTC | May 11, 09:35 UTC | 40m |
| 2026-05-03 | CXA8790 | - | May 3, 23:35 UTC | May 4, 05:55 UTC | 6h 20m |
| 2026-05-03 | CXA8790 | - | May 3, 07:45 UTC | May 4, 05:55 UTC | 22h 10m |
| 2026-05-02 | CXA820 | MNL → XMN | May 2, 13:20 UTC | May 3, 07:55 UTC | 18h 34m |
| 2026-05-02 | CXA819 | XMN → MNL | May 2, 10:50 UTC | May 2, 11:35 UTC | 45m |
| 2026-04-30 | CXA8023 | CSX → HRB | Apr 30, 09:50 UTC | May 1, 02:20 UTC | 16h 30m |
| 2026-04-29 | CXA8028 | CGQ → YCU | Apr 29, 12:40 UTC | Apr 29, 12:50 UTC | 10m |
| 2026-04-29 | CXA8027 | YCU → CGQ | Apr 29, 08:55 UTC | Apr 29, 09:05 UTC | 11m |
| 2026-04-18 | CXA8323 | FOC → CAN | Apr 18, 03:10 UTC | Apr 18, 03:20 UTC | 10m |
| 2026-04-13 | CXA8605 | - | Apr 13, 12:20 UTC | Apr 13, 15:00 UTC | 2h 40m |
| 2026-04-13 | CXA8605 | - | Apr 13, 11:55 UTC | Apr 13, 12:15 UTC | 20m |
| 2026-04-13 | CXA8430 | KMG → FOC | Apr 13, 07:55 UTC | Apr 13, 08:10 UTC | 15m |
| 2026-04-13 | CXA8430 | KMG → FOC | Apr 13, 07:15 UTC | Apr 13, 08:10 UTC | 55m |
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-7197 page for operator, model, and routing details .