sensors Mode-S transponder
780E48
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6486 · BOEING 737-800
- Hex
- 780E48
- Octal
- 36007110
- Decimal
- 7,867,976
- Country
- CN
- Tail
- B-6486
- Type
- B738
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 780E48 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 |
|---|---|---|---|
| CXA869 | Xiamen Airlines | 4 | 2026-04-28 |
| CXA879 | Xiamen Airlines | 3 | 2026-05-30 |
| CXA880 | Xiamen Airlines | 2 | 2026-05-26 |
| CXA878 | Xiamen Airlines | 2 | 2026-06-01 |
| CXA877 | Xiamen Airlines | 2 | 2026-06-01 |
| CXA8650 | - | 2 | 2026-04-14 |
| CXA8416 | Xiamen Airlines | 2 | 2026-05-04 |
| CXA8842 | Xiamen Airlines | 1 | 2026-05-10 |
| CXA8841 | Xiamen Airlines | 1 | 2026-05-10 |
| CXA8828 | Xiamen Airlines | 1 | 2026-05-24 |
| CXA882 | - | 1 | 2026-05-03 |
| CXA881 | - | 1 | 2026-05-03 |
| CXA8784 | - | 1 | 2026-04-14 |
| CXA8783 | Xiamen Airlines | 1 | 2026-04-14 |
| CXA8722 | Xiamen Airlines | 1 | 2026-05-16 |
| CXA8678 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA8677 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA8406 | - | 1 | 2026-05-12 |
| CXA8390 | Xiamen Airlines | 1 | 2026-04-25 |
| CXA8343 | - | 1 | 2026-05-24 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | CXA810 | NRT → FOC | Jun 2, 07:50 UTC | Jun 2, 09:15 UTC | 1h 25m |
| 2026-06-02 | CXA809 | FOC → NRT | Jun 2, 03:05 UTC | Jun 2, 04:40 UTC | 1h 35m |
| 2026-06-01 | CXA878 | ICN → FOC | Jun 1, 11:50 UTC | Jun 1, 12:20 UTC | 30m |
| 2026-06-01 | CXA877 | FOC → ICN | Jun 1, 07:55 UTC | Jun 1, 09:40 UTC | 1h 45m |
| 2026-05-30 | CXA878 | ICN → FOC | May 30, 12:15 UTC | May 30, 12:40 UTC | 25m |
| 2026-05-30 | CXA877 | FOC → ICN | May 30, 03:45 UTC | May 30, 09:40 UTC | 5h 55m |
| 2026-05-30 | CXA879 | FOC → TPE | May 30, 01:30 UTC | May 30, 02:00 UTC | 30m |
| 2026-05-26 | CXA880 | TPE → FOC | May 26, 03:35 UTC | May 26, 04:04 UTC | 30m |
| 2026-05-26 | CXA879 | FOC → TPE | May 26, 01:34 UTC | May 26, 02:04 UTC | 30m |
| 2026-05-25 | CXA828 | MNL → XMN | May 25, 04:05 UTC | May 26, 02:04 UTC | 22h 0m |
| 2026-05-25 | CXA827 | XMN → MNL | May 25, 01:55 UTC | May 25, 02:35 UTC | 40m |
| 2026-05-24 | CXA8828 | ZUH → XMN | May 24, 14:10 UTC | May 24, 14:20 UTC | 10m |
| 2026-05-24 | CXA8343 | - | May 24, 12:20 UTC | May 24, 12:45 UTC | 25m |
| 2026-05-16 | CXA8722 | SUB → FOC | May 16, 04:05 UTC | May 16, 11:35 UTC | 7h 31m |
| 2026-05-12 | CXA8406 | - | May 12, 05:45 UTC | May 12, 05:55 UTC | 10m |
| 2026-05-10 | CXA8842 | ZUH → FOC | May 10, 11:05 UTC | May 10, 11:15 UTC | 10m |
| 2026-05-10 | CXA8841 | FOC → ZUH | May 10, 09:30 UTC | May 10, 09:50 UTC | 20m |
| 2026-05-04 | CXA8416 | KMG → XMN | May 4, 09:45 UTC | May 4, 09:55 UTC | 10m |
| 2026-05-03 | CXA8416 | KMG → XMN | May 3, 12:05 UTC | May 4, 09:55 UTC | 21h 50m |
| 2026-05-03 | CXA882 | - | May 3, 11:35 UTC | May 4, 09:55 UTC | 22h 20m |
| 2026-05-03 | CXA881 | - | May 3, 09:50 UTC | May 3, 10:30 UTC | 40m |
| 2026-05-01 | CXA8318 | SZX → SHA | May 1, 11:35 UTC | May 1, 11:45 UTC | 10m |
| 2026-05-01 | CXA8317 | SHA → SZX | May 1, 09:35 UTC | May 1, 10:00 UTC | 25m |
| 2026-04-28 | CXA869 | XMN → HAN | Apr 28, 06:40 UTC | Apr 28, 10:50 UTC | 4h 10m |
| 2026-04-27 | CXA869 | XMN → HAN | Apr 27, 12:50 UTC | Apr 28, 10:50 UTC | 22h 0m |
| 2026-04-27 | CXA869 | XMN → HAN | Apr 27, 10:05 UTC | Apr 28, 07:05 UTC | 21h 0m |
| 2026-04-27 | CXA869 | XMN → HAN | Apr 27, 02:35 UTC | Apr 27, 12:50 UTC | 10h 15m |
| 2026-04-25 | CXA8390 | SZX → CKG | Apr 25, 14:50 UTC | Apr 25, 15:00 UTC | 10m |
| 2026-04-25 | CXA8304 | SZX → CKG | Apr 25, 04:05 UTC | Apr 25, 04:15 UTC | 10m |
| 2026-04-23 | CXA8678 | KUL → HGH | Apr 23, 08:10 UTC | Apr 23, 11:50 UTC | 3h 40m |
| 2026-04-23 | CXA8677 | HGH → KUL | Apr 23, 03:05 UTC | Apr 23, 06:50 UTC | 3h 46m |
| 2026-04-17 | CXA880 | TPE → FOC | Apr 17, 04:40 UTC | Apr 17, 04:55 UTC | 15m |
| 2026-04-17 | CXA879 | FOC → TPE | Apr 17, 02:30 UTC | Apr 17, 02:55 UTC | 25m |
| 2026-04-14 | CXA8784 | - | Apr 14, 14:50 UTC | Apr 14, 15:05 UTC | 15m |
| 2026-04-14 | CXA8783 | FOC → HAK | Apr 14, 11:40 UTC | Apr 14, 12:00 UTC | 20m |
| 2026-04-14 | CXA8650 | - | Apr 14, 07:15 UTC | Apr 14, 07:45 UTC | 30m |
| 2026-04-14 | CXA8650 | - | Apr 14, 05:15 UTC | Apr 14, 06:55 UTC | 1h 40m |
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-6486 page for operator, model, and routing details .