sensors Mode-S transponder
780EAA
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6887 · BOEING 737-800
- Hex
- 780EAA
- Octal
- 36007252
- Decimal
- 7,868,074
- Country
- CN
- Tail
- B-6887
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780EAA 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 |
|---|---|---|---|
| CXA8230 | Xiamen Airlines | 4 | 2026-06-03 |
| CXA8698 | - | 3 | 2026-07-06 |
| CXA8229 | Xiamen Airlines | 3 | 2026-06-03 |
| CXA8697 | - | 2 | 2026-07-06 |
| CXA8359 | Xiamen Airlines | 2 | 2026-05-27 |
| CXA8044 | - | 2 | 2026-07-10 |
| CXA8867 | - | 1 | 2026-07-15 |
| CXA8828 | Xiamen Airlines | 1 | 2026-06-17 |
| CXA8827 | - | 1 | 2026-07-14 |
| CXA8789 | - | 1 | 2026-07-14 |
| CXA8727 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA8605 | Xiamen Airlines | 1 | 2026-04-19 |
| CXA8526 | - | 1 | 2026-05-04 |
| CXA8524 | - | 1 | 2026-06-20 |
| CXA8523 | - | 1 | 2026-07-01 |
| CXA844 | - | 1 | 2026-06-20 |
| CXA843 | - | 1 | 2026-06-20 |
| CXA8426 | - | 1 | 2026-04-14 |
| CXA8405 | - | 1 | 2026-06-05 |
| CXA8388 | Xiamen Airlines | 1 | 2026-05-29 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | CXA8867 | - | Jul 15, 23:55 UTC | Jul 16, 00:30 UTC | 35m |
| 2026-07-14 | CXA8344 | - | Jul 14, 14:25 UTC | Jul 14, 14:35 UTC | 10m |
| 2026-07-14 | CXA8827 | - | Jul 14, 12:40 UTC | Jul 14, 13:00 UTC | 20m |
| 2026-07-14 | CXA8789 | - | Jul 14, 01:45 UTC | Jul 14, 08:10 UTC | 6h 25m |
| 2026-07-10 | CXA8044 | - | Jul 10, 06:40 UTC | Jul 10, 07:20 UTC | 40m |
| 2026-07-07 | CXA8309 | - | Jul 7, 09:20 UTC | Jul 7, 12:20 UTC | 3h 0m |
| 2026-07-06 | CXA8698 | - | Jul 6, 15:00 UTC | Jul 7, 12:20 UTC | 21h 20m |
| 2026-07-06 | CXA8698 | - | Jul 6, 09:45 UTC | Jul 6, 10:00 UTC | 15m |
| 2026-07-06 | CXA8697 | - | Jul 6, 06:35 UTC | Jul 6, 06:50 UTC | 15m |
| 2026-07-03 | CXA8698 | - | Jul 3, 09:45 UTC | Jul 3, 14:15 UTC | 4h 30m |
| 2026-07-03 | CXA8697 | - | Jul 3, 07:30 UTC | Jul 3, 08:05 UTC | 35m |
| 2026-07-01 | CXA8523 | - | Jul 1, 14:30 UTC | Jul 1, 14:45 UTC | 15m |
| 2026-06-20 | CXA844 | - | Jun 20, 19:15 UTC | Jun 20, 21:30 UTC | 2h 15m |
| 2026-06-20 | CXA843 | - | Jun 20, 14:59 UTC | Jun 20, 17:19 UTC | 2h 20m |
| 2026-06-20 | CXA8524 | - | Jun 20, 11:14 UTC | Jun 20, 11:44 UTC | 30m |
| 2026-06-17 | CXA8828 | ZUH → XMN | Jun 17, 16:10 UTC | Jun 17, 16:25 UTC | 15m |
| 2026-06-17 | CXA8343 | - | Jun 17, 13:45 UTC | Jun 17, 14:45 UTC | 1h 0m |
| 2026-06-15 | - | - | Jun 15, 05:30 UTC | Jun 15, 05:40 UTC | 10m |
| 2026-06-09 | CXA818 | - | Jun 9, 10:10 UTC | Jun 9, 11:20 UTC | 1h 10m |
| 2026-06-09 | CXA817 | - | Jun 9, 07:45 UTC | Jun 9, 08:30 UTC | 45m |
| 2026-06-05 | CXA8405 | - | Jun 5, 00:30 UTC | Jun 5, 16:15 UTC | 15h 45m |
| 2026-06-03 | CXA8230 | TSN → HGH | Jun 3, 12:00 UTC | Jun 3, 12:20 UTC | 20m |
| 2026-06-03 | CXA8229 | TSN → URC | Jun 3, 03:50 UTC | Jun 3, 04:10 UTC | 20m |
| 2026-06-02 | CXA8230 | TSN → HGH | Jun 2, 12:10 UTC | Jun 2, 12:40 UTC | 30m |
| 2026-05-30 | CXA8230 | TSN → HGH | May 30, 11:55 UTC | May 30, 12:15 UTC | 20m |
| 2026-05-30 | CXA8229 | TSN → URC | May 30, 03:55 UTC | May 30, 04:15 UTC | 20m |
| 2026-05-29 | CXA8388 | SZX → HGH | May 29, 06:45 UTC | May 29, 06:55 UTC | 10m |
| 2026-05-29 | CXA8387 | HGH → SZX | May 29, 04:40 UTC | May 29, 04:55 UTC | 15m |
| 2026-05-27 | CXA8359 | XMN → NNG | May 27, 00:25 UTC | May 27, 10:25 UTC | 10h 0m |
| 2026-05-19 | CXA8230 | TSN → HGH | May 19, 12:10 UTC | May 19, 12:30 UTC | 20m |
| 2026-05-19 | CXA8229 | TSN → URC | May 19, 03:55 UTC | May 19, 04:15 UTC | 20m |
| 2026-05-07 | CXA8370 | ZUH → HGH | May 7, 02:50 UTC | May 7, 03:00 UTC | 10m |
| 2026-05-07 | CXA8369 | HGH → ZUH | May 7, 00:50 UTC | May 7, 01:10 UTC | 20m |
| 2026-05-06 | CXA8044 | CGQ → HGH | May 6, 06:40 UTC | May 6, 07:15 UTC | 35m |
| 2026-05-04 | CXA8341 | - | May 4, 06:35 UTC | May 4, 09:50 UTC | 3h 15m |
| 2026-05-04 | CXA8526 | - | May 4, 02:00 UTC | May 4, 02:35 UTC | 35m |
| 2026-04-30 | CXA8375 | XMN → NNG | Apr 30, 23:55 UTC | May 1, 14:20 UTC | 14h 25m |
| 2026-04-28 | CXA8727 | TAO → FOC | Apr 28, 04:10 UTC | Apr 28, 04:55 UTC | 45m |
| 2026-04-19 | CXA8605 | FOC → NNG | Apr 19, 12:40 UTC | Apr 19, 15:25 UTC | 2h 45m |
| 2026-04-15 | CXA8359 | XMN → NNG | Apr 15, 10:30 UTC | Apr 15, 10:55 UTC | 25m |
| 2026-04-14 | CXA8426 | - | Apr 14, 15:05 UTC | Apr 14, 15:15 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-6887 page for operator, model, and routing details .