sensors Mode-S transponder
780477
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5383 · BOEING 737-800
- Hex
- 780477
- Octal
- 36002167
- Decimal
- 7,865,463
- Country
- CN
- Tail
- B-5383
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 780477 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 |
|---|---|---|---|
| CXA8696 | - | 3 | 2026-06-09 |
| CXA8409 | - | 3 | 2026-06-12 |
| CXA882 | - | 2 | 2026-05-29 |
| CXA8688 | Xiamen Airlines | 2 | 2026-05-28 |
| CXA8687 | Xiamen Airlines | 2 | 2026-05-28 |
| CXA8867 | - | 1 | 2026-06-04 |
| CXA885 | Xiamen Airlines | 1 | 2026-05-03 |
| CXA881 | - | 1 | 2026-05-29 |
| CXA880 | Xiamen Airlines | 1 | 2026-05-13 |
| CXA879 | Xiamen Airlines | 1 | 2026-05-13 |
| CXA8724 | - | 1 | 2026-06-03 |
| CXA8723 | - | 1 | 2026-06-03 |
| CXA872 | Xiamen Airlines | 1 | 2026-05-07 |
| CXA871 | - | 1 | 2026-05-07 |
| CXA8704 | Xiamen Airlines | 1 | 2026-05-10 |
| CXA8703 | Xiamen Airlines | 1 | 2026-05-10 |
| CXA8676 | - | 1 | 2026-05-04 |
| CXA8675 | - | 1 | 2026-05-04 |
| CXA8524 | Xiamen Airlines | 1 | 2026-05-04 |
| CXA8397 | - | 1 | 2026-05-15 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | CXA8409 | - | Jun 12, 00:25 UTC | Jun 12, 05:20 UTC | 4h 56m |
| 2026-06-09 | CXA8696 | - | Jun 9, 11:10 UTC | Jun 10, 05:30 UTC | 18h 20m |
| 2026-06-09 | CXA8696 | - | Jun 9, 07:50 UTC | Jun 10, 05:30 UTC | 21h 40m |
| 2026-06-09 | CXA8696 | - | Jun 9, 07:35 UTC | Jun 10, 05:30 UTC | 21h 55m |
| 2026-06-04 | CXA8867 | - | Jun 4, 00:45 UTC | Jun 4, 03:55 UTC | 3h 10m |
| 2026-06-03 | CXA8724 | - | Jun 3, 08:30 UTC | Jun 4, 03:55 UTC | 19h 25m |
| 2026-06-03 | CXA8723 | - | Jun 3, 02:55 UTC | Jun 3, 06:30 UTC | 3h 35m |
| 2026-06-02 | CXA8020 | - | Jun 2, 06:40 UTC | Jun 2, 07:05 UTC | 25m |
| 2026-06-01 | - | - | Jun 1, 02:00 UTC | Jun 1, 02:10 UTC | 10m |
| 2026-05-29 | CXA882 | - | May 29, 11:55 UTC | May 29, 12:25 UTC | 30m |
| 2026-05-29 | CXA881 | - | May 29, 10:20 UTC | May 29, 10:50 UTC | 30m |
| 2026-05-28 | CXA8688 | KUL → CKG | May 28, 08:20 UTC | May 28, 08:45 UTC | 25m |
| 2026-05-28 | CXA8688 | KUL → CKG | May 28, 06:00 UTC | May 28, 06:10 UTC | 10m |
| 2026-05-28 | CXA8687 | CKG → KUL | May 28, 04:25 UTC | May 28, 04:45 UTC | 20m |
| 2026-05-27 | CXA8687 | CKG → KUL | May 27, 13:35 UTC | May 28, 02:15 UTC | 12h 40m |
| 2026-05-26 | CXA8388 | SZX → HGH | May 26, 08:10 UTC | May 26, 08:19 UTC | 10m |
| 2026-05-26 | CXA8387 | HGH → SZX | May 26, 04:39 UTC | May 26, 05:00 UTC | 20m |
| 2026-05-20 | CXA8380 | SZX → TSN | May 20, 04:20 UTC | May 20, 04:35 UTC | 15m |
| 2026-05-16 | CXA818 | - | May 16, 10:01 UTC | May 16, 11:01 UTC | 1h 0m |
| 2026-05-16 | CXA817 | - | May 16, 06:25 UTC | May 16, 08:20 UTC | 1h 55m |
| 2026-05-15 | CXA8397 | - | May 15, 00:35 UTC | May 15, 05:15 UTC | 4h 40m |
| 2026-05-14 | CXA8409 | - | May 14, 00:25 UTC | May 14, 00:50 UTC | 25m |
| 2026-05-13 | CXA880 | TPE → FOC | May 13, 03:35 UTC | May 13, 04:10 UTC | 35m |
| 2026-05-13 | CXA879 | FOC → TPE | May 13, 01:20 UTC | May 13, 02:00 UTC | 40m |
| 2026-05-10 | CXA8704 | SIN → HGH | May 10, 07:30 UTC | May 10, 07:45 UTC | 15m |
| 2026-05-10 | CXA8703 | HGH → SIN | May 10, 01:45 UTC | May 10, 04:50 UTC | 3h 5m |
| 2026-05-08 | CXA816 | NRT → XMN | May 8, 06:25 UTC | May 8, 08:09 UTC | 1h 45m |
| 2026-05-08 | CXA815 | XMN → NRT | May 8, 02:49 UTC | May 8, 04:19 UTC | 1h 30m |
| 2026-05-07 | CXA882 | - | May 7, 11:55 UTC | May 7, 12:25 UTC | 30m |
| 2026-05-07 | CXA872 | ICN → XMN | May 7, 04:50 UTC | May 7, 10:25 UTC | 5h 35m |
| 2026-05-07 | CXA871 | - | May 7, 01:05 UTC | May 7, 03:15 UTC | 2h 10m |
| 2026-05-04 | CXA8676 | - | May 4, 19:30 UTC | May 4, 22:30 UTC | 3h 0m |
| 2026-05-04 | CXA8675 | - | May 4, 17:30 UTC | May 4, 17:50 UTC | 20m |
| 2026-05-04 | CXA8524 | TAO → FOC | May 4, 01:15 UTC | May 4, 12:10 UTC | 10h 55m |
| 2026-05-03 | CXA885 | XMN → SIN | May 3, 00:20 UTC | May 3, 14:20 UTC | 13h 59m |
| 2026-05-02 | CXA8409 | - | May 2, 10:40 UTC | May 3, 06:00 UTC | 19h 19m |
| 2026-04-27 | CXA8344 | SZX → HGH | Apr 27, 14:05 UTC | Apr 27, 14:15 UTC | 10m |
| 2026-04-27 | CXA8343 | - | Apr 27, 12:20 UTC | Apr 27, 12:35 UTC | 15m |
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-5383 page for operator, model, and routing details .